- openSUSE Bugs

[Bug 199962] Automatic mounting of USB memory sticks fails
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=199962 coolo(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #9 from coolo(a)novell.com 2006-10-12 05:39 MST ------- well, then. There is no bug left the HAL maintainer says. Christophe, if this happens with the next alpha for you, please open a new bug report against HAL as the cause will be a new one. -- 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 203471] Network Manager - NetworkManager exits on assertion failure (security) with ndiswrapper
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=203471 tambet(a)ximian.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tambet(a)ximian.com |zoz(a)novell.com ------- Comment #3 from tambet(a)ximian.com 2006-10-12 05:18 MST ------- >From the logs it looks like two copies of NetworkManager always get executed at the same time: Sep 2 15:02:28 ecbatana NetworkManager: <information> starting... .. Sep 2 15:02:28 ecbatana NetworkManager: <ERROR> [1157223748.914576] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded. .. Sep 2 15:03:23 ecbatana NetworkManager: <information> starting... .. Sep 2 15:03:25 ecbatana NetworkManager: <information> starting... .. Sep 2 15:03:26 ecbatana NetworkManager: <ERROR> [1157223806.046616] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded. So it seems to be system startup scripts' problem instead of NetworkManager's fault (the fact that it works when run manually from the command line also confirms that). -- 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 121905] Can't set native mode (1680X1050) for Dell 2005FPW
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=121905 russellh(a)ysmail.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |russellh(a)ysmail.net ------- Comment #20 from russellh(a)ysmail.net 2006-10-12 05:03 MST ------- I have this same issue using SLED and a Thinkpad T60 - the native resolution of 1400 x 1050 cannot be set, and despite SaX2 showing this resolution, the 'text screen' and eventual resolution is set to 1280 x 1024. The chipset is intel 945GM -- 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 199962] Automatic mounting of USB memory sticks fails
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=199962 dkukawka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka(a)novell.com |kde-maintainers(a)suse.de ------- Comment #8 from dkukawka(a)novell.com 2006-10-12 05:00 MST ------- I tested usb storage device handling at least with alpha5 as root under KDE and all worked correct for me. -- 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 176285] rug strings for translation
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=176285 swims(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gekker(a)novell.com ------- Comment #5 from swims(a)novell.com 2006-10-12 04:59 MST ------- This is an issue of proofreading and developers adding comments to aid localisation. Gary, do you know who the developer of Rug is? -- 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 210993] New: Booting a new XEN VM fails: "Error: Device 1 (vif) could not be connected. Hotplug scripts not working."
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=210993 Summary: Booting a new XEN VM fails: "Error: Device 1 (vif) could not be connected. Hotplug scripts not working." Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de When trying to install a new XEN VM from a network (NFS) source (as suggested), the VM cannot be created (YaST does not tell the reason to the user). It turns out that the message reads: Error: Device 1 (vif) could not be connected. Hotplug scripts not working. The line: vif = [ 'mac=00:16:3e:ff:3b:18,bridge=xenbr0', 'mac=00:16:3e:c0:92:08,bridge=xenbr1' ] causes that problem. If replaced with vif = [] the VM can be created, but then it cannot locate the installation source via NFS (naturally). -- 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 5

[Bug 211866] New: Screensaver can not be stopped, wrong passwd
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=211866 Summary: Screensaver can not be stopped, wrong passwd Product: openSUSE 10.2 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: w.keegstra(a)rug.nl QAContact: qa(a)suse.de Logging in under Gnome and activating (either automatically or manually) the screensaver results in error message: wrong password. The passwd entry window is shaking (probably NO) and the screensaver is not deactivated. Logging in under KDE the sreensaver (and decativating) is OK. -- 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 1

[Bug 201448] Support for Intel 965 chipsets still missing in intel-agp/i915 module
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=201448 ------- Comment #24 from sndirsch(a)novell.com 2006-10-12 04:20 MST ------- > We will evaluate on the 12th of October the list of patches and decide > which one to add to our kernel. Could you consider this patch for evaluation? Thanks. -- 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 203541] Kernel-Update: Notification Popup not shown in YOU/qt
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=203541 sh(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh(a)novell.com |schubi(a)novell.com ------- Comment #8 from sh(a)novell.com 2006-10-12 04:15 MST ------- According to bug #196201, this popup is a patch message, so this issue is clearly out of reach of the Qt package selector. As you can see in the screen shot in bug #196201 comment #4, this happens during patch installation, long after the package selector. That code is not specific to y2-qt or y2-ncurses. It might be that the message (the message atom) did not get selected for installation, then it would be a solver issue, or that it did get selected, but never got displayed (hard to imagine why this should happen - unlikely IMHO), then it would be a problem of the online update workflow or libzypp. My bets are on the solver. -- 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 204872] gcc stalls / segfaults on compiling libavcodec/xan.c (inside xine-lib)
by bugzilla_noreply＠novell.com 12 Oct '06

12 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=204872 mhopf(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther(a)novell.com, matz(a)novell.com ------- Comment #3 from mhopf(a)novell.com 2006-10-12 03:44 MST ------- No comment for over a month, adding CCs. -- 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