September 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 617912] New: loading WLAN module ssb crashes the system
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=617912 http://bugzilla.novell.com/show_bug.cgi?id=617912#c0 Summary: loading WLAN module ssb crashes the system Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: oneukum(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- The module ssb, which is autoloaded, if the system has a broadcom card, crashes the system. It is a hard lock. The problem is 100% reproducible. -- 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 32

[Bug 615656] New: YAST Frozen on Inel(R) Matrix Storage detection when installer start
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=615656 http://bugzilla.novell.com/show_bug.cgi?id=615656#c0 Summary: YAST Frozen on Inel(R) Matrix Storage detection when installer start Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nagylakas(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=370246) --> (http://bugzilla.novell.com/attachment.cgi?id=370246) Last question before installer stopped User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.1 (KHTML, like Gecko) Chrome/6.0.437.1 Safari/534.1 On openSuSE 11.3 RC1, YaST when asked how to use the Intel(r) Matrix Storage, does not go further, and the progress bar stops at 60% regardless of whether I answer yes or no for the question. A screenshot from the question is attached. My Motherboard is: MSI P45 NEO3-FR Reproducible: Always Steps to Reproduce: 1. Start The installer from the DVD 2. Select Language, Accept the License argement 3. Answer yes or no for the question Actual Results: Installer stopped the "Searching for Linux partitions" step. Expected Results: Start partitioner. openSuSE 11.2 works fine on this computer, no additional configuration requied. The 11.3 RC1 disk checked, and also works on VirtualBoX. -- 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 586643] New: posix_fallocate lets one bypass RLIMIT_FSIZE
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=586643 http://bugzilla.novell.com/show_bug.cgi?id=586643#c0 Summary: posix_fallocate lets one bypass RLIMIT_FSIZE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: opensuse.org(a)contacts.eelis.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=347364) --> (http://bugzilla.novell.com/attachment.cgi?id=347364) Testcase program showing the problem 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 The attached testcase shows that by calling posix_fallocate one can bypass an RLIMIT_FSIZE limit and create a file larger than the limit. The problem appears to be ext4 specific. Reproducible: Always Steps to Reproduce: 1. compile attached testcase, note the 1000 byte file size limit; 2. run testcase; 3. observe that a 1000000 byte file "tmp" has been created. Actual Results: The actual result is that the program creates a 1000000 byte file. Expected Results: The expected result is that the program fails to create a 1000000 byte file, in accordance with the RLIMIT_FSIZE limit. Only seems to happen with ext4. -- 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 6

[Bug 584720] New: ls: cannot access /nfs/turnip/windows: Stale NFS file handle
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=584720 http://bugzilla.novell.com/show_bug.cgi?id=584720#c0 Summary: ls: cannot access /nfs/turnip/windows: Stale NFS file handle Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal 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.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I have an openSUSE 11.2 client and server pair. The server exports a number of filesystems with NFSv4. The pseudo filesystem is using 'crossmnt'. One of the directories under the exported filesystem was removed with rmdir. It was not a mount and was not exported specifically. The client, when listing the mounted filesystem, took some time (it was not instant - perhaps 15-30 seconds) before it noticed that the directory was different somehow, but then misbehaved. Instead of not showing the directory (because it doesn't exist), instead the client reported a Stale NFS file handle. This was unexpected and, IMO, not correct. NOTE: the client is running a KOTD kernel, 2.6.33-25-desktop Summary: Server exports the /exports directory, and with the crossmnt option, everything beneath it. the /exports/windows directory did exist (on the server), but had nothing mounted on it. It was also empty. The client, when listing the mount (on /nfs/turnip), saw /nfs/turnip/windows, as expected. On the server, I removed the directory with rmdir /exports/windows. On the client, ls /nfs/turnip continued to show the windows directory, unexpectedly. At some point, the client began grumping about a stale NFS file handle, and continued to show the windows directory. Eventually, the client stopped grumping, and the windows directory disappeared, as expected. Expected: the windows directory should have disappeared more or less immediately from the client's point of view. Unexpected: the windows directory did not disappear immediately. After some delay the client produced error messages (stale NFS file handle), and then eventually the directory disappeared. I am readily available for debugging. 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 12

[Bug 239420] Enhance message when hotpluggable device can not be disconnected
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=239420 https://bugzilla.novell.com/show_bug.cgi?id=239420#c5 Lubos Lunak <llunak(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED URL| |http://bugs.kde.org/show_bu | |g.cgi?id=201227 Resolution| |UPSTREAM --- Comment #5 from Lubos Lunak <llunak(a)novell.com> 2010-09-08 13:48:17 UTC --- Let's move this upstream - http://bugs.kde.org/show_bug.cgi?id=201227 . -- 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 461871] Screen flicker caused by DDC scan
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=461871 https://bugzilla.novell.com/show_bug.cgi?id=461871#c7 Lubos Lunak <llunak(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |yeoheric(a)gmail.com --- Comment #7 from Lubos Lunak <llunak(a)novell.com> 2010-09-08 13:36:42 UTC --- Does the problem still exist with 11.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 0

[Bug 465606] Recurrent knotify crash in KDE3 on 11.0
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=465606 https://bugzilla.novell.com/show_bug.cgi?id=465606#c13 Lubos Lunak <llunak(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #13 from Lubos Lunak <llunak(a)novell.com> 2010-09-08 13:34:32 UTC --- 11.0 is no longer supported, closing. -- 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 346966] More Options for Repository Refreshing
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=346966 https://bugzilla.novell.com/show_bug.cgi?id=346966#c10 --- Comment #10 from Ricardo Cruz <rpmcruz(a)alunos.dcc.fc.up.pt> 2010-09-08 11:47:27 UTC --- With regard to the screenshots, is such configuratory minutia really necessary? What about just a combo-box with options like "every 2 days", "every 15 days", etc. You could have a "custom" option that would popup the yast2 cron tool, and let you do more esoteric schedules. (If there is no such yast2 cron tool, just show those more advanced options in the form of a window when the user chooses "custom". And maybe try to keep the code abstract, so it can in the future form the basis for a systematic cron job tool.) -- 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 346966] More Options for Repository Refreshing
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=346966 https://bugzilla.novell.com/show_bug.cgi?id=346966#c9 --- Comment #9 from Ricardo Cruz <rpmcruz(a)alunos.dcc.fc.up.pt> 2010-09-08 11:40:51 UTC --- This strategy for refreshing the repository cache seems to be a huge time saver for those of us that use zypper, or the graphical software manager, regularly. Anyway, something to be wary of is that if the repo cache is too outdated, and some package versions were replaced by more recent ones, then this could create havoc during the installation procedure. Remember that zypp downloads and installs package per package. So, if a package is missing and it was going to be installed as a dependency, zypp will only notice it after it has already installed a few others, and then all that sub-branch of the package family may be in jeopardy. It is therefor important for repositories to agree on keeping old packages for a period of X days. And this utility shouldn't let the user defer the auto-refresh schedule beyond those X days (or, at least, strongly advise her against doing so). Maybe there is already such a safety system in place. I dunno. I just saw no mentions it, so I thought of bringing it up. -- 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 632726] New: Gdm-simple-greeter reported as not supporting "save current setup" on each logon
by bugzilla_noreply＠novell.com 08 Sep '10

08 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=632726 https://bugzilla.novell.com/show_bug.cgi?id=632726#c0 Summary: Gdm-simple-greeter reported as not supporting "save current setup" on each logon Classification: openSUSE Product: openSUSE 11.3 Version: Final 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: rkrell(a)gmx.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 Using the GNOME:Stable repository for OpenSUSE 11.3 x86_64: Each time I logon I get a popup: These windows do not support "save current setup" and will have to be restarted manually each time you log in: Gdm-simple-greeter 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 4