December 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 200116] USB to serial adapter with PL2303 is not detected proper.
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=200116 haveaniceday(a)cv-sv.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #2 from haveaniceday(a)cv-sv.de 2006-12-02 07:49 MST ------- To be closed -- 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 225605] New: Yast installer doesn't create all /dev entries before first reboot
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=225605 Summary: Yast installer doesn't create all /dev entries before first reboot Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: jsrain(a)novell.com When installing a system, yast doesn't create disk entries /dev/[hs]da* before the first reboot. If the reboot fails, e.g. because of a faulty boot loader installation, booting the rescue system and chroot into it gives trouble because the disks aren't there. Combined with other bugs (wrong boot loader config, yast module hang) this creates a bit of bother. See #225603 for yast logs, and for a real-world scenario when these missing /dev entries are a problem. -- 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 2

[Bug 223773] grub: stage2 problem
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=223773 ------- Comment #12 from jengelh(a)gmx.de 2006-12-02 03:27 MST ------- Yet another comment, including solution. Snapshot state: Works. Case 1: Upgrading grub installs a stage2-only loader, which hangs at next boot. Case 2: Upgrading grub and running grub-install afterwards to have a stage1.5-2-loader, causes a VM machine fault at next boot. Case 3: Upgrading grub, *replacing* /boot/grub/stage2 with /usr/lib/grub/stage2 so that they both have *the same md5* and then running grub-install makes the machine boot successfully. ================================================== Answer to comment #11: grub --batch </etc/grub.conf pokes into /boot/grub/stage2. I suppose GRUB does not get it right and the boot hangs/faults. I suppose the "sync" is not long enough. Also try removing the 2>/dev/null >&1 in the `grub --batch` line. -- 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 223773] grub: stage2 problem
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=223773 ------- Comment #11 from jengelh(a)gmx.de 2006-12-02 02:41 MST ------- Can you tell me what happens? # rpm -q grub grub-0.97-39 # md5sum /boot/grub/stage2 /usr/lib/grub/stage2 8e9c..3cb4 /boot/grub/stage2 (the very older version) 6679..db9f /usr/lib/grub/stage2 Now on upgrade, I had hoped to be everything made straight, but # rpm -Uhv grub-0.97-40.i586.rpm .. # md5sum /boot/grub/stage2 /usr/lib/grub/stage2 d4d9..f354 /boot/grub/stage2 6679..db9f /usr/lib/grub/stage2 What gives? Why does not /boot/grub/stage2 have the same MD5 even though it is copied over from /usr/lib/grub/stage2? When I manually mv & dd like in the %post script, the md5 is correct. What gives? -- 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 208193] New: SuSEconfig has problems with NFS
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=208193 Summary: SuSEconfig has problems with NFS Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)gmx.de QAContact: qa(a)suse.de SuSEconfig seems to have problems when chrooted: # chroot /tftpboot/terran/ # SuSEconfig Starting SuSEconfig, the SuSE Configuration Tool... Running in full featured mode. Reading /etc/sysconfig and updating the system... We do not have enough disk space in /etc. Exit. # df /etc Filesystem 1K-blocks Used Available Use% Mounted on server:/tftpboot/terran 39644928 13418408 26226520 34% / Note that this df entry is synthesized from a specially crafted mtab for later booting by real diskless clients: server:/tftpboot/terran / unionfs rw,dirs=/.STATIC=rw:/.DYNAMIC=nfsro 0 0 Expected result: - successful completion of SuSEconfig, because there _is_ enough space in /etc. -- 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 225396] New: German translation of kopete's settings has a bug
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=225396 Summary: German translation of kopete's settings has a bug Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de In kopete's settings go to Behaviour > General (in German), the second entry in the first box displays: Mit ausgeblendetem Hauptfenster startenStart the "Start" at the end is obsolete. I would have tested with other RCs, but I could not find any torrents to those listed in bugzilla. -- 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 224512] beagle crash
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224512 joeshaw(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vvaradhan(a)novell.com Status|NEW |NEEDINFO Info Provider| |sbrabec(a)novell.com ------- Comment #1 from joeshaw(a)novell.com 2006-12-01 22:24 MST ------- Varadhan updated evo-sharp, can you try with a newer RC? -- 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 223772] New: Manual execution of freshclam requires access to TCP Port 3310 therefore enabling it in System Services should open the Port
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=223772 Summary: Manual execution of freshclam requires access to TCP Port 3310 therefore enabling it in System Services should open the Port Product: SUSE Linux 10.1 Version: Final Platform: i586 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)tpg.com.au QAContact: qa(a)suse.de Manual execution of feshclam requires access to TCP Port 3310. Unless this port is opened manually in SUSE firewall Advanced enabling it as a daemon in system services will result in an incomplete new database being auto downloaded. Some mechanism for Opening Port 3310 and/or including it as a firewall 'service' to be opened rather than use advanced needs to be made for those who activate the daemon. There is also the perception in email conversations that clamAV is only required to protect MS-Windows hosts connected to a SUSE Server - Documentation suggests otherwise. Please consider the GUI KlamAV version 0.7x should be considered a menu option when a KDE desktop is chosen if this GUI is still valid - Documentation is vague on the subject. -- 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 7

[Bug 223968] New: kickoff icon to small after login
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=223968 Summary: kickoff icon to small after login Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: jens(a)khmeros.info QAContact: qa(a)suse.de I changed the size of Kicker to small. And now I have the problem that the icon of Kickoff gets very tiny first but when I hover with the mouse it resizes the icon to the correct size. -- 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 7

[Bug 224081] New: knetwork crashes sigabrt, up to and including latest svn
by bugzilla_noreply＠novell.com 02 Dec '06

02 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224081 Summary: knetwork crashes sigabrt, up to and including latest svn Product: openSUSE 10.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: avuton(a)gmail.com QAContact: qa(a)suse.de I posted this here at the request of http://bugs.kde.org/show_bug.cgi?id=137271 This is actually a gentoo system, but it gives me no choice but say it's opensuse :). I'm not sure it's the same bug but it looks like it and I've got debugging symbols :) Here's what dumps to the console: sbh@rocket ~ % knetworkmanager Session management error: Could not open network socket process 18978: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563. This is normally a bug in some application using the D-Bus library. /usr/lib64/libdbus-1.so.3 [0x2b2390087c8c] /usr/lib64/libdbus-1.so.3 [0x2b2390087319] /usr/lib64/libdbus-1.so.3 [0x2b239007d305] /usr/lib64/libdbus-1.so.3(dbus_connection_dispatch+0x1c8) [0x2b239005d6d8] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt10Connection12dispatchReadEv+0x10) [0x2b238fc113a0] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt10Connection9qt_invokeEiP8QUObject+0x6c) [0x2b238fc11abc] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEP15QConnectionListP8QUObject+0x12a) [0x2b23920539b0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEi+0x1e1) [0x2b23920548e7] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt8Internal10Integrator8slotReadEi+0x46) [0x2b238fc120f6] /usr/lib64/libdbus-qt-1.so.1(_ZN6DBusQt8Internal10Integrator9qt_invokeEiP8QUObject+0x3e) [0x2b238fc1215e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEP15QConnectionListP8QUObject+0x12a) [0x2b23920539b0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN7QObject15activate_signalEii+0x242) [0x2b239205466e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN15QSocketNotifier9activatedEi+0x2a) [0x2b23924450fc] /usr/qt/3/lib64/libqt-mt.so.3(_ZN15QSocketNotifier5eventEP6QEvent+0x40) [0x2b239207a8c0] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication14internalNotifyEP7QObjectP6QEvent+0x27e) [0x2b2391fe0b4e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x28d) [0x2b2391fe2a9d] /usr/kde/3.5/lib/libkdecore.so.4(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x1ea) [0x2b23912ca63a] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication9sendEventEP7QObjectP6QEvent+0x5e) [0x2b2391f69136] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop23activateSocketNotifiersEv+0x108) [0x2b2391fd1986] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop13processEventsEj+0xdbe) [0x2b2391f7f4c8] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop9enterLoopEv+0x72) [0x2b2391ffe69e] /usr/qt/3/lib64/libqt-mt.so.3(_ZN10QEventLoop4execEv+0x2f) [0x2b2391ffe4a7] /usr/qt/3/lib64/libqt-mt.so.3(_ZN12QApplication4execEv+0x22) [0x2b2391fe27a2] /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so(kdemain+0x140) [0x2b238fab08b0] /lib/libc.so.6(__libc_start_main+0xf4) [0x2b239471b394] knetworkmanager [0x400829] ERROR: Communication problem with knetworkmanager, it probably crashed. sbh@rocket ~ % KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = knetworkmanager path = <unknown> pid = 18978 Here's the dump: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47431816559584 (LWP 18978)] [KCrash handler] #5 0x00002b239472d7b5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00002b239472ea4e in *__GI_abort () at abort.c:88 #7 0x00002b2390087335 in _dbus_abort () at dbus-sysdeps.c:84 #8 0x00002b239007d305 in _dbus_warn_check_failed ( format=0x2b2390098860 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283 #9 0x00002b239005d6d8 in dbus_connection_dispatch (connection=0x56b0a0) at dbus-connection.c:4213 #10 0x00002b238fc113a0 in DBusQt::Connection::dispatchRead (this=0x56c4b0) at ./connection.cpp:119 #11 0x00002b238fc11abc in DBusQt::Connection::qt_invoke (this=0x56c4b0, _id=8, _o=0x7fff1b14ff00) at ./connection.moc:112 #12 0x00002b23920539b0 in QObject::activate_signal (this=0x56c5e0, clist=0x5836e0, o=0x7fff1b14ff00) at kernel/qobject.cpp:2356 #13 0x00002b23920548e7 in QObject::activate_signal (this=0x56c5e0, signal=2) at kernel/qobject.cpp:2325 #14 0x00002b238fc120f6 in DBusQt::Internal::Integrator::slotRead ( this=0x56c5e0, fd=<value optimized out>) at ./integrator.cpp:169 #15 0x00002b238fc1215e in DBusQt::Internal::Integrator::qt_invoke ( this=0x56c5e0, _id=2, _o=0x7fff1b1500b0) at ./integrator.moc:233 #16 0x00002b23920539b0 in QObject::activate_signal (this=0x582ec0, clist=0x583340, o=0x7fff1b1500b0) at kernel/qobject.cpp:2356 #17 0x00002b239205466e in QObject::activate_signal (this=0x582ec0, signal=2, param=10) at kernel/qobject.cpp:2449 #18 0x00002b23924450fc in QSocketNotifier::activated (this=0x582ec0, t0=10) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #19 0x00002b239207a8c0 in QSocketNotifier::event (this=0x582ec0, e=0x7fff1b1505b0) at kernel/qsocketnotifier.cpp:258 #20 0x00002b2391fe0b4e in QApplication::internalNotify (this=0x7fff1b150980, receiver=0x582ec0, e=0x7fff1b1505b0) at kernel/qapplication.cpp:2635 #21 0x00002b2391fe2a9d in QApplication::notify (this=0x7fff1b150980, receiver=0x582ec0, e=0x7fff1b1505b0) at kernel/qapplication.cpp:2358 #22 0x00002b23912ca63a in KApplication::notify (this=0x7fff1b150980, receiver=0x582ec0, event=0x7fff1b1505b0) at kapplication.cpp:550 #23 0x00002b2391f69136 in QApplication::sendEvent (receiver=0x582ec0, event=0x7fff1b1505b0) at ../include/qapplication.h:496 #24 0x00002b2391fd1986 in QEventLoop::activateSocketNotifiers (this=0x54c590) at kernel/qeventloop_unix.cpp:578 #25 0x00002b2391f7f4c8 in QEventLoop::processEvents (this=0x54c590, flags=4) at kernel/qeventloop_x11.cpp:383 #26 0x00002b2391ffe69e in QEventLoop::enterLoop (this=0x54c590) at kernel/qeventloop.cpp:198 #27 0x00002b2391ffe4a7 in QEventLoop::exec (this=0x54c590) at kernel/qeventloop.cpp:145 #28 0x00002b2391fe27a2 in QApplication::exec (this=0x7fff1b150980) at kernel/qapplication.cpp:2758 #29 0x00002b238fab08b0 in kdemain () from /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so #30 0x00002b238faeb880 in typeinfo name for QGList () from /usr/kde/3.5/lib/libkdeinit_knetworkmanager.so #31 0x0000000000000000 in ?? () -- 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 3