Porteus-v4.0rc4 bug reports
Porteus-v4.0rc4 bug reports
Sorry being late...
In MATE DE the locale modules generated via Porteus Centre seems to be mixed/uncomplete. I.E. Brisk Menu shows locale strings correctly, but desktop menu (RightMouseButton) is showing in english.
Also, some settings (power-management sleep display, fonts settings, etc.), remain unchanged despite saving changes while some others are kept.
The keyboard behaviour operates as in version 3.2.2: Whenever the desktop is alive, the us layout is back into bussiness no matter what cheatcode was chosen at startup (cheatcode keyb=es in my case). Clicking on the country tray icon switches to the desired one, althought it changes from time to time, and depending on which tasks are executed. The only valid solution I've found is to click in the systray and set it manually _just after_ login in.
Thanks.
In MATE DE the locale modules generated via Porteus Centre seems to be mixed/uncomplete. I.E. Brisk Menu shows locale strings correctly, but desktop menu (RightMouseButton) is showing in english.
Also, some settings (power-management sleep display, fonts settings, etc.), remain unchanged despite saving changes while some others are kept.
The keyboard behaviour operates as in version 3.2.2: Whenever the desktop is alive, the us layout is back into bussiness no matter what cheatcode was chosen at startup (cheatcode keyb=es in my case). Clicking on the country tray icon switches to the desired one, althought it changes from time to time, and depending on which tasks are executed. The only valid solution I've found is to click in the systray and set it manually _just after_ login in.
Thanks.
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
Porteus-v4.0rc4 bug reports
Yes you're right. The cheatcode I'm using is kmap=es
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
-
- Black ninja
- Posts: 76
- Joined: 28 Dec 2013, 15:21
- Distribution: Porteus 4.0 LXDE 64-bit
- Location: England
Porteus-v4.0rc4 bug reports
fulalas
LXDE 32-bit
I can now confirm that the Porteus settings centre does start from the menu. But for some unknown reason it didn't work at the time of the test.
LXDE 32-bit
I can now confirm that the Porteus settings centre does start from the menu. But for some unknown reason it didn't work at the time of the test.
-
- Black ninja
- Posts: 76
- Joined: 28 Dec 2013, 15:21
- Distribution: Porteus 4.0 LXDE 64-bit
- Location: England
Porteus-v4.0rc4 bug reports
Openbox 32-bit
epdf viewer: If a pdf document contains .jpg images, they are not shown in the viewer.
Cannot get kmap=gb to work. Even setting the keymap in porteus-settings-centre does not retain the setting between boots.
epdf viewer: If a pdf document contains .jpg images, they are not shown in the viewer.
Cannot get kmap=gb to work. Even setting the keymap in porteus-settings-centre does not retain the setting between boots.
Porteus-v4.0rc4 bug reports
@Philip, this was already fixed. It's going public on the next release
-
- Contributor
- Posts: 1857
- Joined: 09 Aug 2013, 14:25
- Distribution: Porteus and Nemesis
- Location: USA
Porteus-v4.0rc4 bug reports
Thanks for the test file with the 4 images and with my builds I can see all 4 images when I open your pdf file. Thanks for your test pdf file.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.
Porteus-v4.0rc4 bug reports
If cheatcodes like changes=, volume=, kmap= etc. are added in the new porteus-v4.0-x86_64.cfg instead of passing through the bootloader, then these cheatcodes will not be present in /proc/cmdline. Hence porteus scripts that check only /proc/cmdline for cheatcodes would fail to implement the cheatcodes.
Also looks like some cheatcodes (noeject, changes-ro etc.) are only checked in /proc/cmdline by linuxrc.
Code: Select all
[root:/opt/porteus-scripts]# grep -R cmdline
xorg/gui-autostart:VOLUME=`egrep -o " volume=[^ ]+" /proc/cmdline | cut -d= -f2`
xorg/gui-autostart:KMAP=`egrep -o " kmap=[^ ]+" /proc/cmdline | cut -d= -f2`
xorg/gui-autostart:for cmd in `egrep -o " guiexec=[^ ]+" /proc/cmdline | cut -d= -f2- | tr ";" " "`; do
gtk-porteus-timeconfig:grep "changes=" /proc/cmdline && export using_changes=1 || unset using_changes
make-changes:## Check if changes file was used in cmdline
make-changes:changeline=`grep -o -P 'changes=/.*.dat' /proc/cmdline`
pinstaller: export cmdline=`</proc/cmdline`
pinstaller:#export cchanges=`cat /proc/cmdline|grep -o "[^ ]*changes[^ ]*"`
pinstaller:if [ `grep -o copy2ram /proc/cmdline` ]; then
porteus-settings-centre:[[ `grep -o "changes=" /proc/cmdline` ]] && using_changes=1
xpsinfo:cat /proc/cmdline >> $info
psinfo:cat /proc/cmdline >> $info
pxe-server:storage=`egrep -o " storage=[^ ]+" /proc/cmdline | cut -d= -f2 | sed s@^/dev/@/mnt/@`
update-porteus:if [ `egrep -o " from=[^ ]+" /proc/cmdline | cut -d= -f2 | grep "\.iso"` ]; then
Porteus-v4.0rc4 bug reports
M. Eerie, can you execute the following command and then check if keyboard layout stays in es layout and does not jump to us layout after that from time to time?
Code: Select all
guest@porteus:~$ gsettings set org.mate.peripherals-keyboard-xkb.kbd layouts "['es', 'us']"
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Porteus-v4.0rc4 bug reports
Thanks jssouza,
I know there are many cheatcodes that won`t work. It`s a matter of me tracking them all down and adding the extra check. Thanks for the list.
I know there are many cheatcodes that won`t work. It`s a matter of me tracking them all down and adding the extra check. Thanks for the list.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
Porteus-v4.0rc4 bug reports
Done. And yes, the layout seems to be fixed now.
However, in dconf-editor, the real path seems to be: /org/mate/desktop/peripherals/keyboard/kbd/layouts
Perhaps this schema was missing. I'll check it out booting again, prior to save my ~/.config/dconf/user file.
Thanks!
Edit: This was my previous setup. Not sure this makes a big change.
Edit2: Sorry...
Last edited by M. Eerie on 09 Mar 2018, 16:26, edited 1 time in total.
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
- Ed_P
- Contributor
- Posts: 8343
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus-v4.0rc4 bug reports
Maybe an early run routine that merges the .cfg file cheatcodes into the cmdline ones would be an easier approach.
Anyone able to read this image?
Ed
- Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v4.0rc4 bug reports
Nope, seems the image is just a preview? M. Eerie, you need to upload a higher quality image...
Cheers!
Yours Rava
Yours Rava
Porteus-v4.0rc4 bug reports
Fixed image above.
Digging up a bit more, I've found that keyboard reverts back to 'us' as before.
I'd swear this is happening whenever a system updating script fires up (i.e. a module gets activated, etc.). Then the layout can't get swapped by simply clicking system tray icon. You have to right-click on it, then select Layouts --> English (US), and only then, you are able to select another layout.
Cheers!
Digging up a bit more, I've found that keyboard reverts back to 'us' as before.
I'd swear this is happening whenever a system updating script fires up (i.e. a module gets activated, etc.). Then the layout can't get swapped by simply clicking system tray icon. You have to right-click on it, then select Layouts --> English (US), and only then, you are able to select another layout.
Cheers!
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584