Page 5 of 13
Porteus-v5.0rc3 x86_64 bug reports
Posted: 27 Jul 2021, 06:16
by jroovy
XFCE: brightness keys are not working
1) Press the brightness keys on your laptop
2) Press Ctrl+Alt+F1
3) Observe the messages in the console saying: "No outputs have backlight property"
Porteus-v5.0rc3 x86_64 bug reports
Posted: 27 Jul 2021, 06:58
by babam
AcnapyxoB wrote: ↑27 Jul 2021, 06:02
babam, mounting result:
Code: Select all
using /dev/loop11
Please wait while I gather some info ....
NTFS signature is missing.
Failed to mount '/dev/loop39': Invalid argument
The device '/dev/loop39' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Code: Select all
su
toor
mkdir mountdir
losetup /dev/loopX encrypted.dat
cryptsetup luksOpen /dev/loopX crypt
mount /dev/mapper/crypt mountdir
Porteus-v5.0rc3 x86_64 bug reports
Posted: 27 Jul 2021, 13:19
by AcnapyxoB
losetup /dev/loopX encrypted.dat
Code: Select all
losetup: /dev/loopX: failed to set up loop device: No such file or directory
Porteus-v5.0rc3 x86_64 bug reports
Posted: 27 Jul 2021, 13:27
by babam
AcnapyxoB wrote: ↑27 Jul 2021, 13:19
losetup /dev/loopX encrypted.dat
Code: Select all
losetup: /dev/loopX: failed to set up loop device: No such file or directory
Code: Select all
losetup -f encrypted.dat
losetup -a | grep encrypted.dat
Porteus-v5.0rc3 x86_64 bug reports
Posted: 27 Jul 2021, 13:38
by AcnapyxoB
babam wrote: ↑27 Jul 2021, 13:27
AcnapyxoB wrote: ↑27 Jul 2021, 13:19
losetup /dev/loopX encrypted.dat
Code: Select all
losetup: /dev/loopX: failed to set up loop device: No such file or directory
Code: Select all
losetup -f encrypted.dat
losetup -a | grep encrypted.dat
The above commands mounts existing save.dat file, not the new created one !
Porteus-v5.0rc3 x86_64 bug reports
Posted: 29 Jul 2021, 02:59
by Bicephale
Bicephale wrote: ↑24 Jul 2021, 04:29
...why not also seek inspiration from the Sergei Strelec Live WinPE...
Bad piece of advice unless prepared with multiple anti-virus strategies, better left alone. VirtualBox which works both on Windows and Linux gave me a lot more enjoyable moments actually confirming the idea of playing video on a Linux machine that doesn't have the necessary drivers to access legacy Windows devices itself...
Porteus-v5.0rc3 x86_64 bug reports
Posted: 01 Aug 2021, 17:43
by Ed_P
Porteus-v5.0rc3 x86_64 bug reports
Posted: 04 Aug 2021, 11:43
by Bicephale
D/Ld .bat script, table PC is a hybrid i3 featured with both BIOS and UEFI. Laptop is UEFI only CherryTrail and i may want to have Porteus installed besides one of it's present TWO Linux flavours (XUbuntu + Linuxium) - since with Windows 10 now gone such aging machine with no room to update (W11 wants more than 32 GB, i think) can finally have a second life, possibly even more productive... Qui vivra verra!
En tout cas merci bien d'y avoir pensé!
Porteus-v5.0rc3 x86_64 bug reports
Posted: 08 Aug 2021, 08:46
by raja
porteus-5.0rc3-QT
pcmanfm(root) does not start
Code: Select all
root@porteus:/home/guest# /usr/bin/pcmanfm-qt
QStandardPaths: runtime directory '/tmp/xdg-runtime-guest' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 100
Porteus-v5.0rc3 x86_64 bug reports
Posted: 09 Aug 2021, 09:57
by raja
Here is the outcome, when I tried .... ,
Code: Select all
root@porteus:/home/guest# psu dbus-launch --exit-with-session pcmanfm-qt %U
GConf Error: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
psu: unrecognized option '--exit-with-session'
GKsu version 2.0.2
Usage: psu [-u <user>] [options] <command>
I tried with thunar. It starts from terminal.
Porteus-v5.0rc3 x86_64 bug reports
Posted: 09 Aug 2021, 13:01
by ncmprhnsbl
raja wrote: ↑09 Aug 2021, 09:57
GKsu version 2.0.2
try fresh, gksu should not be present.
although, technically this is a bug, since psu script should no longer look for it.
Porteus-v5.0rc3 x86_64 bug reports
Posted: 09 Aug 2021, 21:34
by amplatfus
raja wrote: ↑12 Jul 2021, 10:27
Installing blueman-2.2.1-x86_64-1.xzm solved the above problem.
Bluetooth icon in panel. Cheers.
Hi,
Could you please share this module?
Thank you so much,
amplatfus
Porteus-v5.0rc3 x86_64 bug reports
Posted: 11 Aug 2021, 07:11
by Blaze
KDE5 bug report from this post
СОФТ и инструкции для Porteus-5.x (Пост dorohov.alex77 #83575)
Then, in Dolphin, when I went to Network and double clicked "Samba Shares" I saw the error
Code: Select all
Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/smb.so'
Porteus-v5.0rc3 x86_64 bug reports
Posted: 11 Aug 2021, 10:27
by amplatfus
amplatfus wrote: ↑09 Aug 2021, 21:34
raja wrote: ↑12 Jul 2021, 10:27
Installing blueman-2.2.1-x86_64-1.xzm solved the above problem.
Bluetooth icon in panel. Cheers.
Hi,
Could you please share this module?
Thank you so much,
amplatfus
Thank you for sharing!
On clean RC3, in my case is activating, I can even hear the sound on BT but is mono and I cannot see any profiles for my device.
I have some Python errors. I saved my steps. Please if you have any clue, please reply. I will attached a screenshot too.
Thank you in advance.
amplatfus
PS:
I did not manage to take the screenshot form the moment I had ne Mono ouput related to BT device.
Code: Select all
root@porteus:~# chmod +x /etc/rc.d/rc.bluetooth
root@porteus:~# /etc/rc.d/rc.bluetooth stop
root@porteus:~# /etc/rc.d/rc.bluetooth start
Starting Bluetooth services: bluetoothd hciconfig sdptool hciattach
root@porteus:~# blueman-applet
blueman-applet 13.49.50 ERROR PluginManager:90 load_plugin: Unable to load plugin module AppIndicator
Traceback (most recent call last):
File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/AppIndicator.py", line 11, in <module>
require_version('AppIndicator3', '0.1')
File "/usr/lib64/python3.9/site-packages/gi/__init__.py", line 126, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace AppIndicator3 not available
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.9/site-packages/blueman/main/PluginManager.py", line 88, in load_plugin
importlib.import_module(self.module_path.__name__ + f".{plugin}")
File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 850, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/AppIndicator.py", line 13, in <module>
raise ImportError("AppIndicator3 not found")
ImportError: AppIndicator3 not found
blueman-applet 13.49.50 WARNING PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 13.49.50 WARNING PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Porteus-v5.0rc3 x86_64 bug reports
Posted: 11 Aug 2021, 20:27
by beny
Code: Select all
guest@porteus:~$ su root
Password:
root@porteus:/home/guest# sh '/etc/rc.d/rc.bluetooth' start
Starting Bluetooth services: bluetoothd hciconfig sdptool hciattach
root@porteus:/home/guest# bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:1A:7D:DA:71:0D BlueZ 5.59 [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:0D Discovering: yes
[NEW] Device FE:77:E6:B5:E8:6F Mi True Wireless EBs Basic_R
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[CHG] Device FE:77:E6:B5:E8:6F RSSI: -80
[CHG] Device FE:77:E6:B5:E8:6F RSSI: -64
[DEL] Device FE:77:E6:B5:E8:6F Mi True Wireless EBs Basic_R
[NEW] Device FE:77:E6:B5:E8:6F Mi True Wireless EBs Basic_R
[CHG] Device FE:77:E6:B5:E8:6F RSSI: -87
[CHG] Device FE:77:E6:B5:E8:6F RSSI: -67
[bluetooth]# pair FE:77:E6:B5:E8:6F
Attempting to pair with FE:77:E6:B5:E8:6F
[CHG] Device FE:77:E6:B5:E8:6F Connected: yes
[CHG] Device FE:77:E6:B5:E8:6F Modalias: bluetooth:v05D6p000Ad0240
[CHG] Device FE:77:E6:B5:E8:6F UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device FE:77:E6:B5:E8:6F UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device FE:77:E6:B5:E8:6F UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device FE:77:E6:B5:E8:6F UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device FE:77:E6:B5:E8:6F ServicesResolved: yes
[CHG] Device FE:77:E6:B5:E8:6F Paired: yes
Pairing successful
[CHG] Device FE:77:E6:B5:E8:6F ServicesResolved: no
[CHG] Device FE:77:E6:B5:E8:6F Connected: no
[bluetooth]# trust FE:77:E6:B5:E8:6F
[CHG] Device FE:77:E6:B5:E8:6F Trusted: yes
Changing FE:77:E6:B5:E8:6F trust succeeded
[bluetooth]# connect FE:77:E6:B5:E8:6F
Attempting to connect to FE:77:E6:B5:E8:6F
[CHG] Device FE:77:E6:B5:E8:6F Connected: yes
Connection successful
[CHG] Device FE:77:E6:B5:E8:6F ServicesResolved: yes
[Mi True Wireless EBs Basic_R]#
well i have do in this way to connect to bluetooth dongle blueman do not work also here you have to open pulseaudio mixer for the stereo option.