June 2013 - openSUSE Bugs - openSUSE Mailing Lists

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 23 Jun '13

23 Jun '13

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&a… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! wiki.opensuse.org redirects to wiki.opensuse.org// -> http://bugzilla.novell.com/show_bug.cgi?id=761235 help.opensuse.org still uses the old 'openSUSE' theme instead of 'bento' -> http://bugzilla.novell.com/show_bug.cgi?id=821405

1 0

[Bug 814735] New: Switching on/off display/TV brings: "A new monitor output has been connected"
by bugzilla_noreply＠novell.com 23 Jun '13

23 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=814735 https://bugzilla.novell.com/show_bug.cgi?id=814735#c0 Summary: Switching on/off display/TV brings: "A new monitor output has been connected" Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: dirk(a)goe.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 KDE4 as desktop, standard X64-64 machine, TV set connected to DVI port of the machine. Set is switched off and on again brings "A new monitor output has been connected" every time independent of the thing I'm doing: - "Try automatically" does nothing - "Yes" brings the configuration dialog (here I saved several times this configuration as default with no use) - "No" gets rid of the dialog, but next time it will be there again This is totally annoying as switching on and off a display naturally occurs a couple of times. Reproducible: Always Steps to Reproduce: 1. Switch off the display 2. Switch on the display get annoyed by the dialog - try every option you see in there 3. Repeat the cycle ad-inifitum Actual Results: Get the annoying KDE dialog with no chance to avoid it. Expected Results: I don't want to see it again if NOTHING changes in the hardware setup. The monitor detection and configuration seems to be a mess nevertheless, as reported for earlier versions (bug 780219). -- 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 780219] New: KDE4 fails miserably with hot(un)plugged monitors (displays added/removed during session dynamically e.g. on laptops)
by bugzilla_noreply＠novell.com 23 Jun '13

23 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=780219 https://bugzilla.novell.com/show_bug.cgi?id=780219#c0 Summary: KDE4 fails miserably with hot(un)plugged monitors (displays added/removed during session dynamically e.g. on laptops) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: dirk(a)goe.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1 The KDE4 desktop is not really able to properly add hotplugged additional displays. When I add a monitor on the VGA port of my Lenovo X220, then I get the option to configure the additional display. All OK. But if I remove the display, then I'm in trouble. The display configuration interface detects (by graying out the removed monitor) that a display got removed, but the KDE4 desktop does not shrink back to the remaining displays. Plus, error messages or new windows appear on the non-existing display. The complete handling procedure is a mess. It kind of works, when running "xrandr --auto", but it does not necessarily reconfigures the same monitor plugged in again in the same way. Often I simply get a wrecked up duplicated display (both screens using their optimal resolution and not all stuff is displayed on every display). The same was found on a Kubuntu 12.04 KDE4 desktop with a bit less trouble when running xrandr (previous monitor configurations got restored properly). It does not get better when running krandrtray. Everything is working fine under GNOME. A monitor gets plugged in, the desktop extends automatically. If I configure it to sit on a certain side, then it gets every time properly reconfigured when (re)connected. This works properly with a couple of different monitors and exactly as I like to see it. I don't get bothered with pop-ups and do not need to accept/click/click-away anything. It simply works smoothly. Why it cannot act exactly the same on KDE4? The desktop is perfectly able to handle desktop expansion and reduction. Reproducible: Always Steps to Reproduce: 1. Start your laptop without a monitor connected. 2. Login to KDE4 3. Add a second display and enjoy the mess. 4. Remove the second display and it gets worse. 5. Try to get out of the mess (CTRL-ALT-BACKSPACE helps) Actual Results: The system is unusable with KDE4 in dynamic multi-display settings. Expected Results: Should seemlessly work like in GNOME. -- 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

[Bug 768562] New: Flash needs HAL to reproduce protected content but HAL is not available
by bugzilla_noreply＠novell.com 22 Jun '13

22 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=768562 https://bugzilla.novell.com/show_bug.cgi?id=768562#c0 Summary: Flash needs HAL to reproduce protected content but HAL is not available Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: albert.passalacqua(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0 It is not possible to reproduce flash content with DRM since HAL is required, and not available in openSUSE 12.1 (and 12.2). Please, see http://helpx.adobe.com/x-productkb/multi/flash-player-11-problems-playing.h… 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 21

[Bug 720141] New: courier-authdaemon does not start
by bugzilla_noreply＠novell.com 22 Jun '13

22 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=720141 https://bugzilla.novell.com/show_bug.cgi?id=720141#c0 Summary: courier-authdaemon does not start Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Starting courier-authdaemon using, as root, the command rccourier-authdaemon, the service does not start. The problem is that the directory authdaemon.courier-imap in /var/run/ does not exist. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: The packet courier-authlib should create the directory during installation. -- 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 7

[Bug 771340] New: Configuring NTP in YaST2 the service does not start
by bugzilla_noreply＠novell.com 22 Jun '13

22 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=771340 https://bugzilla.novell.com/show_bug.cgi?id=771340#c0 Summary: Configuring NTP in YaST2 the service does not start Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1 Starting the NTP Configuration in YaST2 Network Services I configured a server and checked Now and on boot, also I disabled running chroot. After that I clicked on OK and got an error message that the service did not start. Checking the status with "rcntp status" showed the service was not running. Only after giving the command "rcntp start" the service did start. Going back to the YaST2 module and clicking OK showed, using "rcntp status", that the service was restarted OK. Reverting back to the default settings of the NTP configuration, removing the server, enabling chroot and checking Only manually reverted the service back to a non-active state. Reconfiguration to the configuration above gives the same error message "NTP daemon can not be restarted". A "rcntp start" starts the service and "chkconfig -l ntp" shows the service is enabled for 3 and 5. Reproducible: Always Steps to Reproduce: 1. See above 2. 3. Expected Results: The service should start. -- 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 16

[Bug 820218] New: ibus qt tray icon is not in keeping with KDE monochrome icon look.
by bugzilla_noreply＠novell.com 22 Jun '13

22 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=820218 https://bugzilla.novell.com/show_bug.cgi?id=820218#c0 Summary: ibus qt tray icon is not in keeping with KDE monochrome icon look. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: mrkfbrn(a)yahoo.co.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 since kde 4.10 the ibus tray icon is not in keeping with the monochrome look of KDE tray icons and looks somewhat out of place in the KDE system tray. - see screen-shot. some other distributions have different icons for ibus to keep the look consistent with the currently used DE. Reproducible: Always Expected Results: re-work ibus icon to be consistent with kde 4.10 openSUSE look (openSUSE theme) -- 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 29

[Bug 824262] New: LibreOffice crashes in libicule.so.51.2
by bugzilla_noreply＠novell.com 22 Jun '13

22 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=824262 https://bugzilla.novell.com/show_bug.cgi?id=824262#c0 Summary: LibreOffice crashes in libicule.so.51.2 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: jengelh(a)inai.de ReportedBy: lchiquitto(a)suse.com QAContact: qa-bugs(a)suse.de CC: pmladek(a)suse.com Found By: --- Blocker: --- LibreOffice crashes on start up after the last Factory update. Downgrading libicu51 from version 51.2-1.1 to 51.1-1.1 resolves the problem. - Update to new upstream release 51.2 * Common Locale Data Repository (CLDR) 23.1 * Time zone database version 2013c * Security fixes for font layout and glyph table errors. NOTE: Applications must implement LEFontInstance::getFontTable(LETag, size_t &length) in their LEFontInstance subclasses, so that ICU can properly bounds-check font tables. -- 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 826262] New: amarok-2.7.1-196.1.x86_64 does not recognize iPod classic (160G); KDE does
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826262 https://bugzilla.novell.com/show_bug.cgi?id=826262#c0 Summary: amarok-2.7.1-196.1.x86_64 does not recognize iPod classic (160G); KDE does Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: bferrell(a)baywinds.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 When I plug my ipod in, the KDE device notifier shows me actions for it. I then start Amarok, and the device is never recognized Reproducible: Always Steps to Reproduce: 1. plug in ipod 2. wait for device notifier 3. start amarok; look for ipod... never seen Actual Results: local collection visible. device never appears Expected Results: local collection should be available as well as thge ipod It used to work -- 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 807284] New: mkinitrd /boot/do_purge_kernels fails under systemd
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=807284 https://bugzilla.novell.com/show_bug.cgi?id=807284#c0 Summary: mkinitrd /boot/do_purge_kernels fails under systemd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: mmarek(a)suse.com ReportedBy: lmuelle(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: No Created an attachment (id=527958) --> (http://bugzilla.novell.com/attachment.cgi?id=527958) Make use of the intended /boot/do_purge_kernels filename /boot/do_purge_kernels exists and the multiversion feature of /etc/zypp/zypp.conf is configured like this: lmuelle@maximegalon:~> grep ^multiversion /etc/zypp/zypp.conf multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running Nevertheless we see: maximegalon:~ # systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Mon, 04 Mar 2013 13:34:41 +0100; 9s ago CGroup: name=systemd:/system/purge-kernels.service /lib/systemd/system/purge-kernels.service checks for /boot/do_pure_kernels instead of /boot/do_purge_kernels -- 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