May 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 594388] New: dmraid cannot load shared library
by bugzilla_noreply＠novell.com 06 May '10

06 May '10

http://bugzilla.novell.com/show_bug.cgi?id=594388 http://bugzilla.novell.com/show_bug.cgi?id=594388#c0 Summary: dmraid cannot load shared library Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: nfbrown(a)novell.com ReportedBy: aschnell(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- During installation YaST tries to activate dmraid. This causes an error message: /sbin/dmraid -ay -p The dynamic shared library "libdmraid-events-isw.so" could not be loaded: /lib/libdmraid-events-isw.so: undefined symbol: pthread_mutex_trylock Apparently the RAID is activated nevertheless. -- 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 2

[Bug 201704] startup scripts idmapd, gssd and nfs prevent mounting a GSS-secured NFS4 filesystem on boot.
by bugzilla_noreply＠novell.com 06 May '10

06 May '10

http://bugzilla.novell.com/show_bug.cgi?id=201704 http://bugzilla.novell.com/show_bug.cgi?id=201704#c6 --- Comment #6 from Neil Brown <nfbrown(a)novell.com> 2010-05-06 00:14:27 UTC --- Yes, I've been leaving this in to too-hard basket for too long.... It should probably be a feature request rather than an bug but let's leave it here for now. I think that the only sane way to support / and/or /usr on NFSv4 is to require that they be accessible without any encryption, presumably in a read-only mode. i.e. we would mount / (and /usr) read-only with a "-o uid=0" flag to force all files to appear to be root-owned (thus avoiding the need for idmapd). Then we would have access to gssd etc and count mount a new / and/or /usr read-write with crypto and with idmapd service. This would require a 'uid=' mount option to nfs and possibly other kernel changes. However I think this is beyond the actual original needs which (I think) did not want to mount /usr or / from NFSv4. That was just a boot script ordering problem. It may well be fixed in 11.x. I will try to find time to experiment. -- 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 0

[Bug 557760] New: rpciod taking 100% of cpu, box *almost* unusable
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=557760 http://bugzilla.novell.com/show_bug.cgi?id=557760#c0 Summary: rpciod taking 100% of cpu, box *almost* unusable Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 While reading/writing an .iso over NFS (gig-e connection), rpciod/0 started consuming 100% of the CPU, and it stayed that way. The mount is NFSv4. echo 't' > /proc/sysrq-trigger and looking for the process: Nov 23 08:58:53 frank kernel: [ 3169.336539] rpciod/0 R running task 0 1471 2 0x00000008 Nov 23 08:58:53 frank kernel: [ 3169.336539] 0000000000000000 000000006521588b ffff88002c45c610 ffffffffa029b730 Nov 23 08:58:53 frank kernel: [ 3169.336539] ffffffffa0297be0 ffffc90010a43448 ffff88002c53be20 ffffffffa0297c0d Nov 23 08:58:53 frank kernel: [ 3169.336539] 0000000000000010 000000006521588b ffff88002c53be80 ffffffff81088631 Nov 23 08:58:53 frank kernel: [ 3169.336539] Call Trace: Nov 23 08:58:53 frank kernel: [ 3169.336539] Inexact backtrace: Nov 23 08:58:53 frank kernel: [ 3169.336539] Nov 23 08:58:53 frank kernel: [ 3169.336539] [<ffffffffa029b730>] ? rpc_async_schedule+0x0/0x40 [sunrpc] Nov 23 08:58:53 frank kernel: [ 3169.336539] [<ffffffffa029b753>] ? rpc_async_schedule+0x23/0x40 [sunrpc] Nov 23 08:58:53 frank kernel: [ 3169.336539] [<ffffffff81088631>] ? run_workqueue+0xc1/0x1f0 Nov 23 08:58:53 frank kernel: [ 3169.336539] [<ffffffff81088814>] ? worker_thread+0xb4/0x140 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff8108f390>] ? autoremove_wake_function+0x0/0x60 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff81088760>] ? worker_thread+0x0/0x140 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff8108ec26>] ? kthread+0xb6/0xc0 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff8100d70a>] ? child_rip+0xa/0x20 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff8108eb70>] ? kthread+0x0/0xc0 Nov 23 08:58:54 frank kernel: [ 3169.336539] [<ffffffff8100d700>] ? child_rip+0x0/0x20 Other processes are stuck in 'D' for more than 120s. This appears to be a regression. Easy to reproduce. Client and server are both openSUSE 11.2, and up-to-date as of now. I enabled all of the rpc debug flags for rpc and that was a mistake. I see a lot of this: Nov 23 09:12:27 frank kernel: [ 3855.711413] 16588 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711446] 16589 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711482] 16590 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711517] 16591 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711550] 16592 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711582] 16593 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711619] 16594 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711653] 16595 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711686] 16596 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711722] 16597 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711756] 16598 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711788] 16599 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711821] 16600 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711853] 16601 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711886] 16602 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711918] 16603 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711951] 16604 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.711983] 16605 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.712016] 16606 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.712048] 16607 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.712079] 16608 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.712115] 16609 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog Nov 23 09:12:27 frank kernel: [ 3855.712148] 16610 0281 -11 ffff88002cc1d800 (null) 0 ffffffffa035ce10 nfsv4 RENEW a:call_reserveresult q:xprt_backlog but a bunch of other stuff too. 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 19

[Bug 601822] New: [SMBTA] 'file l.tar.bz2, total rw' crashed smbtad
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=601822 http://bugzilla.novell.com/show_bug.cgi?id=601822#c0 Summary: [SMBTA] 'file l.tar.bz2, total rw' crashed smbtad Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: hhetter(a)novell.com ReportedBy: hhetter(a)novell.com QAContact: samba-maintainers(a)SuSE.de CC: mhaefner(a)novell.com, bbrunner(a)novell.com Found By: --- Blocker: --- smbtad crashes on any command involving the total command. AI holger, Benjamin, check the query code. -- 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 602940] New: kde logout screen "restart"-option for grub has no effect
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=602940 http://bugzilla.novell.com/show_bug.cgi?id=602940#c0 Summary: kde logout screen "restart"-option for grub has no effect Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: cyberbeat(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 SUSE/5.0.375.0-2.1 (KHTML, like Gecko) Chrome/5.0.375.0 Safari/533.4 When I choose to restart my pc from kde, and I choose to boot from the drop-down-menu another grub-entry (like windows), this has no effect. I am not 100% sure, if this happens on a fresh opensuse-11.2 install, but it happens with the obs kde4-factory packages. And I write this report in hope, that this will be fixed for opensuse-11.3 with kde-4.4. This was always a nice feature of kde: you did not need to wait on reboot and pass the right moment in grub, so that the wanted system is started. 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 1

[Bug 587146] New: Goggle is Indexing all our Feature Request Information
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=587146 http://bugzilla.novell.com/show_bug.cgi?id=587146#c0 Summary: Goggle is Indexing all our Feature Request Information Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: openFATE AssignedTo: tschmidt(a)novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: freitag(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 Goggle is indexing all feature requests. I know the login and session is via HTTPS but there appears to be HTTP Mailinglist Archives being indexed and everything is on display - I strongly suggest we use PKI Signed Messages auto-generated and manually generated. lists.opensuse.org/opensuse-features/2009-02/msg00224.html - Cached [openFATE 305688] system wide spellchecker (hunspell) Feature changed by: Scott Couston (zczc2311) Feature #305688, revision 14 ... + #7: Scott Couston (zczc2311) (2009-02-27 23:19:23) ... lists.opensuse.org/opensuse-features/2009-02/msg00224.html - Cached [openFATE 305715] Package event framework * From: fate_noreply@xxxxxxx * Date: Sat, 28 Feb 2009 15:06:07 +0100 (CET) * Message-id: <feature-305715-12@xxxxxxxxxxxxxx> Feature changed by: Casper Clemence (maninalift) Feature #305715, revision 12 Title: Package event framework openSUSE-11.2: New Priority Requester: Desirable Requested by: Andreas Gruenbacher (agruen) Description: The installation, upgrade, or removal of several packages triggers actions such as running ldconfig, rebuilding the initrd, or similar. Those actions are not specific to the package at hand, but either global with a system-wide effect (such as running ldconfig), or they affect a group of packages (such as all kernel (sub-)packages of a specific version, including all KMPs affecting it). Those actions need to be run eventually (with order restrictions relative to other package installs, upgrades, or removals), but running them again and again for each package is wasteful. (Example: with the kernel packages split into kernel-$flavor-base, kernel-$flavor, and kernel-$flavor-extra in CODE11, we currently run mkinitrd out of the %post script of each package. We don't know which of those packages will be installed, and when generating the initrd is supposed to succeed. This both wastes time, and we also cannot tell transient from permanent failures.) In former days, SuSEconfig was used for some of those tasks, but it turned into a major nightmare (perhaps due to its design). It would be nice if we could come up with a framework in which packages can trigger events and define which actions they need to be run, and rpm will then perform those actions in an appropriate order, avoiding repeating the same action unnecessarily. (The dependencies between actions and package installs/upgrades/removals are somewhat complex, but I think they are manageable.) Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-23 18:09:34) This is desirable only as it happens within RPM's framework (or if the additions are "candy" that does not affect the actual result). This includes upstreaming. Reproducible: Always Steps to Reproduce: 1.Ask Google - It appears it is freely indexing the mail archive NOT the FATE session but I think to give free access to mailing archives and thus FATE is not the way to go. I think we need to get creative (again)...seems Goggle knows when we all fart! 2. 3. Actual Results: Google Search Screen output is below in its entirety Expected Results: Q.A You may want to reclassify # [openFATE 305688] system wide spellchecker (hunspell) Feature changed by: Scott Couston (zczc2311) Feature #305688, revision 14 ... + #7: Scott Couston (zczc2311) (2009-02-27 23:19:23) ... lists.opensuse.org/opensuse-features/2009-02/msg00224.html - Cached # -- 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 12

[Bug 602866] New: Window manager does not start on login
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=602866 http://bugzilla.novell.com/show_bug.cgi?id=602866#c0 Summary: Window manager does not start on login Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: juglist(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100417 SUSE/3.6.4-1.1 Firefox/3.6.4 The metacity wm does not start on login. Running metacity --replace brings it up fine. I suspect compiz is the issue, because after running compiz --replace (or enabling desktop effecs via simple-ccsm) I lose the window manager again. 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 1

[Bug 513019] New: shutdown after resume from s2disk
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=513019 Summary: shutdown after resume from s2disk Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE It has now happened two times with the newly updated 2.6.27.23-0.1.1 kernel that a shutdown was initiated directly after resume from s2disk. Up to now I just kept experiencing repeated self-s2rams after resume from s2ram. Issuing an init 5 during shutdown could not rescue the system (I would expect an init 5 to terminate the shutdown process.). Reproducible: Sometimes -- 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 19

[Bug 456236] RAID1 md0 reported as md126
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=456236 http://bugzilla.novell.com/show_bug.cgi?id=456236#c7 Michal Marek <mmarek(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|jblunck(a)novell.com | Resolution| |NORESPONSE --- Comment #7 from Michal Marek <mmarek(a)novell.com> 2010-05-05 12:37:54 UTC --- Closing as noresponse. Please reopen if you can reproduce this on 11.2 or even better Factory and provide the information Neil requested in comment 3. Thanks. -- 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 0

[Bug 601780] New: root password entered during installation is invalid
by bugzilla_noreply＠novell.com 05 May '10

05 May '10

http://bugzilla.novell.com/show_bug.cgi?id=601780 http://bugzilla.novell.com/show_bug.cgi?id=601780#c0 Summary: root password entered during installation is invalid Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ingesvensson(a)orion.vokby.se QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729) During an install in Swedish and Swedish keyboard I enter a root password with an ? in it. After installation when I enter this password i.e. in YaST I get invalid password. The ? is interpretted by the installer as _ Reproducible: Always Steps to Reproduce: 1.Install 2. choose Swedish language and Swedish keyboard 3. choose root password not same as user password 4. enter root password with a ? 5. After installation start YaST and at request enter root password as entered at installation. Actual Results: Invalid password. Expected Results: YaST should have let me in as root. In console I can change password if I enter _ instead of ? and change _ to ? After that password works in YaST. -- 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