You are not logged in.
I do not use Dropbox myself, but with libappindicator-*, lib32-libappindicator, sni-qt and lib32-sni-qt the "new" systray of Plasma 5 should display all icons of GTK2, GTK3, Qt4 and Qt5 applications (32-bit and 64-bit).
Out of curiosity since I'm happy with the dropbox CLI interface, but shouldn't sni-qt and lib32-sni-qt be enough to get the Dropbox systray icon? I have them installed but still no icon.
Offline
Out of curiosity since I'm happy with the dropbox CLI interface, but shouldn't sni-qt and lib32-sni-qt be enough to get the Dropbox systray icon? I have them installed but still no icon.
No. sni-qt is for Qt4 apps, Dropbox uses Qt5.
Offline
dropbox use a embeded qt5 installation, i've tried to edit the installation to use a system Qt5, but the icons still don't work (if they used an edited version)
in a 3.2.4 changelog, the dev's says are working with the Qt dev's to solve the problem
https://www.dropboxforum.com/hc/communi … 2-4?page=1
greetings
Last edited by sl1pkn07 (2015-02-10 22:03:55)
Offline
in a 3.2.4 changelog, the dev's says are working with the Qt dev's to solve the problem
Super, thanks for the info!
Offline
Hi guys,
about a week ago I made the transition to KF5 & Co. and up until yesterday, all was (quite) fine and dandy. However, yesterday when I entered my login info and the splash screen showed up, the progress bar would get stuck at about one third of the login process and after about 20 seconds, a black screen with just a mouse pointer would show up.
I tried to dig out some log message and this is what I found in /var/log/everything.log
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WimaxEnabled" true
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WimaxHardwareEnabled" true
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WirelessEnabled" true
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WirelessHardwareEnabled" true
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WwanEnabled" false
Feb 10 20:45:01 clayman kdeinit5[1867]: libnm-qt: "WwanHardwareEnabled" true
Feb 10 20:45:01 clayman CROND[2042]: (clay) CMD (/usr/bin/modprobed-db store &> /dev/null)
Feb 10 20:46:12 clayman kdeinit5[1867]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/c3"
Feb 10 20:46:12 clayman kdeinit5[1867]: powerdevil: Current session is now inactive
Feb 10 20:46:22 clayman kdeinit5[1867]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/c4"
Feb 10 20:46:22 clayman kdeinit5[1867]: powerdevil: Current session is now inactive
Feb 10 20:46:26 clayman sddm[1766]: Signal received: SIGTERM
Feb 10 20:46:26 clayman kwin_x11[1893]: The X11 connection broke (error 1). Did the X11 server die?
Feb 10 20:46:26 clayman sddm[1766]: Socket server stopping...
Feb 10 20:46:26 clayman sddm[1766]: Socket server stopped.
Feb 10 20:46:26 clayman sddm[1766]: Display server stopping...
Feb 10 20:46:26 clayman kdeinit5[1864]: The X11 connection broke (error 1). Did the X11 server die?
Feb 10 20:46:26 clayman kdeinit5[1867]: The X11 connection broke (error 1). Did the X11 server die?
Feb 10 20:46:26 clayman kdeinit5[1870]: The X11 connection broke (error 1). Did the X11 server die?
Feb 10 20:46:26 clayman kernel: kscreen_backend[1979]: segfault at 1bbdab9 ip 00007f59d087704f sp 00007fffe2775038 error 4 in libQt5Core.so.5.4.0[7f59d076e000+4be000]
Feb 10 20:46:26 clayman kdeinit5[1862]: kdeinit5: Fatal IO error: client killed
Feb 10 20:46:26 clayman kdeinit5[1862]: kdeinit5: sending SIGHUP to children.
Feb 10 20:46:26 clayman kdeinit5[1862]: kdeinit5: sending SIGTERM to children.
Feb 10 20:46:26 clayman kdeinit5[1862]: kdeinit5: Exit.
Feb 10 20:46:26 clayman org.kde.kuiserver[1821]: kuiserver: Fatal IO error: client killed
Feb 10 20:46:26 clayman kactivitymanagerd[1912]: The X11 connection broke (error 1). Did the X11 server die?
Feb 10 20:46:26 clayman sddm[1766]: Display server stopped.
Feb 10 20:46:26 clayman sddm[1766]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Feb 10 20:46:26 clayman kdeinit5[1882]: QProcess: Destroyed while process ("kwin_x11") is still running.
Feb 10 20:46:27 clayman systemd-coredump[2112]: Process 1893 (kwin_x11) of user 1000 dumped core.
Feb 10 20:46:27 clayman systemd-coredump[2110]: Process 1979 (kscreen_backend) of user 1000 dumped core.
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: KCrash: Attempting to start /usr/bin/kglobalaccel5 from kdeinit
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: Warning: connect() failed: : No such file or directory
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: KCrash: Attempting to start /usr/bin/kglobalaccel5 directly
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: KCrash: Application 'kglobalaccel5' crashing...
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: Warning: connect() failed: : No such file or directory
Feb 10 20:46:27 clayman org.kde.kglobalaccel[1821]: KCrash: Attempting to start /usr/lib/drkonqi directly
Feb 10 20:46:27 clayman kglobalaccel5[2130]: QXcbConnection: Could not connect to display :0
Feb 10 20:46:27 clayman kdeinit5[2137]: QXcbConnection: Could not connect to display :0
Feb 10 20:46:28 clayman systemd-coredump[2133]: Process 2130 (kglobalaccel5) of user 1000 dumped core.
Feb 10 20:46:28 clayman systemd-coredump[2138]: Process 2137 (klauncher) of user 1000 dumped core.
Feb 10 20:46:29 clayman drkonqi[2131]: QXcbConnection: Could not connect to display :0
Feb 10 20:46:29 clayman drkonqi[2135]: QXcbConnection: Could not connect to display :0
Feb 10 20:46:29 clayman systemd-coredump[2139]: Process 2131 (drkonqi) of user 1000 dumped core.
Feb 10 20:46:29 clayman systemd-coredump[2140]: Process 2135 (drkonqi) of user 1000 dumped core.
Feb 10 20:46:29 clayman systemd[427]: Starting Shutdown.
Feb 10 20:46:29 clayman systemd[427]: Reached target Shutdown.
Feb 10 20:46:29 clayman systemd[427]: Starting Exit the Session...
Feb 10 20:46:29 clayman systemd[427]: Stopping Default.
Feb 10 20:46:29 clayman systemd[427]: Stopped target Default.
Feb 10 20:46:29 clayman systemd[427]: Stopping Basic System.
Feb 10 20:46:29 clayman systemd[427]: Stopped target Basic System.
Feb 10 20:46:29 clayman systemd[427]: Stopping Sockets.
Feb 10 20:46:29 clayman systemd[427]: Stopped target Sockets.
Feb 10 20:46:29 clayman systemd[427]: Stopping Timers.
Feb 10 20:46:29 clayman systemd[427]: Stopped target Timers.
Feb 10 20:46:29 clayman systemd[427]: Stopping Paths.
Feb 10 20:46:29 clayman systemd[427]: Stopped target Paths.
Feb 10 20:46:29 clayman systemd[427]: Received SIGRTMIN+24 from PID 2143 (kill).
A segfault in libQt5Core? Color me perplexed. Mind you, the kernel message about the segfault did not appear in the log every time this happened but the other messages about broken X11 connection and sddm QProcess getting destroyed did.
Upgrading regularly, I checked Pacman's log and it appeared that no extremely important packages had been upgraded the day before (with the possible exception of dbus but that does not seem to be the culprit here).
Has any of you encountered this (or a similar issue)?
TIA for any ideas.
EDIT: Also, I have tried moving all k*, plasma* etc. config files out of ~/.config to see if it would help. It didn't.
Last edited by clayman (2015-02-11 06:56:15)
Offline
Another question: did we lose the ability to set a separate plasmoids set for the dashboard? I can't find any related setting in systemsettings
Offline
I updated today to plasma 5.2 and the system is running ok, despite the lack of certain options and random stability issues. However, I'm having a strange problem with the scaling of a few icons:
They are massive enough to break the consistency of graphical elements. Any ideas?
Last edited by Elemento Cero (2015-02-11 15:21:53)
Offline
- snip -
I had a similar issue ages ago, I believe I had to delete some KDE config files from ~/.config I can't really remember what but you can try making a backup of the most obvious ones like plasmashellrc or kwinrc and deleting them to see if that helps, if not you may try with some of the other "k" files in that folder. I'm sorry that I can't be more specific, but that's a as far as I can remember.
Offline
Elemento Cero wrote:- snip -
I had a similar issue ages ago, I believe I had to delete some KDE config files from ~/.config I can't really remember what but you can try making a backup of the most obvious ones like plasmashellrc or kwinrc and deleting them to see if that helps, if not you may try with some of the other "k" files in that folder. I'm sorry that I can't be more specific, but that's a as far as I can remember.
I made a backup of /.config and then deleted the whole folder, in order to do it quick, but to no avail; upon restarting, icons remain huge. I even tried the same with /.kde4, but it didn't work either. Could be something related to the EDID of my monitor and the DPI? I never had this problem before.
Last edited by Elemento Cero (2015-02-11 17:27:31)
Offline
Could be something related to the EDID of my monitor and the DPI? I never had this problem before.
Quite likely. See https://bbs.archlinux.org/viewtopic.php?id=187672
Offline
Elemento Cero wrote:Could be something related to the EDID of my monitor and the DPI? I never had this problem before.
Quite likely. See https://bbs.archlinux.org/viewtopic.php?id=187672
I followed the instructions but it didn't work. Then, I tried renaming the file, uncommenting lines related to DPI or resolutions , etc., but the problem persist. Almost all plasma 5 elements show these huge icons (menu, certain plasmoids, chashew...). I'm using the Catalyst driver.
Last edited by Elemento Cero (2015-02-11 18:49:42)
Offline
I don't have the breeze plasma and window decoration theme, how do I get this? I have breeze and breeze-kde4 installed.
Offline
I don't have the breeze plasma and window decoration theme, how do I get this? I have breeze and breeze-kde4 installed.
Then what theme do you have? Breeze is the default one.
Offline
Emil wrote:I don't have the breeze plasma and window decoration theme, how do I get this? I have breeze and breeze-kde4 installed.
Then what theme do you have? Breeze is the default one.
Oxygen.
Offline
Oxygen.
I doubt it. There is no oxygen window decoration in plasma 5.2.
Offline
Emil wrote:Oxygen.
I doubt it. There is no oxygen window decoration in plasma 5.2.
What's this then? https://i.imgur.com/T1LHnys.png
Offline
arojas wrote:Emil wrote:Oxygen.
I doubt it. There is no oxygen window decoration in plasma 5.2.
What's this then? https://i.imgur.com/T1LHnys.png
That's KDE4 system settings.
Offline
arojas wrote:Emil wrote:Oxygen.
I doubt it. There is no oxygen window decoration in plasma 5.2.
What's this then? https://i.imgur.com/T1LHnys.png
You need to install breeze-kde4 too I think.
Offline
Emil wrote:arojas wrote:I doubt it. There is no oxygen window decoration in plasma 5.2.
What's this then? https://i.imgur.com/T1LHnys.png
That's KDE4 system settings.
Ok, that was stupid of me... Installed plasma5 and everything looks okay now, thanks
Offline
Whenever i connect an external monitor to my laptop any open konsole windows are closed. This seems to only happen to konsole, other windows are not closed.
Does this happen to anyone else?
Offline
Does anybody else have and/or know fixes for any of the following?
1) Changes to Konsole shortcuts do not persist, even within a session [I know there are known issues here but am not clear whether there are any workarounds].
2) Icons in the icon task manager are tiny although other icons (in the panel and elsewhere) are fine. [So I don't think I have the not-recognising-correct-EDID problem.]
3) Konsole tabs are not saved as part of the session.
4) Firefox windows are not groups automatically, and no windows can be grouped by hand. That is, the window menus no longer offer 'Attach as tab to...' etc.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
4) Firefox windows are not groups automatically, and no windows can be grouped by hand. That is, the window menus no longer offer 'Attach as tab to...' etc.
I think this was a feature bound to the oxygen window decoration and is among those we have lost in the transition to Plasma 5. Momentarily, I hope.
Last edited by Wu (2015-02-13 00:19:25)
Offline
2) Icons in the icon task manager are tiny although other icons (in the panel and elsewhere) are fine. [So I don't think I have the not-recognising-correct-EDID problem.]
This can happen with the port of the plasma theme air, switch that over to breeze and they should look normal.
Offline
cfr wrote:2) Icons in the icon task manager are tiny although other icons (in the panel and elsewhere) are fine. [So I don't think I have the not-recognising-correct-EDID problem.]
This can happen with the port of the plasma theme air, switch that over to breeze and they should look normal.
I've tried both breeze and breeze dark. Initially, breeze dark solved the problem, but since I rebooted I get the problem with both. I've not tried the port of air so I don't think that's the problem.
cfr wrote:4) Firefox windows are not groups automatically, and no windows can be grouped by hand. That is, the window menus no longer offer 'Attach as tab to...' etc.
I think this was a feature bound to the oxygen window decoration and is among those we have lost in the transition to Plasma 5. Momentarily, I hope.
I do hope the loss is temporary. Extraordinarily useful on a small screen!
Last edited by cfr (2015-02-13 12:48:56)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Has anyone else had any issues with SDDM? I'm up & running with Plasma 5, but after I enter my login details with SDDM, I get a blank screen and no progress. I can get into Plasma fine with startx.
Here's the journal from sddm. The SIGTERM will be from me stopping the sddm service.
Feb 16 12:55:27 Leto sddm[574]: Initializing...
Feb 16 12:55:27 Leto sddm[574]: Starting...
Feb 16 12:55:27 Leto sddm[574]: Adding new display 0 on vt 1 ...
Feb 16 12:55:27 Leto sddm[574]: Adding cookie to "/var/run/sddm/:0"
Feb 16 12:55:27 Leto sddm[574]: Display server starting...
Feb 16 12:55:27 Leto sddm[574]: Running: /usr/bin/X :0 -auth /var/run/sddm/:0 -nolisten tcp -background none -noreset vt1
Feb 16 12:55:28 Leto sddm[574]: Signal received: SIGUSR1
Feb 16 12:55:28 Leto sddm[574]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Feb 16 12:55:28 Leto sddm[574]: Display server started.
Feb 16 12:55:28 Leto sddm[574]: Socket server starting...
Feb 16 12:55:28 Leto sddm[574]: Socket server started.
Feb 16 12:55:28 Leto sddm[574]: Greeter starting...
Feb 16 12:55:28 Leto sddm-helper[828]: [PAM] Starting...
Feb 16 12:55:28 Leto sddm-helper[828]: [PAM] Authenticating...
Feb 16 12:55:28 Leto sddm-helper[828]: [PAM] returning.
Feb 16 12:55:28 Leto sddm-helper[828]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 16 12:55:28 Leto sddm[574]: Greeter session started successfully
Feb 16 12:55:28 Leto sddm[574]: Message received from greeter: Connect
Feb 16 12:55:35 Leto sddm[574]: Message received from greeter: Login
Feb 16 12:55:35 Leto sddm[574]: Reading from "plasma.desktop"
Feb 16 12:55:35 Leto sddm-helper[2951]: [PAM] Starting...
Feb 16 12:55:35 Leto sddm-helper[2951]: [PAM] Authenticating...
Feb 16 12:55:35 Leto sddm-helper[2951]: [PAM] Preparing to converse...
Feb 16 12:55:35 Leto sddm-helper[2951]: [PAM] Conversation with 1 messages
Feb 16 12:55:35 Leto sddm-helper[2951]: [PAM] returning.
Feb 16 12:55:35 Leto sddm[574]: Authenticated successfully
Feb 16 12:55:35 Leto sddm[574]: Auth: sddm-helper exited successfully
Feb 16 12:55:35 Leto sddm[574]: Greeter stopped.
Feb 16 12:55:35 Leto sddm-helper[2951]: pam_unix(sddm:session): session opened for user dannpg by (uid=0)
Feb 16 12:55:36 Leto sddm[574]: Session started
Feb 16 12:55:36 Leto sddm[574]: Auth: sddm-helper exited with 1
Feb 16 12:55:55 Leto sddm[574]: Signal received: SIGTERM
Feb 16 12:55:55 Leto sddm[574]: Socket server stopping...
Feb 16 12:55:55 Leto sddm[574]: Socket server stopped.
Feb 16 12:55:55 Leto sddm[574]: Display server stopping...
Feb 16 12:55:55 Leto sddm[574]: Display server stopped.
Offline