[Bug 1120397] New: I Cannot launch YaST modules from the LXQt programs menu
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397 Bug ID: 1120397 Summary: I Cannot launch YaST modules from the LXQt programs menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: trcs@gmx.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When I click any of the YaST modules menu entries in the programs menu, nothing happens. The only one working is YaST Control Center, and from there the modules can be launch without issues. I think it is something related to quotes because it works fine if I remove the quotes around $cmd in the line $LXQTSU -s "$cmd" of the su_lxqt() function in the /usr/bin/xdg-su script. The LXQt sudo dialog shows a different quotation around the command when I remove the aforementioned quotes. For example: Command: '/sbin/yast2 sound' → xdg-su not modified, it doesn't work Command: '/sbin/yast2' 'sound' → xdg-su modified, it works Following with the example, if I run the command of the Exec key in YaST2/sound.desktop (xdg-su -c "/sbin/yast2 sound") from the terminal, I get the following error: bash: /sbin/yast2 sound: No such file or directory If I use the X11:LXQt:git repository the problem remains, YaST modules menu entries don't work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c5
--- Comment #5 from jc sl
If this has broken recently I'm guessing it could be due to changes in the new bash, xdg-utils haven't been updated for quite some time.
It was broken long before the update. In fact, it may have been broken forever. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c7
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c10
--- Comment #10 from jc sl
I reassign this to maintenance people. The bug got already fixed in openSUSE:Leap:15.0:Update before Leap 15.1 release, but this wasn't taken at all.
I think this is a different bug than #1100871. The authentication dialog does appear, but nothing happens after you type the password and press the Accept button or the Enter key directly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c11
--- Comment #11 from Takashi Iwai
(In reply to Takashi Iwai from comment #9)
I reassign this to maintenance people. The bug got already fixed in openSUSE:Leap:15.0:Update before Leap 15.1 release, but this wasn't taken at all.
I think this is a different bug than #1100871. The authentication dialog does appear, but nothing happens after you type the password and press the Accept button or the Enter key directly.
Well, did you try the Leap 15.0:Update package, and it still shows that behavior? Let's check that at first. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c12
--- Comment #12 from jc sl
(In reply to jc sl from comment #10)
(In reply to Takashi Iwai from comment #9)
I reassign this to maintenance people. The bug got already fixed in openSUSE:Leap:15.0:Update before Leap 15.1 release, but this wasn't taken at all.
I think this is a different bug than #1100871. The authentication dialog does appear, but nothing happens after you type the password and press the Accept button or the Enter key directly.
Well, did you try the Leap 15.0:Update package, and it still shows that behavior? Let's check that at first.
No, I didn't, because I'm a Tumbleweed user, not a Leap user. I switched over to Tumbleweed when openSUSE became openSUSE Leap. As I said, I thought they were different issues and lxqt-sudo from Leap wouldn't work on Tumbleweed. As far as I can remember, this bug has always been present in Tumbleweed, which is the one I reported the bug for and the only one I'm interested in. Anyway, as it may be of help, I've downloaded 15.0 and 15.1 DVD ISOs to test the issue: ─ On 15.0 freshly installed from the DVD and then installing LXQt without the Update repository enabled, it works ─ On 15.0 fully updated, it doesn't work ─ On 15.1 freshly installed from the DVD and then installing LXQt without the Update repository enabled, it works ─ On 15.1 fully updated, it works ─ On Tumbleweed with lxqt-sudo from 15.0/Update, it doesn't work ─ On Tumbleweed with lxqt-sudo from 15.1/Oss, it works Greetings. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c13
--- Comment #13 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c14
oota toshiya
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
oota toshiya
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397
http://bugzilla.opensuse.org/show_bug.cgi?id=1120397#c21
Nathan Wolf
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com