KF 5 & Plasma

Shark · 2015-02-20 14:44:14

I have icon-only-task-manager and my icons are really small. Is there any way to enlarge them? Anybody know? KDE4 offer that possiblity ...

Ekaradon · 2015-02-20 15:13:48

giddie wrote:

Ekaradon, I'm not sure what problem you're having with SDDM, but if you're using ZSH, there's a known bug in SDDM that can be fixed as I described in an earlier post.

I am going to try this this week-end. However I had two different troubles :
- The first one is that I was not able to login with SDDM
- The second one is that now... while I have changed nothing... I cannot launch anymore SDDM. It fails to instantiate without saying anything. Journalctl gives me nothing.

pb wrote:

Ekaradon wrote:
I also get a strange complaint about "Unknown CMake command 'plasma_install_package'"...

plasma_install_package is in /usr/lib/cmake/KF5Plasma/KF5PlasmaMacros.cmake which is provides by plasma-framework

Thanks but it is already installed, and it still does not work.

~/.kde4/share/apps/plasma/plasmoids/audoban.applet.playbar » sudo pacman -S plasma-framework         ekaradon@skynet
warning: plasma-framework-5.6.0-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) plasma-framework-5.6.0-2

Total Installed Size:  5.96 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                         [#######################################] 100%
(1/1) checking package integrity                                       [#######################################] 100%
(1/1) loading package files                                            [#######################################] 100%
(1/1) checking for file conflicts                                      [#######################################] 100%
(1/1) checking available disk space                                    [#######################################] 100%
(1/1) reinstalling plasma-framework                                    [#######################################] 100%
------------------------------------------------------------
~/.kde4/share/apps/plasma/plasmoids/audoban.applet.playbar » cmake .                                 ekaradon@skynet
CMake Error at CMakeLists.txt:3 (plasma_install_package):
  Unknown CMake command "plasma_install_package".


CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

    cmake_minimum_required(VERSION 3.1)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also "/home/ekaradon/.kde4/share/apps/plasma/plasmoids/audoban.applet.playbar/CMakeFiles/CMakeOutput.log".

Archange · 2015-02-20 15:16:27

You’re trying to compile a KDE4 plasmoid with plasma 5, it doesn’t work indeed.

giddie · 2015-02-20 15:18:50

Complete guess, but do you maybe need extra-cmake-modules too? Where does this plasmoid come from? You sure it's not simply out of date?

As for SDDM, what do you get from "systemctl status sddm"?

arojas · 2015-02-20 15:26:00

Soukyuu wrote:

Anyone else trying to make KDE run scripts on shutdown? I can manually execute them (and see the message they create in the journal), but they're seemingly not being executed on shutdown...

Put them in $HOME/.config/plasma-workspace/shutdown

Ekaradon · 2015-02-20 18:40:00

giddie wrote:

Ekaradon, I'm not sure what problem you're having with SDDM, but if you're using ZSH, there's a known bug in SDDM that can be fixed as I described in an earlier post.

Oh yeah! It works!
In fact, I get troubles because SDDM was using /var partition and this partition was full. So it could not succeed to start right.

Also, I still get some errors about SDDM:

Feb 20 19:23:38 skynet sddm[517]: Greeter session started successfully
Feb 20 19:23:39 skynet sddm-greeter[601]: Connected to the daemon.
Feb 20 19:23:39 skynet sddm[517]: Message received from greeter: Connect
Feb 20 19:23:39 skynet sddm-greeter[601]: QObject: Cannot create children for a parent that is in a different thread.
                                          (Parent is SDDM::GreeterApp(0x7fff86e02e00), parent's thread is QThread(0x25a3e90), current thread is QThread(0x2acc8a0)
Feb 20 19:23:39 skynet sddm-greeter[601]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Feb 20 19:23:39 skynet kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 20 19:23:39 skynet sddm-greeter[601]: QObject: Cannot create children for a parent that is in a different thread.
                                          (Parent is SDDM::GreeterApp(0x7fff86e02e00), parent's thread is QThread(0x25a3e90), current thread is QThread(0x2acc8a0)
Feb 20 19:23:39 skynet sddm-greeter[601]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.

But finally, after modifying SDDM configuration file for managing zsh, I succeed to login. Thanks to you!

I still get complaints about baloo_file_extractor[2794]: "database is locked Unable to fetch row" which is utterly spamming my journalctl... but it seems fine. Do not know from where it comes.
I am going to test plasma now. Really happy to get it finally.

Ekaradon · 2015-02-20 18:43:13

However, even if it works... I notice that the SDDM login takes time before it appears. Something like one minute. I have enabled sddm through sudo systemctl enable sddm.service. Maybe I have forgotten something, or is it just a bug?

I get these logs:

Feb 20 19:51:17 skynet sddm[323]: Signal received: SIGUSR1
Feb 20 19:51:17 skynet sddm[323]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Feb 20 19:51:17 skynet sddm[323]: Display server started.
Feb 20 19:51:17 skynet sddm[323]: Socket server starting...
Feb 20 19:51:17 skynet sddm[323]: Socket server started.
Feb 20 19:51:17 skynet sddm[323]: Greeter starting...
Feb 20 19:51:17 skynet sddm-helper[1723]: [PAM] Starting...
Feb 20 19:51:17 skynet sddm-helper[1723]: [PAM] Authenticating...
Feb 20 19:51:17 skynet sddm-helper[1723]: [PAM] returning.
Feb 20 19:51:17 skynet sddm-helper[1723]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 20 19:51:17 skynet systemd-logind[311]: New session c4 of user sddm.
Feb 20 19:51:17 skynet sddm[323]: Greeter session started successfully
Feb 20 19:51:17 skynet sddm-greeter[1725]: Connected to the daemon.
Feb 20 19:51:17 skynet sddm[323]: Message received from greeter: Connect
Feb 20 19:51:17 skynet sddm-greeter[1725]: QObject: Cannot create children for a parent that is in a different thread.
Feb 20 19:51:17 skynet sddm-greeter[1725]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Feb 20 19:51:17 skynet sddm-greeter[1725]: QObject: Cannot create children for a parent that is in a different thread.
Feb 20 19:51:17 skynet sddm-greeter[1725]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Feb 20 19:51:17 skynet kded5[1734]: Qt: Session management error: networkIdsList argument is NULL
Feb 20 19:51:17 skynet kded5[1734]: klauncher not running... launching kdeinit
Feb 20 19:51:17 skynet kdeinit5[1739]: Qt: Session management error: networkIdsList argument is NULL
Feb 20 19:51:17 skynet kdeinit5[1739]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Feb 20 19:51:17 skynet kdeinit5[1739]: kf5.kinit.klauncher: "/bin/kbuildsycoca5" (pid 1741) up and running.
Feb 20 19:51:17 skynet org.kde.kded5[1732]: kbuildsycoca5 running...
Feb 20 19:51:17 skynet kbuildsycoca5[1741]: kf5.kservice.sycoca: Trying to open ksycoca from "/var/lib/sddm/.cache/ksycoca5"
Feb 20 19:51:17 skynet kbuildsycoca5[1741]: checking file timestamps
Feb 20 19:51:17 skynet kbuildsycoca5[1741]: timestamps check ok
Feb 20 19:51:17 skynet kbuildsycoca5[1741]: Emitting notifyDatabaseChanged ()
Feb 20 19:51:17 skynet kded5[1734]: kf5.kservice.sycoca: Trying to open ksycoca from "/var/lib/sddm/.cache/ksycoca5"
Feb 20 19:51:17 skynet kdeinit5[1739]: kf5.kservice.sycoca: Trying to open ksycoca from "/var/lib/sddm/.cache/ksycoca5"
Feb 20 19:51:17 skynet kdeinit5[1739]: kf5.kinit.klauncher: "/usr/lib/kf5/kconf_update" (pid 1746) up and running.
Feb 20 19:51:17 skynet kdeinit5[1745]: QXcbConnection: Could not connect to display :0
Feb 20 19:51:17 skynet systemd-coredump[1747]: Process 1745 (klauncher) of user 1000 dumped core.
Feb 20 19:51:17 skynet org.kde.kded5[1732]: 2015-02-20T19:51:17 Checking update-file '/usr/share/kconf_update/gtkbreeze.upd' for new updates
Feb 20 19:51:17 skynet drkonqi[1743]: QXcbConnection: Could not connect to display :0
Feb 20 19:51:17 skynet systemd-coredump[1748]: Process 1743 (drkonqi) of user 1000 dumped core.

It stills working but it takes some times (~ 1 minute) before sddm login is displayed.

Last edited by Ekaradon (2015-02-20 18:53:53)

RJQ · 2015-02-21 03:57:43

Anyone else having problems with chromium on plasma, the sites on any given tab freeze although the mouse seems to scroll or click on links and change tabs, but nothing change visually until I maximize/minimize, so far chromium is the only app I experience this behaviour, up to date arch with KF5 and plasma only, nvidia gpu. Thank you for any comment. Also running chromium from the terminal doesn't show any error.

Plaristote · 2015-02-22 16:06:32

Hey !

After the last updates, I'm having an issue with Kwin and the Plasmashell. I already removed all KDE-related settings files, and here's what haven't been fixed by that:

With kwin, all my windows are borderless. The log says "Trying to load decoration plugin Oxygen" and claims that it doesn't exist. It seems related to this issue:
http://comments.gmane.org/gmane.comp.kd … eral/67623
However, installing xcb-util-cursor didn't work for me.

It looks to me like I don't have the oxygen decoration installed. But I can't guess for the life of me what package provides that. It doesn't look like it's in the "oxygen" package, since this one is installed and up to date.

---
And plasma-desktop crashes on launch, displaying this on the console:

Could not find drkonqi at /usr/lib/drkonqi
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-plaristote'
fname "/usr/share/plasma/desktoptheme/default/metadata.desktop"
kf5.kservice.sycoca: Trying to open ksycoca from "/home/plaristote/.cache/ksycoca5"
populateAddPanelsMenu 1
QObject::connect: No such slot ShellCorona::populateAddPanelsMenu()
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Service started, version: 6.2.0
fname "/usr/share/plasma/desktoptheme/default/metadata.desktop"
kscreen: Loading backend
kscreen.xrandr11: This backend is only for XRandR 1.1, your version is:  1 . 4
kscreen.xcb.helper: Detected XRandR 1.4
kscreen.xcb.helper: Event Base:  89
kscreen.xcb.helper: Event Error:  147
kscreen.qscreen: Screen added QScreen(0x2697470) "LVDS1"
kscreen: No backend found!
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_wallpaperimages.so" instead.
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_layoutemplate.so" instead.
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_lookandfeel.so" instead.
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_plasmashell.so" instead.
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_share.so" instead.
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use KPluginInfo::pluginName() in "/usr/lib/qt/plugins/plasma/packagestructure/plasma_packagestructure_wallpaper.so" instead.
ShellCorona::checkActivities is called whilst activity daemon is still connecting
QObject::connect: Cannot connect (null)::destroyed(QObject*) to KScreen::ConfigMonitor::_k_configurationDestroyed(QObject*)
Application::crashHandler() called with signal 11; recent crashes: 1
KCrash: Application 'plasmashell' crashing...

Could it be related to KScreen not being compatible with XRandr 1.4 ?

Last edited by Plaristote (2015-02-22 16:07:01)

arojas · 2015-02-22 16:29:10

There is no oxygen decoration in plasma 5.2, which version of kwin are you using?

giddie · 2015-02-23 10:30:31

For now, I think Breeze is the only theme that is well-supported in Plasma 5. Athough there are certain aspects of Breeze that are very nice, I'm hoping that Oxygen will eventually be ported, if only to offer a second choice.

arojas · 2015-02-23 11:37:10

giddie wrote:

For now, I think Breeze is the only theme that is well-supported in Plasma 5. Athough there are certain aspects of Breeze that are very nice, I'm hoping that Oxygen will eventually be ported, if only to offer a second choice.

It is already ported, see oxygen-window-decoration-git. Will be back in Plasma 5.3. Besides, the aurorae engine was also fixed in 5.2, so it should be possible to download and install themes from GHNS.

dav:d · 2015-02-25 09:40:37

hi there,
sorry for interrupting but i guess i am at right place here.
I am using kf5 since november and i am really happy with it.
But last week,I somehow managed to remove my only (default-kde-) panel and since then i wasn't able to bring it back!
I reinstalled kde and plasma (more than once), i removed all config files (.kde, .kde4), but without getting luck!
For now i am using lxpanel as a workaround, but if anyone has an idea how to get the default one back, i would be very thankfull.

Ps: There is no "Add a panel" option anymore, at least i wasnt able to find one!
thanks, david

arojas · 2015-02-25 09:54:46

dav:d wrote:

Ps: There is no "Add a panel" option anymore, at least i wasnt able to find one!
thanks, david

You have to unlock the widgets first.

misto · 2015-02-25 09:58:10

dav:d wrote:

For now i am using lxpanel as a workaround, but if anyone has an idea how to get the default one back, i would be very thankfull.

It seems that the configuration is stored in ~/.config/plasma-org.kde.plasma.desktop-appletsrc. You could create a new user, log in once, and then copy that file to your own account. I'm not sure if that will work but it's what I'd try.

dav:d · 2015-02-25 10:17:38

Thanks for the fast reply !!

arojas wrote:

You have to unlock the widgets first.

Tried that but without success!

misto wrote:

It seems that the configuration is stored in ~/.config/plasma-org.kde.plasma.desktop-appletsrc. You could create a new user, log in once, and then copy that file to your own account. I'm not sure if that will work but it's what I'd try.

i will try that when i am returning home.

haagch · 2015-02-25 15:00:23

So, I'm another one with no gtk tray. After realizing libindicator* from the pantheon repo is a problem, I removed the pantheon repository and installed libindicator and libappindicator from the AUR:

pacman -Qqs appindicator-gtk
libappindicator-gtk2
libappindicator-gtk3

But the gtk programs I tried, pidgin, thunderbird with firetray, liferea, all do not create a tray icon in the plasma 5 indicator tray, only in an xembed tray like trayer.

I have googled a simple test program and changed http://ubuntuforums.org/showthread.php? … st11902222 a bit:

from gi.repository import Gtk
import sys

if len(sys.argv) <= 1 or not sys.argv[1] == "indicator":
        APPIND_SUPPORT = 0
elif sys.argv[1] == "indicator":
        try: from gi.repository import AppIndicator3
        except:
                print("Error: Appindicator not supported")
                exit()
        APPIND_SUPPORT = 1
print("Using indicator: " + str(bool(APPIND_SUPPORT)))

class IconoTray:
        def __init__(self, iconname):
                self.menu = Gtk.Menu()
                if APPIND_SUPPORT == 1:
                        self.ind = AppIndicator3.Indicator.new("rhythmbox", iconname, AppIndicator3.IndicatorCategory.APPLICATION_STATUS)
                        self.ind.set_status (AppIndicator3.IndicatorStatus.ACTIVE)
                        self.ind.set_menu(self.menu)
                else:
                        self.myStatusIcon = Gtk.StatusIcon()
                        self.myStatusIcon.set_from_icon_name(iconname)
                        self.myStatusIcon.connect('popup-menu', self.right_click_event_statusicon)
        
        def add_menu_item(self, command, title):
                aMenuitem = Gtk.MenuItem()
                aMenuitem.set_label(title)
                aMenuitem.connect("activate", command)
                self.menu.append(aMenuitem)
                self.menu.show_all()

        def get_tray_menu(self):
                return self.menu                

        def right_click_event_statusicon(self, icon, button, time):
                self.get_tray_menu()
                def pos(menu, aicon):
                        return (Gtk.StatusIcon.position_menu(menu, aicon))
                self.menu.popup(None, None, pos, icon, button, time)

app = IconoTray("rhythmbox")
app.add_menu_item(lambda x: Gtk.main_quit(), "Quit")
Gtk.main()

Start with "python3 tray.py" for xembed and "python3 tray.py indicator" for libappindicator.

when libappindicator-gtk3 is NOT installed, then tray.py indicator errors out with not supported stuff. When libappindicator-gtk3 is installed, then it works as expected and an icon in the plasma 5 tray is created.

But the wiki article promises that even the xembed method would be magically translated to an appindicator, but that does not happen.

Is it even supposed to automatically translate xembed tray icons to indicators?

Last edited by haagch (2015-02-25 15:01:05)

arojas · 2015-02-25 15:10:46

haagch wrote:

But the wiki article promises that even the xembed method would be magically translated to an appindicator, but that does not happen.
Is it even supposed to automatically translate xembed tray icons to indicators?

No, this is not true. Applications need to explicitely add support for this, and then need to be recompiled against the appindicator libs. Given that these libs are not even in the official repositories, I doubt that this will be the case with Arch packages.

archoriano · 2015-02-26 18:27:52

Hey! just installed plasma 5, looks cool but some apps are ugly. I expected this from non-native kde apps not from apps like Dolphin

Is this normal? Can it be fixed?

Here's a SS

Thanks

kostas213 · 2015-02-26 18:34:27

Check first if you have the problem with both qt5 and qt4 applications. For example, what about Kate or Kwrite?

ChemBro · 2015-02-26 18:41:57

archoriano wrote:

Hey! just installed plasma 5, looks cool but some apps are ugly. I expected this from non-native kde apps not from apps like Dolphin
Is this normal? Can it be fixed?

Dolphin is a KDE4 app, so you have to wait, until it is ported.

arojas · 2015-02-26 18:43:04

archoriano wrote:

Hey! just installed plasma 5, looks cool but some apps are ugly. I expected this from non-native kde apps not from apps like Dolphin

This has been answered a few times already, including in this same thread. Please do some search

haagch · 2015-02-27 12:13:52

arojas wrote:

Applications need to explicitely add support for this,

Thanks for clarifying. So there definitely does need to be a "legacy systray" addon for plasma. I looked at whether it would be hard to make a plasmoid for that but the documentation is... thin... and doesn't really go into how one would go about it. In pure qml I guess it would not be possible to go outside the provided api. I don't think there is other language support like c++ for plasmoids?

Maybe it would be possible to modify stalonetray to become a service and then display "fake" icons with qml for every tray icon, and somehow forward the context menu. But that doesn't sound like a good idea...

Is there a way to add a legacy systray to the plasma panels I'm not seeing?

giddie · 2015-02-27 12:27:10

I'm pretty sure C++ is supported for Plasmoids. QML is a glue language; the individual components that QML instantiates are often written in C++. It would be a little more complex than writing a JS or Python plasmoid, I expect. I'd contact the Plasma devs first to see if there's already a project to make an XEmbed plasmoid for Plasma 5, though.

miszasty93 · 2015-02-27 14:01:27

How to disable ctrl + alt + L shortcut (lock session)? i can't find this one.

Last edited by miszasty93 (2015-02-27 14:02:04)

Arch Linux

#651 2015-02-20 14:44:14

Re: KF 5 & Plasma

#652 2015-02-20 15:13:48

Re: KF 5 & Plasma

#653 2015-02-20 15:16:27

Re: KF 5 & Plasma

#654 2015-02-20 15:18:50

Re: KF 5 & Plasma

#655 2015-02-20 15:26:00

Re: KF 5 & Plasma

#656 2015-02-20 18:40:00

Re: KF 5 & Plasma

#657 2015-02-20 18:43:13

Re: KF 5 & Plasma

#658 2015-02-21 03:57:43

Re: KF 5 & Plasma

#659 2015-02-22 16:06:32

Re: KF 5 & Plasma

#660 2015-02-22 16:29:10

Re: KF 5 & Plasma

#661 2015-02-23 10:30:31

Re: KF 5 & Plasma

#662 2015-02-23 11:37:10

Re: KF 5 & Plasma

#663 2015-02-25 09:40:37

Re: KF 5 & Plasma

#664 2015-02-25 09:54:46

Re: KF 5 & Plasma

#665 2015-02-25 09:58:10

Re: KF 5 & Plasma

#666 2015-02-25 10:17:38

Re: KF 5 & Plasma

#667 2015-02-25 15:00:23

Re: KF 5 & Plasma

#668 2015-02-25 15:10:46

Re: KF 5 & Plasma

#669 2015-02-26 18:27:52

Re: KF 5 & Plasma

#670 2015-02-26 18:34:27

Re: KF 5 & Plasma

#671 2015-02-26 18:41:57

Re: KF 5 & Plasma

#672 2015-02-26 18:43:04

Re: KF 5 & Plasma

#673 2015-02-27 12:13:52

Re: KF 5 & Plasma

#674 2015-02-27 12:27:10

Re: KF 5 & Plasma

#675 2015-02-27 14:01:27

Re: KF 5 & Plasma

Board footer