You are not logged in.
I recently switched from Mate to KDE. Things were working well, but after making some changes to my panel, I discovered that the changes are lost upon logging out.
For example, if I add, remove or change the position of widgets, they're back to how they were upon logging in again.
Any suggestions?
Offline
I recently switched from Mate to KDE. Things were working well, but after making some changes to my panel, I discovered that the changes are lost upon logging out.
For example, if I add, remove or change the position of widgets, they're back to how they were upon logging in again.
Any suggestions?
I had the same bug that's the reason I switched to Gnome. I heard of the same issue also by other users on Manjaro Forum and apparently they haven't fixed it yet. This appeared on 5.18 release and the 5.19 did nothing to fix.
Offline
I had the same bug that's the reason I switched to Gnome. I heard of the same issue also by other users on Manjaro Forum and apparently they haven't fixed it yet. This appeared on 5.18 release and the 5.19 did nothing to fix.
Thanks. Do you know if the bug is specific to Arch?
It's really frustrating, as I moved from Mate due to not being able to get the look I wanted. I want a theme that gives me a black panel without making dialogue boxes or windows black. Mate doesn't appear to provide this with the included themes. If I manually change the panel to black, the text fails to turn white, and I can't read anything.
I haven't used Gnome for years. Maybe I should try it.
Offline
Worksforme™
How are you starting your session what's your output for
systemctl status
stat ~/.config ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasmarc ~/.config/plasmashellrc
Last edited by V1del (2020-06-23 17:31:34)
Offline
Thanks. Do you know if the bug is specific to Arch?
It's not specific to Arch, I read about it on Manjaro forum.
Last edited by digitalone (2020-06-23 19:20:01)
Offline
What is the output of
stat ~/.config ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Plasma 5.19.2 just arrived. It made no difference.
Given Manjaro is based on Arch, the issue being in Manjaro doesn't really shed light on its origin.
File: /home/eclipse/.config
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 801h/2049d Inode: 284525 Links: 31
Access: (0700/drwx------) Uid: ( 1000/ eclipse) Gid: ( 1000/ eclipse)
Access: 2020-06-23 16:13:17.858850303 +1000
Modify: 2020-06-24 06:53:37.508715152 +1000
Change: 2020-06-24 06:53:37.508715152 +1000
Birth: 2019-01-17 02:16:36.892731435 +1100
File: /home/eclipse/.config/plasma-org.kde.plasma.desktop-appletsrc
Size: 7114 Blocks: 16 IO Block: 4096 regular file
Device: 801h/2049d Inode: 263539 Links: 1
Access: (0600/-rw-------) Uid: ( 1000/ eclipse) Gid: ( 1000/ eclipse)
Access: 2020-06-23 20:47:42.852029805 +1000
Modify: 2020-06-23 20:47:42.418696475 +1000
Change: 2020-06-23 20:47:42.428696474 +1000
Birth: 2020-06-23 20:47:42.418696475 +1000
File: /home/eclipse/.config/plasmarc
Size: 150 Blocks: 8 IO Block: 4096 regular file
Device: 801h/2049d Inode: 263547 Links: 1
Access: (0600/-rw-------) Uid: ( 1000/ eclipse) Gid: ( 1000/ eclipse)
Access: 2020-06-23 14:37:55.894148455 +1000
Modify: 2020-06-23 14:37:55.427481789 +1000
Change: 2020-06-23 14:37:55.434148456 +1000
Birth: 2020-06-23 14:37:55.427481789 +1000
File: /home/eclipse/.config/plasmashellrc
Size: 700 Blocks: 8 IO Block: 4096 regular file
Device: 801h/2049d Inode: 263525 Links: 1
Access: (0600/-rw-------) Uid: ( 1000/ eclipse) Gid: ( 1000/ eclipse)
Access: 2020-06-23 07:00:12.514981508 +1000
Modify: 2020-06-23 06:59:17.671694006 +1000
Change: 2020-06-23 06:59:17.678360605 +1000
Birth: 2020-06-23 06:59:17.671694006 +1000
Last edited by Pumpino (2020-06-23 21:04:21)
Offline
Please always put shell IO and file contents in "code" tags.
Check your journal, could be a crash-on-exit.
How are you starting your session
Offline
How are you starting your session what's your output for
systemctl status
I'm using SDDM. I suspect that doesn't answer your question though.
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─user@1000.service …
│ │ ├─pulseaudio.service
│ │ │ ├─3623 /usr/bin/pulseaudio --daemonize=no
│ │ │ └─3666 /usr/lib/pulse/gsettings-helper
│ │ ├─apps-thunderbird-c4e194fcd0a34f8f92aef976e95ecd1d.scope
│ │ │ ├─3705 /usr/lib/thunderbird/thunderbird
│ │ │ ├─3777 /usr/lib/firefox/firefox https://bbs.archlinux.org/viewtopic.php?pid=1911868#p1911868
│ │ │ ├─3828 /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -prefsLen 1 -prefMapSize 221084 -parentBuildID 20200603085854 -appdir /usr/lib/firefox/browser 3777 true tab
│ │ │ ├─3875 /usr/lib/firefox/firefox -contentproc -childID 2 -isForBrowser -prefsLen 6395 -prefMapSize 221084 -parentBuildID 20200603085854 -appdir /usr/lib/firefox/browser 3777 true tab
│ │ │ ├─3991 /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -prefsLen 7297 -prefMapSize 221084 -parentBuildID 20200603085854 -appdir /usr/lib/firefox/browser 3777 true tab
│ │ │ └─4118 /usr/lib/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 7344 -prefMapSize 221084 -parentBuildID 20200603085854 -appdir /usr/lib/firefox/browser 3777 true tab
│ │ ├─gvfs-daemon.service
│ │ │ ├─643 /usr/lib/gvfsd
│ │ │ └─653 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f
│ │ ├─apps-org.kde.konsole-240b26a5dfc740058c44ce75a46e0db0.scope
│ │ │ ├─4359 /usr/bin/konsole
│ │ │ ├─4370 /bin/bash
│ │ │ ├─4376 su
│ │ │ ├─4379 bash
│ │ │ ├─4381 systemctl status
│ │ │ └─4382 less
│ │ ├─init.scope
│ │ │ ├─471 /usr/lib/systemd/systemd --user
│ │ │ └─472 (sd-pam)
│ │ ├─at-spi-dbus-bus.service
│ │ │ ├─ 704 /usr/lib/at-spi-bus-launcher
│ │ │ ├─ 710 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
│ │ │ └─3980 /usr/lib/at-spi2-registryd --use-gnome-session
│ │ └─dbus.service
│ │ ├─ 482 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
│ │ ├─ 520 /usr/lib/dconf-service
│ │ ├─3577 /usr/lib/kactivitymanagerd
│ │ ├─3590 /usr/bin/kglobalaccel5
│ │ └─3762 /usr/lib/kf5/kscreen_backend_launcher
│ ├─session-2.scope
│ │ └─567 /usr/bin/baloo_file
│ └─session-7.scope
│ ├─3523 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-authd1665de2-a506-4cba-a329-5dbac3a9ce57 --id 5 --start /usr/bin/startplasma-x11 --user eclipse
│ ├─3524 /usr/bin/startplasma-x11
│ ├─3540 /usr/lib/kf5/start_kdeinit
│ ├─3541 kdeinit5: Running...
│ ├─3542 /usr/lib/kf5/klauncher --fd=9
│ ├─3556 /usr/bin/kded5
│ ├─3560 /usr/bin/kwin_x11
│ ├─3592 /usr/bin/ksmserver
│ ├─3602 /usr/bin/xembedsniproxy
│ ├─3605 /usr/bin/kaccess
│ ├─3607 /usr/lib/polkit-kde-authentication-agent-1
│ ├─3612 /usr/bin/plasmashell
│ ├─3622 /usr/bin/gmenudbusmenuproxy
│ ├─3625 /usr/lib/DiscoverNotifier
│ ├─3632 /usr/bin/megasync
│ └─4063 file.so [kdeinit5] file local:/run/user/1000/klaunchernfQuha.1.slave-socket local:/run/user/1000/kded5HhGkAg.1.slave-socket
├─init.scope
│ └─1 /sbin/init
system.slice
├─systemd-udevd.service
│ └─250 /usr/lib/systemd/systemd-udevd
├─home-eclipse-data.mount
│ └─331 /usr/bin/mount.ntfs-3g /dev/sda3 /home/eclipse/data -o rw
├─polkit.service
│ └─535 /usr/lib/polkit-1/polkitd --no-debug
├─rtkit-daemon.service
│ └─668 /usr/lib/rtkit-daemon
├─home-eclipse-media.mount
│ └─329 /usr/bin/mount.ntfs-3g /dev/sda4 /home/eclipse/media -o rw
├─wpa_supplicant.service
│ └─417 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant
├─systemd-journald.service
│ └─237 /usr/lib/systemd/systemd-journald
├─sshd.service
│ └─376 sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startups
├─colord.service
│ └─456 /usr/lib/colord
├─org.cups.cupsd.service
│ └─455 /usr/bin/cupsd -l
├─NetworkManager.service
│ └─358 /usr/bin/NetworkManager --no-daemon
├─vsftpd.service
│ └─378 /usr/bin/vsftpd
├─dhcpcd.service
│ ├─362 dhcpcd: [master] [ip4] [ip6]
│ ├─363 dhcpcd: [privileged actioneer]
│ ├─364 dhcpcd: [network proxy]
│ ├─365 dhcpcd: [control proxy]
│ └─453 dhcpcd: [BPF ARP] enp2s0 192.168.1.100
├─lvm2-lvmetad.service
│ └─256 /usr/bin/lvmetad -f
├─upower.service
│ └─663 /usr/lib/upowerd
├─sddm.service
│ ├─ 396 /usr/bin/sddm
│ └─3487 /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{0c04547d-cf4a-435d-998e-dce49d52202a} -background none -noreset -displayfd 18 -seat seat0 vt1
├─udisks2.service
│ └─582 /usr/lib/udisks2/udisksd
├─dbus.service
│ └─357 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
├─systemd-timesyncd.service
│ └─338 /usr/lib/systemd/systemd-timesyncd
└─systemd-logind.service
└─360 /usr/lib/systemd/systemd-logind
Offline
megasync sounds like it mess with this…
Offline
megasync sounds like it mess with this…
How did you arrive at that conclusion?
I disabled MegaSync and the changes still don't stick.
It might be time to try Gnome or Cinnamon.
Offline
Theory was: logout, network disconnect, megasync fails to upload your config. Login, network connects, megasync downloads your config.
Check your journal, could be a crash-on-exit.
Offline
Check your journal, could be a crash-on-exit.
What command would I use for that?
Offline
Offline
Well, this is just plain weird. I rebooted, made some changes to the panel, logged out and then logged in again, with the aim of running journal -b to sift through all of the messages since booting. It saved the changes this time. I have no idea why, as I've rebooted the machine a number of times today. I'd like to jump for joy, but I'm uneasy, given I don't know why it began working.
Last edited by Pumpino (2020-06-24 07:54:18)
Offline
I'd say the megasync theory not being too far fetched here... FWIW if you had test runs that did run into the issue you can also just relevantly filter the journal to look at excerpts from when it should still have occurred.
Last edited by V1del (2020-06-24 08:50:42)
Offline
And you'll likely want to look into older journals (from boots/logouts/logins where this might have failed)
Offline