November 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 648412] New: NetworkManager not working if nfs mount in fstab
by bugzilla_noreply＠novell.com 05 Nov '10

05 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=648412 https://bugzilla.novell.com/show_bug.cgi?id=648412#c0 Summary: NetworkManager not working if nfs mount in fstab Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 2 of 6 Platform: 32bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: harmie(a)opensuse.fi QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi-FI; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-3.4 Firefox/3.6.10 When I add nfs mount to /etc/fstab NetworkManager does not start after boot. I need to run rcnetwork restart after boot to get the wireless network working again. After boot the KnetworkManager is gray and nothing can be done with it. Reproducible: Always Steps to Reproduce: 1.add nfs mount to /etc/fstab 2.boot Actual Results: workaround to fix the problem rcnewtwork restart Expected Results: NetworkManager should work after boot without restart. -- 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 546136] New: YaST does not allow abandoning a full installation run.
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

http://bugzilla.novell.com/show_bug.cgi?id=546136 Summary: YaST does not allow abandoning a full installation run. Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE If I click on Abandon (Abbrechen) during an installation run YaST2 does not react. However if downloading of packages uses to fail I can only select to abandon download of the currently to-be-installed package. This is no enough if downloading of all packages from a given source uses to fail. Please enable a total installation abandoning by making the abandon button of the 'perform installation' window work. Besides this I wonder why drawing packages from the Kernel-Head source does totally fail. Reproducible: Always -- 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 7

[Bug 539208] New: YaST error handling is cumbersome
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

http://bugzilla.novell.com/show_bug.cgi?id=539208 Summary: YaST error handling is cumbersome Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 7 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: radomir.cernoch(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-3.4 Firefox/3.5.2 If there is a problem with package downloads during installation (openSUSE 11.2 Milestone 7), the error handling is extremely cumbersume and unintuitive. To see what happens, see the long chain of error dialogs, which showes up: 1) = Error = Download fails: Failed to download [path] from [url] History: - [AbstractCommand.cc] URI=[the same url] [[OK]] Here I wonder why the user must know the name of the source file, where the error (or exception?) was thrown (or caught?). It is such an important information? Since the only button is "OK", the user must click "OK". 2) Cannot access installation media [the same url, for the 3rd time] Check whether the server is accessible. Remaining time to automatic retry: 00:30 [[Retry]] [[Abort]] [[Skip]] "Retry" button starts the download again, but it is the only button which does what it says. "Abort" and "Skip" surprisingly do the same thing, but it is neither abort nor skip. Both buttons pass you to the dialog 3. 3) Cannot create a repository from URL '[the same url, for the 4th time]' Details: no valid metadata found at given URL. History: - Failed to download [path] from [url, 5th time] - Can't provide [path]: Failed to download [path] from [url, 6th time] Do you want to retry? [[Yes]] [[No]] Here I started to wonder whether it is really necessary to show the URL 6 times. The buttons here have even more confusing meaning than before: If I want to change the url, the logical choice is "No" (because the dialog asks for a "retry"). However the "No" button means "abort" here and it cancels the whole installation. The "Yes" button does not mean "retry" here (as it may seem from the dialog), but "modify URL". It brings you to dialog number 4. 4) Is the final dialog, which the user probably wants to achieve. It allows altering the SMB/HTTP/HTTPS/FTP server, path, username etc. Fortunatelly this one works fine and it does what it says. ======================================== My proposal here is to keep dialog 4) and to squeeze dialogs 1)+2)+3) into a single one. It would look something like: = Error = Cannot initialise repository with software packages. Failed to download [path] from [url] [[Retry download]] [[Modify URL]] [[Abort installation]] [[Skip repository]] where the last button ("Skip repository") would be displayed only if there is at least one more repository to be initialised. Otherwise it would be hidden not to confuse the user. Reproducible: Always -- 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 10

[Bug 651097] New: kaddressbook stack traces at start
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=651097 https://bugzilla.novell.com/show_bug.cgi?id=651097#c0 Summary: kaddressbook stack traces at start Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: pablo(a)blueoakdb.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=398453) --> (http://bugzilla.novell.com/attachment.cgi?id=398453) stack trace with debug symbols User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-1.1 Firefox/3.6.12 [ I'm testing `openSUSE 11.3' + `Upstream release (KDE SC 4.5)' -- please let me know if I should use a different venue to report bugs. ] Hi, With `kaddressbook' from `Upstream release (KDE SC 4.5)', I always get a stack trace when starting the application from the CLI. See the attached crash report along with stdout. Please let me know if you need additional data. `rpm' ===== pablo@zoom-171-[pablo]: rpm -q kaddressbook kaddressbook-4.4.7-8.2.i586 Details ======= My first attempt was to use `kontact > contacts' which crashed. Next, I manually started `kaddressbook' from the CLI and found it crashed as well. I initially was using `Factory (KDE SC 4.5)' repository so I thought I'd try the latest and greatest repository (`Upstream release (KDE SC 4.5)'). Unfortunately, this didn't resolve the issue. I checked for existing bugs but didn't find any. This is a fresh install. Reproducible: Always Steps to Reproduce: 1. % kaddressbook Actual Results: `The KDE Crash Handler' pops up. Expected Results: 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 6

[Bug 634487] New: cheese does not recognize camera
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=634487 https://bugzilla.novell.com/show_bug.cgi?id=634487#c0 Summary: cheese does not recognize camera Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lthuns(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 Cheese 2.30.1 simply does not recognize my camera. Bus 002 Device 003: ID 090c:37b3 Feiya Technology Corp. whenever I start cheese, /var/log/message tells uvcvideo: Failed to query (130) UVC control 5 (unit 3) : -32 (exp. 1) cheese-2.30.1-2.1.1.x86_64 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 x86_64 x86_64 x86_64 GNU/Linux 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 13

[Bug 638721] New: Are unique comments recommended in "menu.lst"?
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=638721 https://bugzilla.novell.com/show_bug.cgi?id=638721#c0 Summary: Are unique comments recommended in "menu.lst"? Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=388971) --> (http://bugzilla.novell.com/attachment.cgi?id=388971) /boot/grub/menu.lst The file "/boot/grub/menu.lst" was also updated on my system once again after I installed recent kernels. I wonder that a comment like "YaST2 identifier: Original name: linux" is repeated multiple times. I assume that such "identifiers" should be unique, shouldn't they? -- 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 651124] New: Using a dark color scheme in KDE makes OpenOffice unusable
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=651124 https://bugzilla.novell.com/show_bug.cgi?id=651124#c0 Summary: Using a dark color scheme in KDE makes OpenOffice unusable Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: spiollinux(a)alice-dsl.net QAContact: cwei(a)novell.com Found By: --- Blocker: --- Created an attachment (id=398469) --> (http://bugzilla.novell.com/attachment.cgi?id=398469) It#s a screenshot of ooo with some different text colors User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 If you use a dark color scheme in KDE OpenOffice is dark, too (like other windows), but the icons are inverted, the sheet of paper displayed is dark, too, and the font color appears white, no matter which color you set. The error occurs no matter if you have installed openoffice_org-kde or openoffice_org-gnome or none of them or if you activated the setting to use the colors in non-KDE programs Reproducible: Always Steps to Reproduce: 1. use a dark KDE color scheme (ex. Obsidian Coast) 2. launch openoffice Actual Results: buttons are inverted every font color looks white sheet background color is dark, too Expected Results: buttons look normal fonts are displayed in the right color sheet of paper is white a good idea to fix it would be to add a windowspeciefic/ programspeciefic option for the colorscheme like it's possible for geometrie... -- 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 626073] New: NM does not connect to wireless network
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

http://bugzilla.novell.com/show_bug.cgi?id=626073 http://bugzilla.novell.com/show_bug.cgi?id=626073#c0 Summary: NM does not connect to wireless network Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs(a)forge.provo.novell.com ReportedBy: suse(a)bugs.jan.ritzerfeld.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=378717) --> (http://bugzilla.novell.com/attachment.cgi?id=378717) /var/log/NetworkManager User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.6.30 Version/10.60 I use a T410s with a Intel Centrino Ultimate-N 6300 WiFi Adapter and NetworkManager with KNetworkManager as front-end. If I log in, KNetworkManager will not connect to my preferred wireless network. Even when I try to start the connection by manually clicking any stored wireless network, nothing happens. After a "rcnetwork restart" KNetworkManager crashes. However, after restarting KNetworkManager, it automatically connects! I used 11.3 RC2 before and everything worked fine. I kept my /home and installed GM to a different partition, so the initial configuration was identical. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 5

[Bug 650399] New: Virtualbox module version don't match kernel version
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=650399 https://bugzilla.novell.com/show_bug.cgi?id=650399#c0 Summary: Virtualbox module version don't match kernel version Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: speilicke(a)novell.com QAContact: qa(a)suse.de CC: mseben(a)novell.com Found By: --- Blocker: --- There are no updated virtualbox modules shipped with new kernel versions. I've got the following kernel installed from the Updates repository: Linux machine 2.6.34.7-0.5-desktop #1 SMP PREEMPT 2010-10-25 08:40:12 +0200 x86_64 x86_64 x86_64 GNU/Linux But the Virtualbox modules still stay at the kernel version from the vanilla 11.3 repo, which breaks VBox. Instead, updated versions should be shipped in the updates repository alongside new kernel versions. CC'ing the package maintainer... -- 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 8

[Bug 650372] New: Build Service registration doesn't work
by bugzilla_noreply＠novell.com 04 Nov '10

04 Nov '10

https://bugzilla.novell.com/show_bug.cgi?id=650372 https://bugzilla.novell.com/show_bug.cgi?id=650372#c0 Summary: Build Service registration doesn't work Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: General AssignedTo: adrian(a)novell.com ReportedBy: christian.korff(a)gmail.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; NET4.0C; .NET4.0E; InfoPath.1; OfficeLiveConnector.1.5; OfficeLivePatch.1.3) I tried to register myself to the Build Service. However I only recieved the following error message after entering my e-mail address etc. and continue: OBS Web Interface Error: Error Details: Errorcode: invalid_http_method Message: Invalid HTTP Method: PUT Reproducible: Always -- 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 13