January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 349100] New: Congelamiento en OpenSuSE 10.3
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=349100 Summary: Congelamiento en OpenSuSE 10.3 Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: elpreto(a)hotmail.com QAContact: qa(a)suse.de Found By: Customer Lo que me sucede es que, ya sea con la instación desde el dvd, actualizando el Kernel, con KDE, GNOME y XFCE, es inevitable que la pc se cuelgue en algún momento, no hay un comportamiento único que haga que pase esto. Como dije antes, actualice el kernel, , use GNOME, KDE, XFCE, probé con los drivers de la placa aceleradora de video, sin ellos... cada prueba la hice instalando todo nuevamente desde 0. Mi hardware es: Pentium IV 3.00 GHz, 768 MB RAM 400 MHz, Nvidia GeForce 5200, sonido, red y video integrado VIA Technology. Esto no me pasó ni me pasa en el mismo PC con OpenSuSE 10.0, 10.1 y 102. -- 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 3

[Bug 348565] New: YAST software update extremely slow
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=348565 Summary: YAST software update extremely slow Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: openSUSE 10.2 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: karsten_burger(a)gmx.de QAContact: jsrain(a)novell.com Found By: Customer Hello, I have a quite annoying bug here. I have configured the normal SUSE update repositories and Packman. Now, if I want to install any new software package, the installation process freezes and "parse-metadata" occurs in "top" with 100% CPU usage, FOR ABOUT 20 MINUTES. Even installing a simple package needs about an hour. Opening the "installation sources" needs ages, since data from packman is downloaded (why this?): I intended to deactivate packman, but I lost patience. How can I cleanup this? I found no documentation about this and it is a real pain. -- 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 3

[Bug 334809] New: YaST2 terminates when trying to change package architecture
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=334809#c334783 Summary: YaST2 terminates when trying to change package architecture Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jorschiedt(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Had problem #334783 (#2) - 32bit plugin with 64bit JVM. Tried to resolve by advicing the installer to use the 32bit version of JAVA-1_6_0*sun (see attached screenshot). YaST2 showed the installation window without any package in. YaST2 logfile is also attached. -- 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 347178] New: does not install
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=347178 Summary: does not install Product: openSUSE 11.0 Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: M.Peters40(a)kpnplanet.nl QAContact: jsrain(a)novell.com Found By: Beta-Customer M.B. Peters <M.Peters40(a)kpnplanet.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER?, CCB_Review? system: AMD Athlon 64 X2 Dual Core Processor 4600+ 4GB memory, one IDE drive two SATA drives, graphics: GeForce 8800GTX SUSE 11.0 Alpha0 X86-64 ----------------------------- Disk checked in Yast from SUSE 10.3 GM everything oke... (from power up) First attempt to install (no options) : kernel is loaded, screen goes black and stays that way... (from power up) Second attempt to install (no options) : kernel is loaded and booted, everything looks allright, cancelled instalation after choosing the kde environment... (from hard reset) Third attempt to install (no options) : kernel is loaded, startup screen appears, white line goes 1 cm and stays there, only hard reset (after appr. 5min) brings live back... (from hard reset) Fourth attempt to install (no options) : kernel is loaded, screen goes black and stays that way... (from power up) Fifth attempt to install (no options): kernel is loaded, screen goes black and stays that way... (from hard reset) Sixth attempt to install (no options): kernel is loaded, screen goes black and stays that way,..... I give up and wait for alpha1???? kind regards, Giel Peters. -- 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 347163] New: Problems with disable bcm43xx (enable ndiswrapper)
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=347163 Summary: Problems with disable bcm43xx (enable ndiswrapper) Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: romao2000(a)gmail.com QAContact: qa(a)suse.de Found By: Other I have had problem to disable bcm43xx to put ndiswrapper. The blacklist doesn't work, because I can enable bcm43xx, and I can't enable ndiswrapper. -- 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 346817] New: YaST2 live-installer: MBR is not cleaned before GRUB is written
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=346817 Summary: YaST2 live-installer: MBR is not cleaned before GRUB is written Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: de(a)lincomp.eu QAContact: jsrain(a)novell.com Found By: --- I have tried to install the openSUSE 10.3 live cd using the live-installer on a machine which has lilo already installed in MBR. I have selected to use GRUB instead and noticed that the MBR is not cleaned before GRUB is written to it. This makes the newly installed system unbootable. Best Regards Marcus -- 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 303870] New: x2x mangles X11 keycodes
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=303870 Summary: x2x mangles X11 keycodes Product: openSUSE 10.3 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: werner(a)novell.com ReportedBy: matz(a)novell.com QAContact: sndirsch(a)novell.com CC: dmueller(a)novell.com Found By: --- The problem can be seen in Dirk Muellers mail, where he writes ` (GRAVE ACCENT) instead of either ' (APOSTROPHE) or ’ (RIGHT SINGLE QUOTATION MARK) where he wants to write an apostrophe. He presses the apostrophe key on his german keyboard (and the kmail composer is supposed to transform that into nice Unicode quotation marks). He already determined that the problem seems to stem from his use of x2x. I've no more details, perhaps Dirk has. -- 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 344858] New: Unneccesary Reading of Repositories
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=344858 Summary: Unneccesary Reading of Repositories Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: technodude90(a)gmail.com QAContact: jsrain(a)novell.com Found By: Customer To adjust the date and time via yast2, the repositories are read and one must wait until this process is complete before changing the time. The repositories should only be read while attempting to modify software, ex. install/remove/update. -- 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 344204] New: sound test not playing when changing sound card ID in setup
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=344204 Summary: sound test not playing when changing sound card ID in setup Product: openSUSE 10.3 Version: Final Platform: PC OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: s0.sub.z3r0(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- If you have multiple sound cards and switch their order in YaST2 (set the other as being the 'primary' sound card), it swaps the card playing the test sound. example: Before swapping: 0. Creative PCI. 1. C-Media. After: 0. C-Media 1. Creative PCI Test sound card 1. : sound comes out of card 0. That's it. I've been able to reproduce it without difficulty. I'll try working on a patch. Have a great day/evening/whatever. -- 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

[Bug 223209] New: mysql stop script timeout too short
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=223209 Summary: mysql stop script timeout too short Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: mmarek(a)novell.com ReportedBy: dmueller(a)novell.com QAContact: qa(a)suse.de the mysql stop script does a standard killproc, which sends a -TERM and after 5 seconds a KILL to the daemon. This is not enough for a busy mysql daemon to shut down, and consequently, your database is corrupted or in an inconsistent state afterwards. the example scripts, as they come with the mysql distribution, have a TERM wait of 35 and *no* kill. the debian mysql scripts issue a "mysqladmin shutdown" instead, which is blocking until the daemon terminated. Whatever you decide for, but killing a daemon after 5 seconds is dangerous to your data consistency. filing against 10.2 because I just learned this the hard way, but also applicable to SLES10 (I guess). -- 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 11