- openSUSE Bugs

[Bug 204376] None of the actually not mounted media is displayed on the system information page in KDE
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=204376 coolo(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #29 from coolo(a)novell.com 2006-10-09 03:53 MST ------- ok, fixed for KDE -- 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, or are watching someone who is.

1 0

[Bug 206358] New: kdm configuration lost after KDE updates
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=206358 Summary: kdm configuration lost after KDE updates Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: uli.2001(a)gmx.de QAContact: kde-maintainers(a)suse.de I have configured kdm to automatically log in a certain user (using the "Anmeldungsmanager" part of "Kontrollzentrum", as root). I update KDE regularly automatically through http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/ Whenever there are major KDE updates, my settings are lost. -- 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, or are watching someone who is.

1 4

[Bug 198125] fglrx driver does not support X.Org > 7.1 / Mesa > 6.4.2
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=198125 sndirsch(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pnemec(a)novell.com ------- Comment #8 from sndirsch(a)novell.com 2006-10-09 03:49 MST ------- *** Bug 209898 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.

1 0

[Bug 209798] New: module not loadable after nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=209798 Summary: module not loadable after nvidia-gfx-kmp-default- 1.0.8762_2.6.16.21_0.8-1 Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: novell(a)JonnyJD.net QAContact: jsrain(a)novell.com My Kernel is 2.6.16.21-0.25-default I installed x11-video-nvidia-1.0.8762-1 nvidia-gfx-kmp-default-1.0.8762_2.6.16.21_0.8-1 from download.nvidia.com/novell via Yast as root in failsafe mode (also other tries with other modes) to get my GeForce 6200 working. (as in http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html#3) The I do sax2 -r to configure X. With that command I get an error and I have that in SaX.log: (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (==) NVIDIA(0): Using HW cursor (**) NVIDIA(0): Enabling RENDER acceleration (==) NVIDIA(0): Video key set to default value of 0x101fe FATAL: Error inserting nvidia (/lib/modules/2.6.16.21-0.25-default/weak-updates/nvidia.ko): No such device (EE) NVIDIA(0): Failed to load the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (II) UnloadModule: "ramdac" (II) UnloadModule: "fb" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found and at the same time that in dmesg: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. NVRM: The NVIDIA probe routine was not called for 1 device(s). NVRM: This can occur when a driver such as rivafb, nvidiafb or NVRM: rivatv was loaded and obtained ownership of the NVIDIA NVRM: device(s). NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb NVRM: support), then try loading the NVIDIA kernel module again. NVRM: No NVIDIA graphics adapter probed! I have the complete SaX.log and an nvidia-bug-report.log if somebody tells me where I can send them. So the graphics aren't working. The problem is not the nvidia driver since I have a working system doing the following: start as root in failsafe sh NVIDIA-Linux-x86-1.0-8762-pkg1.run -q (same version as in the package, there is also a newer 8774 available) sax2 -r -m 0=nvidia (the other option in the HOWTO for "People who aren't afraid") Then I reboot in runlevel 5 and have a working 3D acceleration. My guess would be, that there is some problems with the Suse-packed precompiled nvidia-packages. That's why I'm posting it here. See: http://www.nvnews.net/vbulletin/showthread.php?p=1007990 You can also find more logs and details about my "progress" -- 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, or are watching someone who is.

1 6

[Bug 195040] Stale NFS handles with kernel 2.6.16.21-0.13
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=195040 kgw(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|kernel:sles10 |fixreleased:kernel:sles10 ------- Comment #34 from kgw(a)novell.com 2006-10-09 03:20 MST ------- nfsd-auth-properly: Patch published in kernelupdate 2.6.16.21-0.25, dated Sep 19, 2006 & released Sep 27, 2006. Setting Whiteboard Status -> fixreleased -- 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, or are watching someone who is.

1 0

[Bug 152099] kernel oops at boot
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=152099 kgw(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|kernel:sles10 |fixreleased:kernel:sles10 ------- Comment #20 from kgw(a)novell.com 2006-10-09 03:17 MST ------- truncate-soft-lockup: Patch published in kernelupdate 2.6.16.21-0.25, dated Sep 19, 2006 & released Oct 04, 2006. Setting Whiteboard Status -> fixreleased -- 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, or are watching someone who is.

1 0

[Bug 150311] powersave does not restart sound daemon
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=150311 ------- Comment #20 from seife(a)novell.com 2006-10-09 03:09 MST ------- ok, this looks like it has not even been stopped, so it won't be started either of course. Up in the logfile, is there something like "stopping alsasound"? also the contents of /var/lib/suspend2disk-state.resume would be interesting. Sorry that this is a bit tedious to debug :-) -- 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, or are watching someone who is.

1 0

[Bug 203526] PolicyKit PAM file includes nonexisting config files
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=203526 kukuk(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Comment #2 from kukuk(a)novell.com 2006-10-09 03:07 MST ------- It is still there. -- 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, or are watching someone who is.

1 0

[Bug 198216] Package mol-0.9.71_pre8-2.src.rpm does not build (=Mac On Linux for PPCs)
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=198216 kgw(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |fixreleased:kernel: sles10 ------- Comment #7 from kgw(a)novell.com 2006-10-09 03:02 MST ------- suse-ppc32-mol-kbuild.patch: Patch published in SL 10.1 and SLES-10 kernelupdates 2.6.16.21-0.25, dated Sep 19, 2006 & released Sep 27, 2006. Setting Whiteboard Status -> fixreleased -- 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, or are watching someone who is.

1 0

[Bug 208841] New: Berhaviour does not match selection
by bugzilla_noreply＠novell.com 09 Oct '06

09 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=208841 Summary: Berhaviour does not match selection Product: openSUSE 10.2 Version: Alpha 4 Platform: 64bit OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hugo.costelha(a)gmail.com QAContact: jsrain(a)novell.com Do the following: 1. Start the installation 2. Proceed until you reach the "Installation Mode" 3. Select "Other Options" ---> By default, "Repair Installed System" is selected. However, pressing "Next" behaves as if the "Boot Installed System" option was selected instead. If I click on "Boot Installed System" and then on "Repair Installed System", then it behaves correctly, i.e., it starts the repair procedure. -- 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, or are watching someone who is.

1 4