August 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 825256] New: polkit-cant-acquire-privilege org.kde.powerdevil.backlighthelper.syspath (??:yes:yes)
by bugzilla_noreply＠novell.com 16 Aug '13

16 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=825256 https://bugzilla.novell.com/show_bug.cgi?id=825256#c0 Summary: polkit-cant-acquire-privilege org.kde.powerdevil.backlighthelper.syspath (??:yes:yes) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: tittiatcoke(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 With KDE 4.11 a new backlighthelper was introduced within the PowerDevil application. On some laptops it would now be possible to regulate the backlight of the laptop screen. However this new helper also caused an issue with the current polkit-defaults-privs, as that it is not listed. In the KDE:Distro:Factory repo we have resolved it temporarily by setting the error to a information in a rpmlintrc, but as indicated this needs to be pushed to Factory soon. The warning is: [ 1579s] kdebase4-workspace.x86_64: I: polkit-cant-acquire-privilege org.kde.powerdevil.backlighthelper.syspath (??:yes:yes) [ 1579s] Usability can be improved by allowing users to acquire privileges via [ 1579s] authentication. Use e.g. 'auth_admin' instead of 'no' and make sure to define [ 1579s] 'allow_any'. This is an issue only if the privilege is not listed in /etc [ 1579s] /polkit-default-privs.* The package itself can be found in KDE:Distro:Factory. As that this is blocking the submission to Factory, it has some urgency. Therefore I set it as a critical bug. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 805344] New: Apper - Windows that Provides Escalation of Auth to root is NEVER INFOCUS and cannot Resolve Dependencies
by bugzilla_noreply＠novell.com 16 Aug '13

16 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=805344 https://bugzilla.novell.com/show_bug.cgi?id=805344#c0 Summary: Apper - Windows that Provides Escalation of Auth to root is NEVER INFOCUS and cannot Resolve Dependencies Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 When Apper calls for escalation of authority window, the window is not infocus. Infact it is so easily missed being behind over other application Windows or the escalation of authority window appears minimised on the task bar, again not in focus. Apper does not adhere to standards of the Windowing Manager and makes up its own rules. For an application to not adhere to the windowing conventions, like apper doesn’t, it looks out of place breaking all standard windowing conventions. This is more than apparent on testing and Apper still has the some horrendous hangovers from Kpackage kit of 11.4. Appear never stays visible in the system tray despite setting to always visible. Apper cannot also resolve conflicts and the allowance to change vendors and clean up, offered by Yast Online update, cannot be applied by Apper's logic of resolving conflicts. Until the conflicts are resolved by user Yast>Online update further updates by apper cannot ever be completed as the kpackage kit cannot resolve past or current dependency issues. Suggest that the settings in Apper adhere to the options available in Yast>Online update This forces the user to use Yast>Online updates which does resolve conflicts of this nature before any further update can possibly be installed via Apper and all sense of logic go out the window, so to speak Reproducible: Always Steps to Reproduce: 1.100% Reproducible, HOWEVER in the unlikely event it cannot be reproduced please tell me what log files you need for assistance in this bug 2. 3. Actual Results: Apper is not reliable...Its better for the user to always initiate an Online>Update via Yast as apper does not come close in the functionality of Yast>Online Update Expected Results: I have no idea of how this conflict in the Windowing Manager escaped alpha testing The bug is about the version of OpenSuse 12.1...By creating KDE type bug here a duplicate bug is auto created in KDE Bugzilla so continuity can be maintained in the total Software Version... Please ask me for any further assistance or log files if required -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 32

[Bug 833101] New: Microphone got shut off by latest update
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=833101 https://bugzilla.novell.com/show_bug.cgi?id=833101#c0 Summary: Microphone got shut off by latest update Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: bkorb(a)gnu.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36 If it were a matter of firing up kmixer or alsamixer or something, the irritation level would be minor. Instead, I have to go Googling around to try to figure out what went wrong this time. I've not gone through the gauntlet yet. (I didn't realize I needed to because there were so many things updated yesterday.) I'm sorry to be so cranky, but I just got off a con-call with my boss wherein I typed while he talked because my mic was disabled. If you cannot help but disable my mic, then please stop updating the sound after a release. This is really, really old. Stop it. Reproducible: Always Steps to Reproduce: 1. Pull an update that includes sound system updates 2. try to use your mic 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 832337] New: kiwi: config.sh not executed if lxc in packages list
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c0 Summary: kiwi: config.sh not executed if lxc in packages list Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Yarny(a)public-files.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=550270) --> (http://bugzilla.novell.com/attachment.cgi?id=550270) archive with kiwi logfile and description to reproduce User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 If a kiwi image root contains the package lxc, the script config.sh is not executed. Reproducible: Always Steps to Reproduce: Mount a yast repository with all needed packages (pattern:base, lxc) in /mnt/suse/suse, then extract the attached tar archive and call $ kiwi -p kiwilxcbug --root /tmp/kiwilxcbug.root The file config.sh is supposed to create the file config.sh.tag in the image root. Actual Results: There is no file config.sh.tag in the image root. Expected Results: If you remove lxc from config.xml and call kiwi again, it will create config.sh.tag as expected. The attached tar file also contains a logfile from kiwi. This bug didn't always exist in openSUSE 12.3. I still have a kiwi image around which has been built on June 23th where lxc is installed and config.sh obviously got executed. The machine which produced this image hadn't been updated for 1 or 2 months at that time, so the bug probably got introduced somewhen after March. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 747811] mariadb: install-info: warning: no info dir entry in `/usr/share/info/mysql.info.gz'
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=747811 https://bugzilla.novell.com/show_bug.cgi?id=747811#c Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|obs:running:1914:moderate |obs:running:1914:moderate | |maint:running:53652:importa | |nt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 834457] New: Variable makeinfo-program is empty in db2x_texixml
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=834457 https://bugzilla.novell.com/show_bug.cgi?id=834457#c0 Summary: Variable makeinfo-program is empty in db2x_texixml Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: stephan.barth(a)suse.com QAContact: ke(a)suse.com Found By: --- Blocker: --- Line 12 has: 'makeinfo-program' => q<>, This breaks the function "texi_openfile". I found this issue when building gnash. On 12.1 and 12.2 it still built the info files because this issue wasn't there yet apparently. On 12.3 it is also broken. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 817327] New: Runlevel Editor in expert mode lacks check-boxes for runlevels other than B
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=817327 https://bugzilla.novell.com/show_bug.cgi?id=817327#c0 Summary: Runlevel Editor in expert mode lacks check-boxes for runlevels other than B Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wodenhof(a)daad-alumni.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 In 12.2 one could activate services for all runlevels in a row of check boxes like so: B 0 1 2 3 4 5 6. Now the numbered boxes are gone, i.e. one can't (de)-activate services except for runlevel B. Reproducible: Always Steps to Reproduce: 1.start YAST2 2.start runlevel editor 3.switch to expert mode Actual Results: module switches to expert mode without the check boxes. See above Expected Results: module schould switch to expert mode with all check boxes As an aside: The list of the status (active) of the services is a coulumn of yes or no statements. Some have an asterisk (*). Why? There is no caption / explanation... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 801542] New: YaST runlevel editor does not support systemd-only services
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=801542 https://bugzilla.novell.com/show_bug.cgi?id=801542#c0 Summary: YaST runlevel editor does not support systemd-only services Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- YaST runlevel editor does not support systemd-only services. They simply don't display, if they don't have a corresponding sysvinit wrapper. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 813607] New: Yast System Services - Expert Mode - default and individual app runlevels missing
by bugzilla_noreply＠novell.com 15 Aug '13

15 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=813607 https://bugzilla.novell.com/show_bug.cgi?id=813607#c0 Summary: Yast System Services - Expert Mode - default and individual app runlevels missing Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)stanmiller.info QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=533634) --> (http://bugzilla.novell.com/attachment.cgi?id=533634) screenshot of yast system settings User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 The dropdown at the top of the Yast System Services for the default runlevel does nothing and the list of runlevels across the bottom of the screen only shows the "B" option for individual app runlevels. Reproducible: Always Steps to Reproduce: 1.Open Yast 2.pick the System Services 3.pick expert mode 4.click the default runlevel dropdown 5.nothing happens 1.Open Yast 2.pick the System Services 3.pick expert mode 4.click any application 5.only the "B" runlevel appears. Actual Results: 1. You get no choice of runlevels 2. The other runlevels are not shown. Expected Results: 1. You should have a choice of runlevels 2. The runlevels other than B should also be there. 12.3 x64 with all patches as of 04 April 2013 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 834896] New: virt-manager cannot show guest screen when spice in use
by bugzilla_noreply＠novell.com 14 Aug '13

14 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=834896 https://bugzilla.novell.com/show_bug.cgi?id=834896#c0 Summary: virt-manager cannot show guest screen when spice in use Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM AssignedTo: dimstar(a)opensuse.org ReportedBy: brogers(a)suse.com QAContact: jdouglas(a)suse.com CC: carnold(a)suse.com Found By: --- Blocker: --- Created an attachment (id=552655) --> (http://bugzilla.novell.com/attachment.cgi?id=552655) patch as used in red hat's spice-gtk package I used virt-manager to install a new guest (openSUSE 13.1 M4) and right before launching the install, tweaked the configuration to switch from vnc to spice. Upon launching the guest, the guest graphical screen fails to display, with virt-manager showing the following error: Cannot display graphical console type 'spice': /usr/lib64/python2.7/site-packages/SpiceClientGtk.so: undefined symbol: spice_channel_string_to_type In working on this with Charles Arnold on this, he discovered the following Red Hat bug, which seems to be dealing with the same issue: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=981815 According to that bug, a fix was made to the spice-gtk package, which I'll include as an attachment. Not having worked with this code, I'll leave it to the normal maintainers of spice-gtk to determine if this is the proper fix for us or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2