[opensuse-factory] [TW] question about NetworkManager
Hi everyone, today I zypper up'ped my TW installation, and since then I can't find an applet for the NetworkManager. I can start the (wireless) connection via commandline, though, so the NM service is running. But where's the applet or plasmoid or whatever it is/was gone? It's neither the the system control bar nor can I add it as a mini app on the screen (sorry if I use wrong words here, I'm using the German translation of KDE). What do I miss? BTW, I'm happy that I'm able to have a GUI again, since /usr/bin/krandrstartup was suddenly missing... Regards, Werner --
Il Thu, 19 Nov 2015 13:13:27 +0100, Werner Flamme ha scritto:
I can start the (wireless) connection via commandline, though, so the NM service is running.
Can you check whether "plasma-nm5" is installed or was removed? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.11.2015 um 13:23 schrieb Luca Beltrame:
Il Thu, 19 Nov 2015 13:13:27 +0100, Werner Flamme ha scritto:
I can start the (wireless) connection via commandline, though, so the NM service is running.
Can you check whether "plasma-nm5" is installed or was removed?
# rpm -q plasma-nm5 plasma-nm5-5.4.2-1.1.x86_64 Hm, it is installed. Where should it appear? --
I can start the (wireless) connection via commandline, though, so the NM service is running.
Then KDE Plasma fails, I much prefer to use nm-applet from NetworkManager-gnome package. You can tray nm-appet also: it starts as
2015.11.19 20:15, Werner Flamme rašė: program in system tray, not like mystic „Plasma applet“, and usually works a bit more reliable. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.11.2015 um 19:27 schrieb opensuse.lietuviu.kalba:
I can start the (wireless) connection via commandline, though, so the NM service is running.
Then KDE Plasma fails, I much prefer to use nm-applet from NetworkManager-gnome package. You can tray nm-appet also: it starts as
2015.11.19 20:15, Werner Flamme rašė: program in system tray, not like mystic „Plasma applet“, and usually works a bit more reliable.
NetworkManager-gnome is installed, and I'm used to have an nm icon in the System Tray, but currently, there isn't any nm icon/app available, at least I don't see any. Something I'm missing? # rpm -qa 'libnm-*' | sort libnm-glib4-1.0.6-1.2.x86_64 libnm-glib-vpn1-1.0.6-1.2.x86_64 libnm-gtk0-1.0.6-3.1.x86_64 libnm-util2-1.0.6-1.2.x86_64 # rpm -qa 'NetworkManager*' | sort NetworkManager-1.0.6-1.2.x86_64 NetworkManager-gnome-1.0.6-3.1.x86_64 NetworkManager-gnome-lang-1.0.6-3.1.noarch NetworkManager-lang-1.0.6-1.2.noarch NetworkManager-openconnect-1.0.2-1.1.x86_64 NetworkManager-openconnect-gnome-1.0.2-1.1.x86_64 NetworkManager-openconnect-lang-1.0.2-1.1.noarch NetworkManager-openvpn-1.0.6-1.1.x86_64 NetworkManager-openvpn-gnome-1.0.6-1.1.x86_64 NetworkManager-openvpn-lang-1.0.6-1.1.noarch NetworkManager-pptp-1.0.6-1.1.x86_64 NetworkManager-pptp-gnome-1.0.6-1.1.x86_64 NetworkManager-pptp-lang-1.0.6-1.1.noarch NetworkManager-strongswan-1.3.1-5.1.x86_64 NetworkManager-strongswan-gnome-1.3.1-5.1.x86_64 NetworkManager-strongswan-lang-1.3.1-5.1.noarch NetworkManager-vpnc-1.0.6-1.1.x86_64 NetworkManager-vpnc-gnome-1.0.6-1.1.x86_64 NetworkManager-vpnc-lang-1.0.6-1.1.noarch BTW, no PM, please. I read the list. --
Am 19.11.2015 um 19:27 schrieb opensuse.lietuviu.kalba:
I can start the (wireless) connection via commandline, though, so the NM service is running. Then KDE Plasma fails, I much prefer to use nm-applet from NetworkManager-gnome package. You can tray nm-appet also: it starts as
2015.11.19 20:15, Werner Flamme rašė: program in system tray, not like mystic „Plasma applet“, and usually works a bit more reliable.
NetworkManager-gnome is installed, and I'm used to have an nm icon in the System Tray, but currently, there isn't any nm icon/app available, at least I don't see any.
Something I'm missing?
# rpm -qa 'libnm-*' | sort libnm-glib4-1.0.6-1.2.x86_64 libnm-glib-vpn1-1.0.6-1.2.x86_64 libnm-gtk0-1.0.6-3.1.x86_64 libnm-util2-1.0.6-1.2.x86_64 # rpm -qa 'NetworkManager*' | sort NetworkManager-1.0.6-1.2.x86_64 NetworkManager-gnome-1.0.6-3.1.x86_64 NetworkManager-gnome-lang-1.0.6-3.1.noarch NetworkManager-lang-1.0.6-1.2.noarch NetworkManager-openconnect-1.0.2-1.1.x86_64 NetworkManager-openconnect-gnome-1.0.2-1.1.x86_64 NetworkManager-openconnect-lang-1.0.2-1.1.noarch NetworkManager-openvpn-1.0.6-1.1.x86_64 NetworkManager-openvpn-gnome-1.0.6-1.1.x86_64 NetworkManager-openvpn-lang-1.0.6-1.1.noarch NetworkManager-pptp-1.0.6-1.1.x86_64 NetworkManager-pptp-gnome-1.0.6-1.1.x86_64 NetworkManager-pptp-lang-1.0.6-1.1.noarch NetworkManager-strongswan-1.3.1-5.1.x86_64 NetworkManager-strongswan-gnome-1.3.1-5.1.x86_64 NetworkManager-strongswan-lang-1.3.1-5.1.noarch NetworkManager-vpnc-1.0.6-1.1.x86_64 NetworkManager-vpnc-gnome-1.0.6-1.1.x86_64 NetworkManager-vpnc-lang-1.0.6-1.1.noarch
BTW, no PM, please. I read the list. You might want to try nm-applet from NetworkManager-appindicator, which implements the appindicator protocol rather then the xembed one that many versions of kde don't support. I added this package for enlightenment which also doesn't support xembed anymore. It has some minor disadvantages such as only currently being able to show 1 network and no indication of whether a access point is secured or not from the
On 11/20/2015 05:05 AM, Werner Flamme wrote: popup menu, thats the reason for the separate package. Cheers Simon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Donnerstag, 19. November 2015, 13:13:27 schrieb Werner Flamme:
But where's the applet or plasmoid or whatever it is/was gone? It's neither the the system control bar nor can I add it as a mini app on the screen (sorry if I use wrong words here, I'm using the German translation of KDE).
What do I miss?
That might be the general problem of system tray icons (plasmoids in particular) randomly disappearing in Plasma5's system tray. See here e.g., or the corresponding upstream bug reports (it seems to be a Qt5 problem again). http://bugzilla.opensuse.org/show_bug.cgi?id=955895 Do you see an empty space where the icon should be? If yes, a workaround should be this, as mentioned in the bug report(s): Enter the "System Tray Settings" (via right-clicking on the system tray), turn off the "Miscellaneous" category e.g., press on "Apply", then turn it on again and press on "Apply". The icon should appear then.
BTW, I'm happy that I'm able to have a GUI again, since /usr/bin/krandrstartup was suddenly missing...
That's not used by Plasma5 at all AFAIK. Are/were you still using KDE4 then? Would explain why you only see this problem just now, after upgrading... ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Wolfgang Bauer
Am Donnerstag, 19. November 2015, 13:13:27 schrieb Werner Flamme:
But where's the applet or plasmoid or whatever it is/was gone? It's neither the the system control bar nor can I add it as a mini app on the screen (sorry if I use wrong words here, I'm using the German translation of KDE).
What do I miss?
That might be the general problem of system tray icons (plasmoids in particular) randomly disappearing in Plasma5's system tray.
See here e.g., or the corresponding upstream bug reports (it seems to be a Qt5 problem again). http://bugzilla.opensuse.org/show_bug.cgi?id=955895
Do you see an empty space where the icon should be?
If yes, a workaround should be this, as mentioned in the bug report(s): Enter the "System Tray Settings" (via right-clicking on the system tray), turn off the "Miscellaneous" category e.g., press on "Apply", then turn it on again and press on "Apply". The icon should appear then.
May work for nm but doesn't work for gapcmon :/ tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.11.2015 um 22:58 schrieb Wolfgang Bauer:
Am Donnerstag, 19. November 2015, 13:13:27 schrieb Werner Flamme:
But where's the applet or plasmoid or whatever it is/was gone? It's neither the the system control bar nor can I add it as a mini app on the screen (sorry if I use wrong words here, I'm using the German translation of KDE).
What do I miss?
That might be the general problem of system tray icons (plasmoids in particular) randomly disappearing in Plasma5's system tray.
See here e.g., or the corresponding upstream bug reports (it seems to be a Qt5 problem again). http://bugzilla.opensuse.org/show_bug.cgi?id=955895
Do you see an empty space where the icon should be?
Hm, maybe. There is an odd number of icons visible, and maybe the lower right corner is free to home the NM icon, just in case it is willing to show up...
If yes, a workaround should be this, as mentioned in the bug report(s): Enter the "System Tray Settings" (via right-clicking on the system tray), turn off the "Miscellaneous" category e.g., press on "Apply", then turn it on again and press on "Apply". The icon should appear then.
I'll give this a try as soon as I sit in front of this box again.
BTW, I'm happy that I'm able to have a GUI again, since /usr/bin/krandrstartup was suddenly missing...
That's not used by Plasma5 at all AFAIK. Are/were you still using KDE4 then?
Where would I know? I installed TW when 13.2 was fresh :). Is has been a while, and I applied all updates. I think yes, there are a lot of KDE4 packages left. But due to the checking in openQA, they should fit into the current environment, I think. Some time ago, the file moved from krandr to kscreen, IIRC. kscreen is installed, the file is not present. And "startx" still needs it.
Would explain why you only see this problem just now, after upgrading... ;-)
Not for me, if the relations between packages ("obsoletes", "requires" a.s.o.) are correct :) Werner --
Am Freitag, 20. November 2015, 13:22:21 schrieb Werner Flamme:
Where would I know?
You should be able to tell the difference between the two. Check whether you have kdebase4-workspace or plasma5-workspace installed. You could also have a look in kinfocenter, the Plasma5 version should tell you which version of Plasma you have installed.
I installed TW when 13.2 was fresh :).
Well, when 13.2 was fresh, the default KDE desktop was KDE4. But it has been switched to Plasma5 some time in May IIRC. If you applied all updates, you should be using Plasma5 now.
Is has been a while, and I applied all updates. I think yes, there are a lot of KDE4 packages left. But due to the checking in openQA, they should fit into the current environment, I think.
Yes. Not all KDE4 applications have been ported yet, so it is normal that you still have a lot of KDE4 packages left. But due to the checking in openQA, there should be no file missing either.
Some time ago, the file moved from krandr to kscreen, IIRC. kscreen is installed, the file is not present. And "startx" still needs it.
Nothing "moved". With KDE 4.11 (in openSUSE 13.1 already) kscreen replaced krandr for screen management. And KDE4's startkde (not startx) calls krandrstartup to apply the screen settings on startup, so kscreen contained a dummy script (it uses a daemon for applying the settings). But as I wrote, that is no longer true for Plasma5. krandr is dead, and krandrstartup is no longer called by startkde.
Would explain why you only see this problem just now, after upgrading... ;-) Not for me, if the relations between packages ("obsoletes", "requires" a.s.o.) are correct :)
Well, the question is when you installed updates the last time... ;-) If your system is outdated, the package dependencies would still be ok. Again, if you regularly updated your system, you should have Plasma5 instead of the KDE4 desktop since May, and that one doesn't have nor need krandrstartup. But if you didn't install updates, you shouldn't have had a problem with a missing krandrstartup either. There was a change in the KDE4 dependencies in the Leap development cycle to not require kscreen any more: https://build.opensuse.org/package/rdiff/KDE:Distro:Factory/kdebase4-workspace?linkrev=base&rev=1150 And kscreen (the KDE4 version) has been removed completely because it didn't build any more (or something like that, I don't know). And it's the KDE4 kscreen package (version 1.0.71) that contains krandrstartup which you need to start the KDE4 desktop, so you might have to install krandr manually now or create a dummy krandrstartup script yourself if you want to use KDE4. We probably could add one to the libkscreen package, but the actual configuration module would still be missing. The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5. But that's not supported, you are on your own in that case, and it might stop working completely any time as you noticed. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 20.11.2015 um 14:13 schrieb Wolfgang Bauer: [about krandrstartup]
Some time ago, the file moved from krandr to kscreen, IIRC. kscreen is installed, the file is not present. And "startx" still needs it.
Nothing "moved". With KDE 4.11 (in openSUSE 13.1 already) kscreen replaced krandr for screen management. And KDE4's startkde (not startx) calls krandrstartup to apply the screen settings on startup, so kscreen contained a dummy script (it uses a daemon for applying the settings).
But as I wrote, that is no longer true for Plasma5. krandr is dead, and krandrstartup is no longer called by startkde.
Maybe. I can't login via GUI, though the GUI logon window starts up. It throws me back to the login window (after displaying the console for a fraction of a second) instead of starting my KDE session. So I switch to tty6 via Ctrl-Alt-F6, log in here, and start my GUI via "startx", not with "startkde". And startx does not start anything graphical, but breaks down telling me that /usr/bin/krandrstartup is missing. # rpm -qa '*kscreen*' | sort kscreen5-5.4.2-2.1.x86_64 libkscreen-1.0.5-2.1.x86_64 libkscreen1-1.0.5-2.1.x86_64 libkscreen2-plugin-5.4.2-1.1.x86_64
Would explain why you only see this problem just now, after upgrading... ;-) Not for me, if the relations between packages ("obsoletes", "requires" a.s.o.) are correct :)
Well, the question is when you installed updates the last time... ;-) If your system is outdated, the package dependencies would still be ok.
I started the thread on November 19, so that was the day I did the last updates.
Again, if you regularly updated your system, you should have Plasma5 instead of the KDE4 desktop since May, and that one doesn't have nor need krandrstartup. But if you didn't install updates, you shouldn't have had a problem with a missing krandrstartup either.
I did install all available updates, and I do have a problem with (ahem, without ;)) /usr/bin/krandrstartup.
There was a change in the KDE4 dependencies in the Leap development cycle to not require kscreen any more: https://build.opensuse.org/package/rdiff/KDE:Distro:Factory/kdebase4-workspace?linkrev=base&rev=1150
And kscreen (the KDE4 version) has been removed completely because it didn't build any more (or something like that, I don't know). And it's the KDE4 kscreen package (version 1.0.71) that contains krandrstartup which you need to start the KDE4 desktop, so you might have to install krandr manually now or create a dummy krandrstartup script yourself if you want to use KDE4. We probably could add one to the libkscreen package, but the actual configuration module would still be missing.
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30. # rpm -f $(which startx) xinit-1.3.4-6.2.x86_64 # rpm -qf $(which startkde) plasma5-workspace-5.4.2-2.1.x86_64 startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server. The settings: # grep ^[^#] /etc/sysconfig/displaymanager DISPLAYMANAGER="kdm" DISPLAYMANAGER_REMOTE_ACCESS="no" DISPLAYMANAGER_ROOT_LOGIN_REMOTE="no" DISPLAYMANAGER_STARTS_XSERVER="yes" DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no" DISPLAYMANAGER_AUTOLOGIN="" DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" DISPLAYMANAGER_AD_INTEGRATION="no" DISPLAYMANAGER_SHUTDOWN="auto" DISPLAYMANAGER_XSERVER="Xorg" KDM_USERS="" KDM_GREETSTRING="" DISPLAYMANAGER_KDM_LOCALARGS="" DISPLAYMANAGER_KDM_THEME="openSUSE" DISPLAYMANAGER_ROOT_LOGIN_LOCAL="yes"
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
But that's not supported, you are on your own in that case, and it might stop working completely any time as you noticed.
# grep 'solvable_name:' /etc/zypp/locks solvable_name: gtk3-immodule-vietnamese solvable_name: gtk2-immodule-thai solvable_name: gtk2-immodule-vietnamese solvable_name: gtk3-immodule-amharic solvable_name: gtk3-immodule-inuktitut solvable_name: gtk3-immodule-thai solvable_name: gtk2-immodule-amharic solvable_name: gtk2-immodule-inuktitut solvable_name: yast2-nis-client solvable_name: apper solvable_name: ypbind Regards, Werner --
Am Freitag, 20. November 2015, 20:25:59 schrieb Werner Flamme:
So I switch to tty6 via Ctrl-Alt-F6, log in here, and start my GUI via "startx", not with "startkde". And startx does not start anything graphical, but breaks down telling me that /usr/bin/krandrstartup is missing.
startx starts an X session. OTOH startkde starts the KDE desktop and has to be run in an existing X session. startx takes the command to run from the environment variable $WINDOWMANAGER (if you run it without arguments). To what is this set? But startx cannot be run as user at all with the default setup.
I started the thread on November 19, so that was the day I did the last updates.
And since then you cannot login to KDE?
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30.
AFAIK Felix Miata uses/used KDE4. And for that you do need krandrstartup.
# rpm -qf $(which startkde) plasma5-workspace-5.4.2-2.1.x86_64
Ok, so you have Plasma5 installed. But is the startkde unmodified? rpm -V plasma5-workspace
startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server.
As written before, you can only run startkde inside an already existing X session.
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
No. Plasma5's startkde does *not* (and never did) use or need krandrstartup. If it would, all fresh Tumbleweed and Leap installations would be broken, as krandrstartup doesn't exist there. If your startkde tries to run krandrstartup, you somehow use the KDE4 version, i.e. your installation is/was broken. Btw, I did fix KDE4's kscreen a month ago, but completely forgot about it (and I haven't noticed upto now that it actually has been removed from Factory). I can submit the fixed package to KDE:Distro:Factory, but I don't know what the maintainers would think about adding it back to Factory/Tumbleweed... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 20. November 2015, 22:27:12 schrieb Wolfgang Bauer:
Btw, I did fix KDE4's kscreen a month ago, but completely forgot about it (and I haven't noticed upto now that it actually has been removed from Factory).
I can submit the fixed package to KDE:Distro:Factory, but I don't know what the maintainers would think about adding it back to Factory/Tumbleweed...
Forgot to mention: In case anybody wants to have/needs this package, it's available here: http://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Fra... As already indicated, the package contains a dummy krandrstartup script that's necessary to start the KDE4 desktop session, and it contains the kscreen display configuration module (systemsettings/"Configure KDE4 Applications"-
Display and Monitor->Display Configuration).
But again, you only need it for KDE4, not Plasma5. And it cannot be installed in parallel with the Plasma5 version, kscreen5. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Wolfgang Bauer composed on 2015-11-20 22:27 (UTC+0100):
AFAIK Felix Miata uses/used KDE4.
I use "KDE": 3, 4, 5 & TDE. 3 enjoys 24/7 uptime, the rest, collectively far less. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 20. November 2015, 17:10:43 schrieb Felix Miata:
Wolfgang Bauer composed on 2015-11-20 22:27 (UTC+0100):
AFAIK Felix Miata uses/used KDE4.
I use "KDE": 3, 4, 5 & TDE.
Ok, but that does include KDE4. And when you encountered the problem with a missing krandrstartup (and suggested the workaround to install krandr), you must have tried to login to KDE4. As I wrote a few times already, only the KDE4 desktop uses/needs krandrstartup. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il Fri, 20 Nov 2015 22:27:12 +0100, Wolfgang Bauer ha scritto:
I can submit the fixed package to KDE:Distro:Factory, but I don't know what the maintainers would think about adding it back to Factory/Tumbleweed...
As one of the proponents of the removal of kscreen 4.x (not the library, which is instead used by software like Okular), I can tell already that at least in my opinion, such a proposal would get a -1. Since the officially supported version for TW and Leap is Plasma 5, I see no reason to add a runtime component that'll be totally unused by the default desktop. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Wolfgang Bauer [20.11.2015 22:27]:
Am Freitag, 20. November 2015, 20:25:59 schrieb Werner Flamme:
So I switch to tty6 via Ctrl-Alt-F6, log in here, and start my GUI via "startx", not with "startkde". And startx does not start anything graphical, but breaks down telling me that /usr/bin/krandrstartup is missing.
startx starts an X session. OTOH startkde starts the KDE desktop and has to be run in an existing X session.
startx takes the command to run from the environment variable $WINDOWMANAGER (if you run it without arguments). To what is this set?
In /etc/sysconfig/windowmanager, KDE is configured.
But startx cannot be run as user at all with the default setup.
That's right, but I wrote a file to /etc/permissions.d, which causes /usr/bin/Xorg set 4755, so I can start X as a user.
I started the thread on November 19, so that was the day I did the last updates.
And since then you cannot login to KDE?
Long ago. First time I wrote about that on this list was 2015-03-31 in posting <551A7866.7020405@ufz.de>, Subject "Re: [opensuse-factory] [TW-20150328]". But not being able to login seems to be related to PAM, not to KDE. The Logon window appears, but the Login is rejected. Now, there was not even that Login Screen.
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30.
AFAIK Felix Miata uses/used KDE4. And for that you do need krandrstartup.
However, his reply was about a user having "Plasma".
# rpm -qf $(which startkde) plasma5-workspace-5.4.2-2.1.x86_64
Ok, so you have Plasma5 installed. But is the startkde unmodified? rpm -V plasma5-workspace
I'll try when I'm in front of that Laptop again. I cannot remember to modify or replace startkde. Currently, I'm in front of a Fujitsu Esprimo (in the office) running 13.2, at home there is one Thinkpad 61p running TW and one Thinkpad 420 running Leap.
startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server.
As written before, you can only run startkde inside an already existing X session.
So the setting 'DISPLAYMANAGER_STARTS_XSERVER="yes"' in /etc/sysconfig/displaymanager is just there to raise confusion?
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
No.
Why do you say that it cannot occur under other circumstances than locking kdebase4-workspace and actively blocking the installation of Plasma5? I do and did none of that, and though I have that problem. So, for me it is obvious that there are other circumstances possible.
Plasma5's startkde does *not* (and never did) use or need krandrstartup. If it would, all fresh Tumbleweed and Leap installations would be broken, as krandrstartup doesn't exist there.
The output of "rpm -qf $(which startkde)" showed you that there is Plama5 installed. And I never copied another startkde from elsewhere to replace that startkde script that is in the system. Nor did I edit this file.
If your startkde tries to run krandrstartup, you somehow use the KDE4 version, i.e. your installation is/was broken.
Obviously, though a "grep -i randr $(which startkde)" shows no output. The same is valid for "grep -i randr $(which startx)". However, I have a line in .xsession-errors stating that the session ends (before any graphic mode was reached) because /usr/bin/krandrstartup wasn't found. Regards, Werner --
Am Montag, 23. November 2015, 09:46:31 schrieb Werner Flamme:
startx takes the command to run from the environment variable $WINDOWMANAGER (if you run it without arguments). To what is this set?
In /etc/sysconfig/windowmanager, KDE is configured.
"KDE" is not valid there. It should either be "kde-plasma" or "plasma5". But my actual question was what $WINDOWMANAGER is set to. startx only takes DEFAULT_WM from /etc/sysconfig/windowmanager when $WINDOWMANAGER is not defined, but even in this case it would set $WINDOWMANAGER appropriately. So posting the value of $WINDOWMANAGER would show what startx *really* runs.
But startx cannot be run as user at all with the default setup.
That's right, but I wrote a file to /etc/permissions.d, which causes /usr/bin/Xorg set 4755, so I can start X as a user.
Good, then it should work as user too.
I started the thread on November 19, so that was the day I did the last updates.
And since then you cannot login to KDE?
Long ago. First time I wrote about that on this list was 2015-03-31 in posting <551A7866.7020405@ufz.de>, Subject "Re: [opensuse-factory] [TW-20150328]".
Back then, KDE4 was the default KDE desktop in Tumbleweed, and yes, this needs (needed) krandrstartup. But back then this problem didn't exist as the KDE4 desktop was still officially supported, and it required kscreen which of course still existed as well and did contain (a dummy) krandrstartup. The problem with the missing krandrstartup only started about a month ago, because kscreen and the dependency on it was removed..
But not being able to login seems to be related to PAM, not to KDE. The Logon window appears, but the Login is rejected. Now, there was not even that Login Screen.
A broken PAM setup can definitely break login too, yes. But a missing login screen is a completely different problem again. The login screen doesn't use krandrstartup either. Maybe you should start afresh and actually explain your exact problems.
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30.
AFAIK Felix Miata uses/used KDE4. And for that you do need krandrstartup.
However, his reply was about a user having "Plasma".
"Plasma" is the name of KDE's desktop since version 4.0 eight years ago. So yes, somebody who runs the KDE4 desktop *is* a user having "Plasma". Plasma5 is the latest generation of KDE's desktop, it is based on Qt5 (instead of Qt4), KDE Frameworks 5 (instead of kdelibs4), and again, it doesn't use nor need krandrstartup because krandr has been removed completely.
startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server.
As written before, you can only run startkde inside an already existing X session.
So the setting 'DISPLAYMANAGER_STARTS_XSERVER="yes"' in /etc/sysconfig/displaymanager is just there to raise confusion?
Don't mix up things, please. This option is completely irrelevant here. If you are in text mode, there is no display manager running, obviously. And startkde is no display manager either, it's a shell script that starts all necessary components of a KDE desktop. And as mentioned, it needs to have an Xserver already running. Just in case you don't know, the display manager is the Login Screen.
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
No.
Why do you say that it cannot occur under other circumstances than locking kdebase4-workspace and actively blocking the installation of Plasma5?
Again, because Plasma5 doesn't use nor need krandrstartup, krandrstartup is not even available any more. If krandrstartup would still be required, *all* fresh Leap and Tumbleweed installations would be broken as I already mentioned, and this would definitely be caught by openQA too.
I do and did none of that, and though I have that problem. So, for me it is obvious that there are other circumstances possible.
I don't know what you do or did. But this is not possible with Plasma5 in *any* circumstance. If your startkde script runs krandrstartup (and fails because of that not existing), you are not using Plasma5's startkde script. I repeat: A Plasma5 installation doesn't contain krandrstartup, and nothing in the Xorg or Plasma5 startup process runs krandrstartup
Plasma5's startkde does *not* (and never did) use or need krandrstartup. If it would, all fresh Tumbleweed and Leap installations would be broken, as krandrstartup doesn't exist there.
The output of "rpm -qf $(which startkde)" showed you that there is Plama5 installed.
Yes, it did. But the startkde script in the package plasma5-workspace does not even mention the word "krandr". If your Plasma5 session doesn't start without krandrstartup, something is broken with your installation. Try reinstalling plasma5-workspace to make sure you use the original, unmodified, Plasma5 startkde script. sudo zypper in -f plasma5-workspace Although your grep below seems to indicate that startkde is ok anyway.
And I never copied another startkde from elsewhere to replace that startkde script that is in the system. Nor did I edit this file.
Well, you might have restored it from an older backup or snapshot by mistake. How should I know?
If your startkde tries to run krandrstartup, you somehow use the KDE4 version, i.e. your installation is/was broken.
Obviously, though a "grep -i randr $(which startkde)" shows no output. The same is valid for "grep -i randr $(which startx)".
So startkde does not run krandrstartup obviously. And it's clear that startx doesn't, because startx is independent of KDE. Well then, if it's really a missing krandrstartup that causes your desktop failing to start, if must be run by some other script in the startup process (which is not done on a standard installation). Check the xinit scripts in /etc/X11/xinit/ and the .xinitrc in your home folder (if it exists). grep -R randr /etc/X11/xinit/ ~/.xinitrc Btw, does it work without krandrstartup on a fresh user account? Then the problem would rather have to be looked for in your home folder, not your installation.
However, I have a line in .xsession-errors stating that the session ends (before any graphic mode was reached) because /usr/bin/krandrstartup wasn't found.
And what's the timestamp of the file? .xsession-errors is not used any more, it should rather be called .xsession- errors-:0, or depending on which displaymanager you use, the logs might (only) go to systemd's journal. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Wolfgang Bauer [23.11.2015 16:40]:
Am Montag, 23. November 2015, 09:46:31 schrieb Werner Flamme:
startx takes the command to run from the environment variable $WINDOWMANAGER (if you run it without arguments). To what is this set?
In /etc/sysconfig/windowmanager, KDE is configured.
"KDE" is not valid there. It should either be "kde-plasma" or "plasma5".
I did not put "KDE" there. I'm not a complete idiot, though it may seem so. Since I can't see into the file right then, I only wanted to give the impression that there is no "gnome" or whatever.
But my actual question was what $WINDOWMANAGER is set to.
startx only takes DEFAULT_WM from /etc/sysconfig/windowmanager when $WINDOWMANAGER is not defined, but even in this case it would set $WINDOWMANAGER appropriately. So posting the value of $WINDOWMANAGER would show what startx *really* runs.
I'll do when I'm starting this Laptop next time. The WINDOWMANAGER variable is set in non-GUI mode also, right? On my 13.2 office pc it is set to "/usr/bin/startkde".
But startx cannot be run as user at all with the default setup.
That's right, but I wrote a file to /etc/permissions.d, which causes /usr/bin/Xorg set 4755, so I can start X as a user.
Good, then it should work as user too.
It does. I *can* start X as a user :)
I started the thread on November 19, so that was the day I did the last updates.
And since then you cannot login to KDE?
Long ago. First time I wrote about that on this list was 2015-03-31 in posting <551A7866.7020405@ufz.de>, Subject "Re: [opensuse-factory] [TW-20150328]".
Back then, KDE4 was the default KDE desktop in Tumbleweed, and yes, this needs (needed) krandrstartup. But back then this problem didn't exist as the KDE4 desktop was still officially supported, and it required kscreen which of course still existed as well and did contain (a dummy) krandrstartup.
The problem with the missing krandrstartup only started about a month ago, because kscreen and the dependency on it was removed..
My problem back then had absolutely nothing to do with krandrstartup.
But not being able to login seems to be related to PAM, not to KDE. The Logon window appears, but the Login is rejected. Now, there was not even that Login Screen.
A broken PAM setup can definitely break login too, yes.
I know. I fought with pam_mount for years. You'll find my posts on various openSUSE lists, or even before (SUSE mailing lists). SUSE was the recommended Linux distro in our company before our boss decided we had to support Ubuntu instead.
But a missing login screen is a completely different problem again. The login screen doesn't use krandrstartup either.
Maybe you should start afresh and actually explain your exact problems.
Ahem... I did. The problem was the non-appearnace of any Icon or applet or plasmoid or anything for NetWorkManager. That's why this thread got the Subject line it still has. This problem is solved. Only a "BTW" at the end of the OP referred to the file /usr/bin/krandrstartup. I never knew it existed until I found in my .~/xsession-errors file that it was missing, and thus my GUI did not start.
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30.
AFAIK Felix Miata uses/used KDE4. And for that you do need krandrstartup.
However, his reply was about a user having "Plasma".
"Plasma" is the name of KDE's desktop since version 4.0 eight years ago. So yes, somebody who runs the KDE4 desktop *is* a user having "Plasma".
Plasma5 is the latest generation of KDE's desktop, it is based on Qt5 (instead of Qt4), KDE Frameworks 5 (instead of kdelibs4), and again, it doesn't use nor need krandrstartup because krandr has been removed completely.
startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server.
As written before, you can only run startkde inside an already existing X session.
So the setting 'DISPLAYMANAGER_STARTS_XSERVER="yes"' in /etc/sysconfig/displaymanager is just there to raise confusion?
Don't mix up things, please. This option is completely irrelevant here.
If you are in text mode, there is no display manager running, obviously.
And startkde is no display manager either, it's a shell script that starts all necessary components of a KDE desktop. And as mentioned, it needs to have an Xserver already running.
Just in case you don't know, the display manager is the Login Screen.
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
No.
Why do you say that it cannot occur under other circumstances than locking kdebase4-workspace and actively blocking the installation of Plasma5?
Again, because Plasma5 doesn't use nor need krandrstartup, krandrstartup is not even available any more.
Well, after installing the krandr package I found a file /usr/bin/krandrstartup on my disk, and the GUI started again.
If krandrstartup would still be required, *all* fresh Leap and Tumbleweed installations would be broken as I already mentioned, and this would definitely be caught by openQA too.
I do and did none of that, and though I have that problem. So, for me it is obvious that there are other circumstances possible.
I don't know what you do or did. But this is not possible with Plasma5 in *any* circumstance.
If your startkde script runs krandrstartup (and fails because of that not existing), you are not using Plasma5's startkde script.
I repeat: A Plasma5 installation doesn't contain krandrstartup, and nothing in the Xorg or Plasma5 startup process runs krandrstartup
Plasma5's startkde does *not* (and never did) use or need krandrstartup. If it would, all fresh Tumbleweed and Leap installations would be broken, as krandrstartup doesn't exist there.
The output of "rpm -qf $(which startkde)" showed you that there is Plama5 installed.
Yes, it did. But the startkde script in the package plasma5-workspace does not even mention the word "krandr".
If your Plasma5 session doesn't start without krandrstartup, something is broken with your installation. Try reinstalling plasma5-workspace to make sure you use the original, unmodified, Plasma5 startkde script.
sudo zypper in -f plasma5-workspace
Although your grep below seems to indicate that startkde is ok anyway.
Thanks for noticing. And please do not believe that I did not reinstall plasma5-workspace and plasma5-session and plasma5-desktop and whatnot.
And I never copied another startkde from elsewhere to replace that startkde script that is in the system. Nor did I edit this file.
Well, you might have restored it from an older backup or snapshot by mistake. How should I know?
You know by me telling you. You have no other way. I never had to restore a backup to a system partition.
If your startkde tries to run krandrstartup, you somehow use the KDE4 version, i.e. your installation is/was broken.
Obviously, though a "grep -i randr $(which startkde)" shows no output. The same is valid for "grep -i randr $(which startx)".
So startkde does not run krandrstartup obviously. And it's clear that startx doesn't, because startx is independent of KDE.
Well then, if it's really a missing krandrstartup that causes your desktop failing to start, if must be run by some other script in the startup process (which is not done on a standard installation). Check the xinit scripts in /etc/X11/xinit/ and the .xinitrc in your home folder (if it exists).
grep -R randr /etc/X11/xinit/ ~/.xinitrc
Btw, does it work without krandrstartup on a fresh user account? Then the problem would rather have to be looked for in your home folder, not your installation.
However, I have a line in .xsession-errors stating that the session ends (before any graphic mode was reached) because /usr/bin/krandrstartup wasn't found.
And what's the timestamp of the file?
It was the current timestamp, and the file was very short.
.xsession-errors is not used any more, it should rather be called .xsession- errors-:0, or depending on which displaymanager you use, the logs might (only) go to systemd's journal.
Ah - those were symlinked, I remember. And sysstemd's jornal will hopefully reach it through to the standard syslog, won't it? Many messages are passed by, so I hope I find display messages in /var/log/messages too (/var/log/Xorg.0.log and /var/log/Xorg.1.log do not show errors, just a clean shutdown). Regards, Werner --
Am Dienstag, 24. November 2015, 08:24:43 schrieb Werner Flamme:
But my actual question was what $WINDOWMANAGER is set to.
startx only takes DEFAULT_WM from /etc/sysconfig/windowmanager when $WINDOWMANAGER is not defined, but even in this case it would set $WINDOWMANAGER appropriately. So posting the value of $WINDOWMANAGER would show what startx *really* runs. I'll do when I'm starting this Laptop next time. The WINDOWMANAGER variable is set in non-GUI mode also, right?
Yes. /etc/profile.d/profile.sh sets it too (by evaluating /etc/sysconfig/displaymanager)..
I started the thread on November 19, so that was the day I did the last updates.
And since then you cannot login to KDE?
Long ago. First time I wrote about that on this list was 2015-03-31 in posting <551A7866.7020405@ufz.de>, Subject "Re: [opensuse-factory] [TW-20150328]".
Back then, KDE4 was the default KDE desktop in Tumbleweed, and yes, this needs (needed) krandrstartup. But back then this problem didn't exist as the KDE4 desktop was still officially supported, and it required kscreen which of course still existed as well and did contain (a dummy) krandrstartup.
The problem with the missing krandrstartup only started about a month ago, because kscreen and the dependency on it was removed..
My problem back then had absolutely nothing to do with krandrstartup.
Obviously, that's what I wrote. But you mentioned that you had similar problems back then...
But a missing login screen is a completely different problem again. The login screen doesn't use krandrstartup either.
Maybe you should start afresh and actually explain your exact problems.
Ahem... I did.
The problem was the non-appearnace of any Icon or applet or plasmoid or anything for NetWorkManager. That's why this thread got the Subject line it still has. This problem is solved.
Yes, but we are talking about your desktop not starting without krandrstartup now. (probably the subject line should be changed...) And then you suddenly mentioned that you don't get a login screen either. So I'm not completely sure any more what your actual problems are in this regard. In particular: is this also related to krandrstartup missing, or does this happen even if it's there?
Only a "BTW" at the end of the OP referred to the file /usr/bin/krandrstartup. I never knew it existed until I found in my .~/xsession-errors file that it was missing, and thus my GUI did not start.
But a last time: krandrstartup is only used by the KDE4 desktop. Nothing in a standard Plasma5 installation uses it. If Plasma5 doesn't start without it, something is wrong on your system. Or, in other words, if
I installed krandr. Felix Miata proposed that in <56332B7A.2060802@earthlink.net> on October, 30.
AFAIK Felix Miata uses/used KDE4. And for that you do need krandrstartup.
However, his reply was about a user having "Plasma".
"Plasma" is the name of KDE's desktop since version 4.0 eight years ago. So yes, somebody who runs the KDE4 desktop *is* a user having "Plasma".
Plasma5 is the latest generation of KDE's desktop, it is based on Qt5 (instead of Qt4), KDE Frameworks 5 (instead of kdelibs4), and again, it doesn't use nor need krandrstartup because krandr has been removed completely.
startkde, started on tty6, gives me $DISPLAY is not set or cannot connect to the X server.
As written before, you can only run startkde inside an already existing X session.
So the setting 'DISPLAYMANAGER_STARTS_XSERVER="yes"' in /etc/sysconfig/displaymanager is just there to raise confusion?
Don't mix up things, please. This option is completely irrelevant here.
If you are in text mode, there is no display manager running, obviously.
And startkde is no display manager either, it's a shell script that starts all necessary components of a KDE desktop. And as mentioned, it needs to have an Xserver already running.
Just in case you don't know, the display manager is the Login Screen.
The problem you described can only happen if you locked kdebase4-workspace and actively blocked the installation of Plasma5.
Obviously, it can occur under other circumstances too.
No.
Why do you say that it cannot occur under other circumstances than locking kdebase4-workspace and actively blocking the installation of Plasma5?
Again, because Plasma5 doesn't use nor need krandrstartup, krandrstartup is not even available any more.
Well, after installing the krandr package I found a file /usr/bin/krandrstartup on my disk, and the GUI started again.
Of course. krandr contains krandrstartup, as krandrstartup is the tool to apply krandr's settings. But a last time: krandrstartup is only used by the KDE4 desktop. Nothing in a standard Plasma5 installation (or even in the whole distribution, except for kdebase4-workspace, of which krandr is actually a part of) uses it, because krandr doesn't exist any more (it was unmaintained since years already anyway, and replaced by kscreen). If Plasma5 doesn't start without it, something is wrong on your system. Or, in other words, if something on your system needs krandrstartup, it cannot come from a current openSUSE package. So, you should find out *what* exactly wants to run krandrstartup, and remove/fix that. E.g. the grep line I suggested would be a first start. Installing krandr is the wrong workaround. It might even break/override your Plasma5/kscreen5 display settings...
And I never copied another startkde from elsewhere to replace that startkde script that is in the system. Nor did I edit this file.
Well, you might have restored it from an older backup or snapshot by mistake. How should I know?
You know by me telling you. You have no other way. I never had to restore a backup to a system partition.
Yeah, but you didn't tell that until now. Just because you didn't mention it, doesn't rule it out. It would have been one possibility why you would have an outdated startkde on your system. And krandrstartup is (only) being called by KDE4's startkde to apply the display settings on login. So having an outdated (KDE4) startkde was the most obvious reason IMHO. But meanwhile it is clear that your startkde is ok, anyway...
.xsession-errors is not used any more, it should rather be called .xsession- errors-:0, or depending on which displaymanager you use, the logs might (only) go to systemd's journal.
Ah - those were symlinked, I remember. And sysstemd's jornal will hopefully reach it through to the standard syslog, won't it? Many messages are passed by, so I hope I find display messages in /var/log/messages too (/var/log/Xorg.0.log and /var/log/Xorg.1.log do not show errors, just a clean shutdown).
If you have a syslog daemon running, it should get forwarded to /var/log/messages, yes. But there's not much difference whether you browse the huge messages file or the systemd log I suppose. Hint: run journalctl -b to only get the entries from the current boot. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.11.2015 um 13:13 schrieb Werner Flamme:
Hi everyone,
today I zypper up'ped my TW installation, and since then I can't find an applet for the NetworkManager.
The thingy is back :) The session management decided to throw away all my session data and start with a blank screen instead of my last session. Now an NM icon is shown in the lower right corner, where it once used to be :) Regards, and thanks for all the help, Werner --
participants (7)
-
Felix Miata -
Luca Beltrame -
opensuse.lietuviu.kalba -
Patrick Shanahan -
Simon Lees -
Werner Flamme -
Wolfgang Bauer