[Bug 1187478] New: Suddenly, cannot launch YaST2 because won't launch with root permissions
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 Bug ID: 1187478 Summary: Suddenly, cannot launch YaST2 because won't launch with root permissions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: tonysu@su-networking.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Although am setting this as an openSUSE 14.2 problem, I also noticed this happening on 15.3 so don't believe this is an OS problem. As recently as yesterday, it was possible to launch YAST2 from the menu, but now cannot on both a 15.2 and a newly installed and updated 15.3. At first, noticed trying to install an app using One Click Install on to the 15.3 machine, and the install failed because root permissions not set. Then, noticed the same problem unable to launch YAST2 on a 15.2 from the menu... Was able to enter credentials but then failed saying that root permissions required. Of course in the case of the 15.2 machine I could get around the problem by launching from a root console. This all seems to have happened within the past 24 hours. In both cases the machines were freshly updated. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c1 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa@suse.com, | |tonysu@su-networking.com Flags| |needinfo?(tonysu@su-network | |ing.com) --- Comment #1 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- Hi Tony, I have tried a freshly updated openSUSE 15.3 and it worked just fine. I would need more details to debug your problem. What desktop environment are you using? Could you attach the output of "journalctl -xn" after trying to run YasT from the menu? Could you even try running 'xdg-su -c "/sbin/yast2"' from a terminal (in graphical mode)? What's the output? Thanks in advance! Regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c2 --- Comment #2 from Tony Su <tonysu@su-networking.com> --- The problem is not in a newly installed 15.3, I have tested that environment twice now without a problem. The problem is in a 15.2 upgraded to a 15.3, there seems to be a difference between that environment and a newly installed 15.3. Should not matter what install source you use To install 15.2 with LXQt as the "original and only" Desktop, you can follow the screens I posted in my openSUSE presentation https://slides.com/tonysu/opensuse/ Be certain to select "Activate online repositories when prompted https://slides.com/tonysu/opensuse/#/5 On the "System Role" screen, select "Generic Desktop" as shown https://slides.com/tonysu/opensuse/#/6 On the "Installation Settings" screen, click on "Software" hyperlink https://slides.com/tonysu/opensuse/#/10 The following YaST Software Manager screen will display with the default "Patterns" view. Select the LXQt pattern and then click "OK" until you can continue the installation and then let the installation run https://slides.com/tonysu/opensuse/#/12 The result should be a 15.2 with LXQt as the first and only Desktop installed. It's possible you will see the openSUSE default wallpaper instead of the LXQt default wallpaper, but that's not important for what you'll be doing. If it bothers someone, you can go into the LXQt settings and Appearance and LXQt Themes and set the default path correctly (which is not possible with the newest LXQt on both 15.2 and 15.3). Until you update the system which may or may not have happened, this setting may or may not be available to you but definitely will not be an option after you've run the following command. Next step is to upgrade the system with the standard zypper command Assumes that the repositories problems earlier this week have been resolved and propagated. zypper up **************************************** Now install the games and Packman repositories, which you can do with the following command zypper ar -f http://download.opensuse.org/repositories/games/openSUSE_Leap_15.2/ games zypper ar -f https://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.2/ Packman Update and upgrade your system to Packman with the following command, and if prompted to change vendor, select the option to change vendor to Packman for every option zypper dup --from Packman When complete, verify system is updated. No further updates should be required for 15.2, but interestingly I found this was necessary in a 15.3(later). zypper up Install Angband zypper in angband Verify Angband launches by selecting the X11 version from the application launch menu (games category). You only need to view the splash screen, then press a key to start the character setup and go no further. At this point, you should have a fully updated 15.2 with Angband installed. *************************************** To execute the upgrade, Modify all repositories to use the releasever variable by running the following command sudo sed -i 's/15.2/${releasever}/g' /etc/zypp/repos.d/*.repo Verify the contents of any repository to verify the change using the releasever variable. If the following doesn't work, it means your repos are named differently so you'll have to use a repo name on your system. cat /etc/zypp/repos.d/repo-update.repo Refresh your zypper cache with 15.3 data zypper --releasever=15.3 ref Disable the Packman and games repos, the following command assumes you added these repos with the above commands. If you added the Packman repo using some other way like YaST Repositories Manager, Packman might be called "Packman_repository" or something else zypper mr --disable games Packman Execute the upgrade, when prompted always select the option to change vendor from Packman to SUSE(be careful, will not always be the first option, unknown why). zypper --releasever=15.3 dup Execute a system update, unknown at this time why this may be required on 15.3 and never on any prior version of openSUSE. zypper up Enable only the games repository. Although normally I would enable Packman as well, you may want to delay so you can test installing and running Angband in an environment without Packman first, and then add and test with Packman as well later. zypper mr --enable games But, do not install Angband immediately! Instead go to the software install website and start the One Click Install of Angband and note the long list of compatibility repos to be installed https://software.opensuse.org/package/angband?search_term=angband The One-Click Install link follows https://software.opensuse.org/ymp/games/openSUSE_Leap_15.3/angband.ymp?base=openSUSE%3ALeap%3A15.3&query=angband Note that unless and until an odd bug that just appeared which doesn't run YaST Software Manager with elevated permissions is fixed, you may find it difficult to proceed... the One Click Install won't work and on your system, YaST won't launch after entering root credentials... You can launch YaST only from a root console. The only other option is to enter that long list of repos manually using zypper commands. But if One Click Install works for you, then great! Proceed and install Angband, launch Angband X11 from the menu and test whether it displays the splash (it should) and then tap your spacebar to see if the game proceeds to set up a character (It shouldn't, it should crash silently). At this point, you should have gone as far as I've gone... I don't know if the long list of compatibility repos should fix whatever problem exist, but the Angband app doesn't launch for me. Since at this point Packman hasn't been enabled, I don't think it's a relevant factor (but could be so I included. Note first error thrown in this report which suggested some kind of ALSA/Pulseaudio problem and may still be an issue despite no errors thrown recently). Unless I've made a mistake, I'm pretty sure the problem is not in Angband itself or Packman although I haven't been able to confirm with additional test runs because of the YaST permissions problem I described... I think the problem is some difference between an upgraded 15.2>15.3 vs a newly installed 15.3. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c3 --- Comment #3 from Tony Su <tonysu@su-networking.com> --- Oops. Posted the wrong comment to this bug. But, answering the question, LXQt is the Desktop and installed as described. Everything else in the post is probably irrelevant to this bug -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c4 --- Comment #4 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- Hi Tony, No problem. Just, please, attach the information I asked for in comment 1 when you have time. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c5 --- Comment #5 from Tony Su <tonysu@su-networking.com> --- I started seeing the problem only recently in two machines, one running 15.2 and the other 15.3 both running LXQt. I have the 15.2 machine in front of me having this problem. I have been capturing all journal messages during an attempt to launch YaST2 from the menu (journalctl -n) and see nothing written at all. The following is the output from running xdg-su. Maybe you see something unusual, but the part about User 1000 not owned by UID 0 is usual and also displays when I launch from a root console. # xdg-su -c "/sbin/yast2" QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 100 lxqt-sudo: Stripping child environment except for: DISPLAY, LANG, LANGUAGE, LC_ADDRESS, LC_ALL, LC_COLLATE, LC_CTYPE, LC_IDENTIFICATION, LC_MEASUREMENT, LC_MESSAGES, LC_MONETARY, LC_NAME, LC_NUMERIC, LC_PAPER, LC_TELEPHONE, LC_TIME, PATH, QT_PLATFORM_PLUGIN, QT_QPA_PLATFORMTHEME, WAYLAND_DISPLAY, XAUTHLOCALHOSTNAME, XAUTHORITY QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' I can run same tests on the 15.3 machine tomorrow, but the observed behavior is identical to this 15.2 machine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c6 --- Comment #6 from Tony Su <tonysu@su-networking.com> --- I had forgotten I have a newly installed and updated 15.3 in my machine inventory where I am. I just ran the same tests and returned the exact same results I posted for 15.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c8 --- Comment #8 from Tony Su <tonysu@su-networking.com> --- Thx for the update. Yes, might be LXQt specific since this problem seemed to happen nearly all at the same time on a 15.2, 15.2 > 15.3 upgrade and on a 15.3, all running LXQt. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 http://bugzilla.opensuse.org/show_bug.cgi?id=1187478#c11 Shawn Dunn <sfalken@cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Shawn Dunn <sfalken@cloverleaf-linux.org> --- This bug is fixed in both 15.4 and Tumbleweed, to the best of my ability to test. There are still issues with directly launching the yast submodules from the menu, but not yast itself. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com