April 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 631274] New: /opt/kde3/share/applications/kde/printers.desktop from kdebase3 broken
by bugzilla_noreply＠novell.com 15 Apr '12

15 Apr '12

http://bugzilla.novell.com/show_bug.cgi?id=631274 http://bugzilla.novell.com/show_bug.cgi?id=631274#c0 Summary: /opt/kde3/share/applications/kde/printers.desktop from kdebase3 broken Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: aj(a)novell.com QAContact: qa(a)suse.de Found By: Product Management Blocker: --- updating firefox with zypper, I see the following error message: Additional rpm output: Error in file "/opt/kde3/share/applications/kde/printers.desktop": "print/manager" is an invalid MIME type ("print" is an unregistered media type) -- Configure bugmail: http://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 672495] New: libcdio cannot be used for GNOME due to a license incompatibility
by bugzilla_noreply＠novell.com 15 Apr '12

15 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=672495 https://bugzilla.novell.com/show_bug.cgi?id=672495#c0 Summary: libcdio cannot be used for GNOME due to a license incompatibility Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joerg.schilling(a)fokus.fraunhofer.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1) Gecko/20090617 Firefox/3.5 There are two problems related to libcdio 1) libcdio contains code from cdda2wav that has been published under "GPLv2 only" but libcdio claims it is under another GPL variant 2) libcdio is publiched under GPL and called from LGPL code. The FSF claims that it is not permitted to use GPL code from code that is not under GPL. This is a problem that has been identified by the Sun legal department in 2006. Sun did immediately stop distributing libcdio. A solution is to replace libcdio by libgstcdda2wav.so that has been written by Brian Cameron and Jörg Schilling. 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 12

[Bug 737537] New: SuSE 12.1 /installation / udev
by bugzilla_noreply＠novell.com 15 Apr '12

15 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=737537 https://bugzilla.novell.com/show_bug.cgi?id=737537#c0 Summary: SuSE 12.1 /installation / udev Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ayadzein(a)yahoo.fr QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 This isn't a duplicate of 727762. I've read what looked at what appeared to be similar reports here and elsewhere and this report is not a duplicate of any. During installation, as soon as udev starts, the display blanks then turns off completely. Something continues to happen (disk activity during which ctrl+alt+del produces a reboot) for a few seconds afterward then system halts requiring a forced physical shutdown. This is is always reproducible using any combination of kernel and BIOS settings when installing from the DVD, booting from a live CD, or installing from a live CD for both 32 and 64 versions of all of the above. I can't look at any logs or debug because the incident immediately follows the "starting udev" output. Reproducible: Always Steps to Reproduce: 1.Load SuSE 12.1 DVD or live CD 2.Select "installation" or "boot live CD" Actual Results: Installation begins, then upon starting udev, display blanks then turns off completely followed by the system becoming unresponsive requiring a forced shutdown. Expected Results: udev should probe for, then list hardware, and then load the 6 parts of the installation system and continue with the installation. Hardware: Laptop, Toshiba, Satellite L775D-S7305, AMD Quad-Core A6-3400M Accelerated Processor; 4MB Cache; AMD Radeon HD 6520G Graphics; 4GB DDR3 1333MHz. -- 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 743980] New: Kmix mixer displays only one channel
by bugzilla_noreply＠novell.com 14 Apr '12

14 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=743980 https://bugzilla.novell.com/show_bug.cgi?id=743980#c0 Summary: Kmix mixer displays only one channel Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: alexander.koenig(a)koenig-a.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=473164) --> (http://bugzilla.novell.com/attachment.cgi?id=473164) Hardware info User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 The "mixer" view of Kmix displays only one channel, i.e. "Internes Audio, Analog Stereo" All other channels, e.g. "line", "mic", "CD", do not appear and I found no way to manage their volume via Kmix. All those channels are visible in the sound module of Yast and I can manage their volume there. I am using the onboard sound chip of may mainboard GIGABYTE GA-MA770-DS3. On my previous openSUSE 11.3 installation all those channels appeared in Kmix. Reproducible: Always Steps to Reproduce: 1.Click on the Kmix symbol 2.Click on the "mixer" button Actual Results: Mixer Window opens, but only one channel is visible "Internes Audio Analog Stereo" - for both, input and output devices. This is also the only channel in the "select main channel" menu. Expected Results: All channels visible (and manageable via Yast) should be in Kmix as well -- 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 754533] New: AR9170 doesn't work: carl9170-firmware should be submitted to Factory and 12.1 updates
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=754533 https://bugzilla.novell.com/show_bug.cgi?id=754533#c0 Summary: AR9170 doesn't work: carl9170-firmware should be submitted to Factory and 12.1 updates Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: coolo(a)suse.com ReportedBy: christian.morales.vega(a)gmail.com QAContact: qa-bugs(a)suse.de CC: AxelKoellhofer(a)web.de Found By: Community User Blocker: --- We have a nice package (driver:wireless/carl9170-firmware) but we don't provide it by default. As a result users with a AR9170 WiFi device haven't Internet connection. Axel, any reason not to do so? -- 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 735519] New: virt-manager problems
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=735519 https://bugzilla.novell.com/show_bug.cgi?id=735519#c0 Summary: virt-manager problems Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: psankar(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I could not find virt-manager in the Applications list. I tried launching it from terminal. I got an error saying that it needed root privileges. I tried launching sudo virt-manager from terminal. I got an error saying that dbus session does not exist (why is dbus needed anyway ?) I tried launching from a root shell (instead of a sudo), I get an error popup: Error launching manager: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 840, in _do_show_create create = vmmCreate(virtman=True,key=0) File "/usr/lib/python2.7/site-packages/vminstall/gtk/interface.py", line 128, in __init__ vminstall.options.calculate(options, defaults) File "/usr/lib/python2.7/site-packages/vminstall/options.py", line 392, in calculate defaults.connect = libvirt_hypervisor.LibVirtHypervisor("qemu:///system") File "/usr/lib/python2.7/site-packages/vminstall/libvirt_hypervisor.py", line 59, in __init__ self.virConn = libvirt.openReadOnly(self.uri) File "/usr/lib/python2.7/site-packages/libvirt.py", line 247, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory P.S: I could not find a Virtualization or KVM component, so I am filing this under Kernel, please re-assign to any valid component. -- 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 5

[Bug 755820] New: hp-toolbox.wrapper script mistakenly produces error about not finding HP all-in-one device
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=755820 https://bugzilla.novell.com/show_bug.cgi?id=755820#c0 Summary: hp-toolbox.wrapper script mistakenly produces error about not finding HP all-in-one device Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)suse.com ReportedBy: rainer.klier(a)gmx.at QAContact: jsmeix(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 the script /usr/bin/hp-toolbox.wrapper tries to find out, if there are any HP devices connected. It does this by starting the hp-toolbox python script and greping the start-messages for "error". When finding the "error" string it shows the error-popup-message "No HP all-in-one device found (those devices require a special setup).". This works, when there are really no HP devices. But it fails, wheh there are more devices set up in HP toolbox, and only ONE of them is not connected or switched on. Because the "error" string is found, when hp-toolbox starts, because it complains about the one missing HP device with such an "error". And the mistakenly produced Error-popup is not the main problem. After clicking this Error-popup away, the HP toolbox does not work any more as expected. Even with the devices connected properly. You can not get status of connected devices. When starting hp-toolbox alone, and not producing this Error-popup, hp-toolbox is working normaly and as expected. Reproducible: Always Steps to Reproduce: 1. start hp-toolbox with the supplied hp-toolbox.wrapper script, when more HP devices are configured in hp-toolbox, but one of them is disconnected. 2. See the mistakenly produced Error-popup. Click it away. 3. Try to get status of connected devices. Actual Results: mistakenly produced Error-popup. You can not get status of connected HP devices. Expected Results: Error-popup only if ALL connected HP devices fail. Status of connected HP devices should be accessible. -- 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 748439] New: yast2/zypper: "Bad media attach point" prevents refresh from repositories
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=748439 https://bugzilla.novell.com/show_bug.cgi?id=748439#c0 Summary: yast2/zypper: "Bad media attach point" prevents refresh from repositories Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jimoe(a)sohnen-moe.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 yasts/zypper can start emitting the error "bad media attach point" when refreshing repository data. The cause is an excess of temporary directories in /var/tmp/, both AP_0x* and zypp.*. There can be up to 1000 of AP_0x* dirs, and an similar number of zypp.* dirs. After deleting the zypp.* directories, updates started working again. Reproducible: Always Steps to Reproduce: 1. Wait until /var/tmp fills up with 1000s of temporary directories. 2. Run Yast::Software::Online Update, or "zypper refresh". Actual Results: All attempts to refresh fail with "bad media attach point". Expected Results: Data is retrieved from repositories. Also that temporary files and directories would be removed after their usefulness is finished. Here is the entry in <zypper.log> that gave me a clue: 2012-02-19 13:03:01 <1> sma-station11l(11666) [zypp++] MediaHandler.cc(createAttachPoint):393 Trying to create attach point in /var/adm/mount 2012-02-19 13:03:01 <3> sma-station11l(11666) [zypp] MediaHandler.cc(createAttachPoint):423 Unable to create an attach point below of /var/adm/mount 2012-02-19 13:03:01 <1> sma-station11l(11666) [zypp++] MediaHandler.cc(createAttachPoint):393 Trying to create attach point in /var/tmp 2012-02-19 13:03:01 <3> sma-station11l(11666) [zypp] MediaHandler.cc(createAttachPoint):423 Unable to create an attach point below of /var/tmp 2012-02-19 13:03:01 <5> sma-station11l(11666) [zypp] Exception.cc(log):137 MediaCurl.cc(attachTo):719 THROW: Bad media attach point: http://download.opensuse.org/distribution/12.1/repo/non-oss/ When I looked in /var/adm/mount/ and /var/tmp/, I found the huge number of temporary dirs. -- 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 5

[Bug 95813] X11 serb locale support
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=95813 https://bugzilla.novell.com/show_bug.cgi?id=95813#c17 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #17 from Stefan Dirsch <sndirsch(a)suse.com> 2012-04-13 10:52:15 UTC --- Yes, I am. We should continue with what is done upstream. -- 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 752329] New: autoupdater: obscure message about not signed software
by bugzilla_noreply＠novell.com 13 Apr '12

13 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=752329 https://bugzilla.novell.com/show_bug.cgi?id=752329#c0 Summary: autoupdater: obscure message about not signed software Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)suse.com Found By: --- Blocker: --- autoupdater: obscure message about not signed software Lately, when AU shows info about new updates, I click OK, AU tries to install updates, but then it shows obscure message that the software is not trusted and if I want to cancel or force install. Now, how from X packages I am supposed to know what package is not trusted? Please, in the same dialog show -- this, this and this package is not trusted, coming from repo X, Y and Z. This is some information I can work with. Another story, why should I have to cancel all packages when only some are not trusted? -- 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 5