May 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 352790] New: lirc-kernel modules do not work with WinTV PVR150
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=352790 User j.lange(a)epic.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=352790#c1 Summary: lirc-kernel modules do not work with WinTV PVR150 Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: j.lange(a)epic.ca QAContact: qa(a)suse.de Found By: Customer It seems that the version of the lirc (0.8.2) included in 10.3 does not work with the WinTV PVR150. This issue is not unique to openSUSE as a google search turns up many people having this problem with Ubuntu as well. I'm currently trying to test and see if the most recent CVS snapshot of lirc fixes this problem or not and will report back. When the lirc_i2c module is loaded, it either fails to detect the PVR150, or if it does detect it it segfaults. Here is the output from /var/log/messages. -------- Jan 9 01:52:31 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61 Jan 9 01:52:31 mythtv kernel: bttv: driver version 0.9.17 loaded Jan 9 01:52:31 mythtv kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture Jan 9 01:52:31 mythtv kernel: cx2388x v4l2 driver version 0.0.6 loaded Jan 9 01:52:31 mythtv kernel: lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150)) Jan 9 01:52:31 mythtv kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 Jan 9 01:52:31 mythtv kernel: printing eip: Jan 9 01:52:31 mythtv kernel: f96840a9 Jan 9 01:52:31 mythtv kernel: *pde = 00000000 Jan 9 01:52:31 mythtv kernel: Oops: 0000 [#1] Jan 9 01:52:31 mythtv kernel: SMP Jan 9 01:52:31 mythtv kernel: last sysfs file: /block/sda/sda1/stat Jan 9 01:52:31 mythtv kernel: Modules linked in: cx8800 cx88xx bttv video_buf ir_common compat_ioctl32 btcx_risc lirc_i2c lirc_dev snd_pcm_oss snd_mixer_oss snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event snd_seq_midi_emul snd_seq iptable_filter ip_tables ip6table_filter ip6_tables x_tables ipv6 af_packet apparmor loop wm8775 cx25840 tuner snd_emu10k1 snd_via8 2xx snd_ac97_codec ac97_bus snd_util_mem snd_pcm snd_timer snd_page_alloc snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device ohci1 394 snd ns558 emu10k1_gp ieee1394 button gameport ivtv firmware_class i2c_algo_bit i2c_viapro soundcore rtc_cmos via_rhine cx2341x r tc_core tveeprom i2c_core rtc_lib mii parport_pc parport shpchp via_agp pci_hotplug videodev v4l2_common v4l1_compat sr_mod cdrom ag pgart sg linear sd_mod uhci_hcd ehci_hcd ohci_hcd usbcore dm_snapshot edd dm_mod ext3 mbcache jbd fan pata_via sata_via libata scsi_ mod thermal processor Jan 9 01:52:31 mythtv kernel: CPU: 0 Jan 9 01:52:31 mythtv kernel: EIP: 0060:[<f96840a9>] Tainted: G N VLI Jan 9 01:52:31 mythtv kernel: EFLAGS: 00210216 (2.6.22.13-0.3-default #1) Jan 9 01:52:31 mythtv kernel: EIP is at __i2c_check_addr+0x26/0x35 [i2c_core] Jan 9 01:52:31 mythtv kernel: eax: c1f20029 ebx: c1f201e1 ecx: 00000000 edx: 00000071 Jan 9 01:52:31 mythtv kernel: esi: 00000071 edi: c1f20029 ebp: fffffff0 esp: f6319c08 Jan 9 01:52:31 mythtv kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Jan 9 01:52:31 mythtv kernel: Process modprobe (pid: 3992, ti=f6318000 task=f628d030 task.ti=f6318000) Jan 9 01:52:31 mythtv kernel: Stack: f58e9000 f58e9060 f9684c88 00000001 0000ffff 00000001 f58e9000 f92cbcec Jan 9 01:52:31 mythtv kernel: f58e907a c1f20059 f58e9000 f92cbcec f58e907a 00000071 f92cb28b f92cbd52 Jan 9 01:52:31 mythtv kernel: 00000071 f58e9064 000041fd c1f2e08c 00000071 00000000 f6319cac c1f2e08c Jan 9 01:52:31 mythtv kernel: Call Trace: Jan 9 01:52:31 mythtv kernel: [<f9684c88>] i2c_attach_client+0x29/0x175 [i2c_core] Jan 9 01:52:31 mythtv kernel: [<f92cb28b>] ir_attach+0x24c/0x260 [lirc_i2c] Jan 9 01:52:31 mythtv kernel: [<f92cb5a1>] ir_probe+0xa5/0x2ad [lirc_i2c] Jan 9 01:52:31 mythtv kernel: [<c01ce0d7>] radix_tree_node_alloc+0x16/0x51 Jan 9 01:52:31 mythtv kernel: [<c01cc586>] __next_cpu+0x12/0x1e Jan 9 01:52:31 mythtv kernel: [<c011d6aa>] find_busiest_group+0x1d2/0x556 Jan 9 01:52:31 mythtv kernel: [<f96853a6>] i2c_register_driver+0x9e/0xce [i2c_core] Jan 9 01:52:31 mythtv kernel: [<f92cb4f8>] init_module+0x42/0x46 [lirc_i2c] Jan 9 01:52:31 mythtv kernel: [<c0140f7f>] sys_init_module+0x172c/0x1802 Jan 9 01:52:31 mythtv kernel: [<c016fbd2>] do_sync_read+0x0/0x10a Jan 9 01:52:31 mythtv kernel: [<c016fc99>] do_sync_read+0xc7/0x10a Jan 9 01:52:31 mythtv kernel: [<f92a9000>] v4l_compat_ioctl32+0x0/0x8 [compat_ioctl32] Jan 9 01:52:31 mythtv kernel: [<f9330c82>] lirc_register_plugin+0x0/0x448 [lirc_dev] Jan 9 01:52:31 mythtv kernel: [<c0104e22>] sysenter_past_esp+0x6b/0xa9 Jan 9 01:52:31 mythtv kernel: ======================= Jan 9 01:52:31 mythtv kernel: Code: d2 c3 31 c0 c3 56 89 d6 53 8b 88 b8 01 00 00 8d 98 b8 01 00 00 eb 14 0f b7 81 5a fe ff ff 39 f0 75 07 b8 f0 ff ff ff eb 0e 89 d1 <8b> 11 0f 18 02 90 39 d9 75 e2 31 c0 5b 5e c3 56 89 d6 53 89 cb Jan 9 01:52:31 mythtv kernel: EIP: [<f96840a9>] __i2c_check_addr+0x26/0x35 [i2c_core] SS:ESP 0068:f6319c08 -- 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 384824] New: Desktop toolbox problems
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=384824 Summary: Desktop toolbox problems Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: badshah400(a)gmail.com QAContact: qa(a)suse.de Found By: Customer Created an attachment (id=211188) --> (https://bugzilla.novell.com/attachment.cgi?id=211188) Snapshot of desktop toolbox Upon hover Desktop toolbox opens under the application windows and not over them, which is not good because most of the buttons on the desktop toolbox disappear beneath the windows. -- 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 1

[Bug 377984] New: e-d-s deadlock overnight ...
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=377984 Summary: e-d-s deadlock overnight ... Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: mmeeks(a)novell.com QAContact: lakhil(a)novell.com Found By: --- Returned overnight, and hit this deadlock: (gdb) t a a bt Thread 7 (Thread 0xb6c03b90 (LWP 24649)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7258aa7 in *__GI___poll (fds=0xa51e580, nfds=8, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb73999b2 in g_main_context_iterate (context=0x8062968, block=1, dispatch=1, self=0x806bf48) at gmain.c:2945 #3 0xb739a042 in IA__g_main_loop_run (loop=0x806cfe8) at gmain.c:2844 #4 0xb749ce00 in link_io_thread_fn (data=0x0) at linc.c:396 #5 0xb73c075f in g_thread_create_proxy (data=0x806bf48) at gthread.c:635 #6 0xb72dd155 in start_thread (arg=0xb6c03b90) at pthread_create.c:297 #7 0xb726269e in clone () from /lib/libc.so.6 Thread 6 (Thread 0xb2a59b90 (LWP 24683)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7258aa7 in *__GI___poll (fds=0x84eb990, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb73999b2 in g_main_context_iterate (context=0x862fe88, block=1, dispatch=1, self=0x8630330) at gmain.c:2945 #3 0xb739a042 in IA__g_main_loop_run (loop=0x863a240) at gmain.c:2844 #4 0xb7f00962 in startup_mainloop (arg=0x0) at e-book.c:3773 #5 0xb73c075f in g_thread_create_proxy (data=0x8630330) at gthread.c:635 #6 0xb72dd155 in start_thread (arg=0xb2a59b90) at pthread_create.c:297 #7 0xb726269e in clone () from /lib/libc.so.6 Thread 5 (Thread 0xb425cb90 (LWP 24734)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb72e3759 in __lll_lock_wait () from /lib/libpthread.so.0 #2 0xb72dec46 in _L_lock_89 () from /lib/libpthread.so.0 #3 0xb72de552 in __pthread_mutex_lock (mutex=0xb6cb56e4) at pthread_mutex_lock.c:86 #4 0xb6ca8ed2 in delta_thread (data=0x86dc980) at e-cal-backend-groupwise.c:358 #5 0xb73c075f in g_thread_create_proxy (data=0x8965780) at gthread.c:635 #6 0xb72dd155 in start_thread (arg=0xb425cb90) at pthread_create.c:297 #7 0xb726269e in clone () from /lib/libc.so.6 Thread 4 (Thread 0xa4965b90 (LWP 2424)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb72e3ea8 in recv () from /lib/libpthread.so.0 #2 0xb6efb63c in ?? () from /usr/lib/libgnutls.so.26 #3 0x00000019 in ?? () #4 0x0b9e7630 in ?? () #5 0x00000005 in ?? () #6 0x00000000 in ?? () Thread 3 (Thread 0xb325ab90 (LWP 2433)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb72e3759 in __lll_lock_wait () from /lib/libpthread.so.0 #2 0xb72dec46 in _L_lock_89 () from /lib/libpthread.so.0 #3 0xb72de552 in __pthread_mutex_lock (mutex=0xb6cb56e4) at pthread_mutex_lock.c:86 #4 0xb6ca8ed2 in delta_thread (data=0x8c8f648) at e-cal-backend-groupwise.c:358 #5 0xb73c075f in g_thread_create_proxy (data=0xaa98ab8) at gthread.c:635 #6 0xb72dd155 in start_thread (arg=0xb325ab90) at pthread_create.c:297 #7 0xb726269e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb1a14b90 (LWP 26261)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb72e0bf5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb749c862 in link_wait () at linc.c:546 #3 0xb749e9cd in link_connection_try_reconnect (cnx=0x806e948) at linc-connection.c:681 #4 0xb747adae in giop_connection_try_reconnect (cnx=0x806e948) at giop-connection.c:194 #5 0xb748513f in ORBit_try_connection_T (obj=0x9516230) at corba-object.c:276 #6 0xb7485246 in ORBit_object_get_connection (obj=0xfffffe00) at corba-object.c:325 #7 0xb7483e52 in ORBit_small_invoke_stub (obj=0x9516230, m_data=0xb7fe98c0, ret=0x0, args=0xb1a13f50, ctx=0x0, ev=0xb1a13f7c) at orbit-small.c:632 #8 0xb7484119 in ORBit_small_invoke_stub_n (object=0x9516230, methods=0xb, index=<value optimized out>, ret=0x0, args=0xb1a13f50, ctx=0x0, ev=0xb1a13f7c) at orbit-small.c:575 #9 0xb7490daa in ORBit_c_stub_invoke (obj=0x9516230, methods=0xb7fe9984, method_index=14, ret=0x0, args=0xb1a13f50, ctx=0x0, ev=0xb1a13f7c, class_id=13, method_offset=60, skel_impl=0xb7f393a0 <_ORBIT_skel_small_GNOME_Evolution_Addressbook_BookListener_notifyWritable>) at poa.c:2643 #10 0xb7f3b1da in GNOME_Evolution_Addressbook_BookListener_notifyWritable ( _obj=0x9516230, writable=1 '\001', ev=0xb1a13f7c) at Evolution-DataServer-Addressbook-stubs.c:309 #11 0xb7f4753f in e_data_book_report_writable (book=0x9fb4cc0, writable=<value optimized out>) at e-data-book.c:822 #12 0xb7f4295a in e_book_backend_notify_writable (backend=0x83dde60, is_writable=1) at e-book-backend.c:978 #13 0xb6cc9d76 in e_book_backend_file_set_mode (backend=0x83dde60, mode=1) at e-book-backend-file.c:1341 #14 0xb7f42fd0 in e_book_backend_set_mode (backend=0x83dde60, mode=1) at e-book-backend.c:779 #15 0xb7f44e92 in impl_GNOME_Evolution_Addressbook_BookFactory_getBook ( servant=0x8056d34, source_xml=0xa1ef541 "<?xml version=\"1.0\"?>\n<source uid=\"1078399181.29115.1@linux\" name=\"Personal\" relative_uri=\"system\" uri=\"file:///home/michael/.evolution/addressbook/local/system\"><properties><property name=\"completion"..., listener=0xa9a7c20, ev=0xb1a142a8) at e-data-book-factory.c:354 #16 0xb7f3944a in _ORBIT_skel_small_GNOME_Evolution_Addressbook_BookFactory_getBook (_o_servant=0x8056d34, _o_retval=0xb1a14150, _o_args=0xb1a14130, _o_ctx=0xb1a141d8, _o_ev=0xb1a142a8, _impl_getBook=0xb7f44d80 <impl_GNOME_Evolution_Addressbook_BookFactory_getBook>) at Evolution-DataServer-Addressbook-common.c:180 #17 0xb7490b27 in ORBit_POAObject_invoke (pobj=0x8062e78, ret=0xb1a14150, args=0xb1a14130, ctx=0xb1a141d8, data=0xb1a14258, ev=0xb1a142a8) at poa.c:1142 #18 0xb74970b5 in ORBit_OAObject_invoke (adaptor_obj=0x8062e78, ret=0xb1a14150, args=0xb1a14130, ctx=0xb1a141d8, data=0xb1a14258, ev=0xb1a142a8) at orbit-adaptor.c:338 #19 0xb74834de in ORBit_small_invoke_adaptor (adaptor_obj=0x8062e78, recv_buffer=0x9039128, m_data=0xb7fe99c0, data=0xb1a14258, ev=0xb1a142a8) at orbit-small.c:844 #20 0xb7494ba9 in ORBit_POAObject_handle_request (pobj=0x8062e78, opname=0xa7765c4 "getBook", ret=0x0, args=0x0, ctx=0x0, recv_buffer=0x9039128, ev=0xb1a142a8) at poa.c:1351 #21 0xb7495282 in ORBit_POAObject_invoke_incoming_request (pobj=0x8062e78, recv_buffer=0x9039128, opt_ev=0x0) at poa.c:1421 #22 0xb747bd45 in giop_thread_queue_process (tdata=0xa139f88) at giop.c:771 #23 0xb747c078 in giop_request_handler_thread (data=0xa139f88, user_data=0x0) at giop.c:481 #24 0xb73c1df6 in g_thread_pool_thread_proxy (data=0x805b940) at gthreadpool.c:265 #25 0xb73c075f in g_thread_create_proxy (data=0x9f442e8) at gthread.c:635 #26 0xb72dd155 in start_thread (arg=0xb1a14b90) at pthread_create.c:297 #27 0xb726269e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb71846e0 (LWP 24648)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb72e3759 in __lll_lock_wait () from /lib/libpthread.so.0 #2 0xb72dec46 in _L_lock_89 () from /lib/libpthread.so.0 #3 0xb72de552 in __pthread_mutex_lock (mutex=0xb7b4e3c8) at pthread_mutex_lock.c:86 #4 0xb7a9a324 in connection_listen_cb (object=0x806e998, user_data=0xbf33a20) at e-component-listener.c:42 #5 0xb749d601 in link_connection_emit_broken (cnx=0x806e998, callbacks=0xb7b4e3c8) at linc-connection.c:146 #6 0xb749d664 in dispatch_callbacks_drop_lock (cnx=0x806e998) at linc-connection.c:235 #7 0xb749e951 in link_connection_try_reconnect (cnx=0x806e998) at linc-connection.c:678 #8 0xb747adae in giop_connection_try_reconnect (cnx=0x806e998) at giop-connection.c:194 #9 0xb748513f in ORBit_try_connection_T (obj=0x9c2fb30) at corba-object.c:276 #10 0xb7485246 in ORBit_object_get_connection (obj=0xfffffe00) at corba-object.c:325 #11 0xb748266d in ORBit_small_get_connection_status (obj=0x9c2fb30) at orbit-small.c:1297 #12 0xb7a9a368 in connection_listen_cb (object=0x806eb28, user_data=0xc01da80) at e-component-listener.c:48 #13 0xb749d601 in link_connection_emit_broken (cnx=0x806eb28, callbacks=0xb7b4e3c8) at linc-connection.c:146 #14 0xb749e133 in link_connection_broken_idle (data=0x806eb28) at linc-connection.c:167 #15 0xb7394561 in g_idle_dispatch (source=0x863a508, callback=0xfffffe00, user_data=0x806eb28) at gmain.c:4081 #16 0xb7396468 in IA__g_main_context_dispatch (context=0x805b7f0) at gmain.c:2003 #17 0xb7399b23 in g_main_context_iterate (context=0x805b7f0, block=1, dispatch=1, self=0x804f098) at gmain.c:2636 #18 0xb739a042 in IA__g_main_loop_run (loop=0x8072be8) at gmain.c:2844 #19 0xb75270a3 in bonobo_main () at bonobo-main.c:311 #20 0x0804b552 in main (argc=0, argv=Cannot access memory at address 0x84 ) at server.c:418 #0 0xffffe430 in __kernel_vsyscall () (gdb) quit Is it possible we call NotifyWriteable with a mutex held that we should not ? CORBA_Object_duplicate / release are safe & can be used to ensure the CORBA object handle lives during the scope of the notification [ or some other similar ref counting mechanism ]. -- 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 8

[Bug 364628] New: Enable "control reaches end of non-void function" gcc warnings?
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=364628 Summary: Enable "control reaches end of non-void function" gcc warnings? Product: openSUSE 11.0 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: meissner(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: qa(a)suse.de Found By: --- I wonder whether we should enable "control reaches end of non-void function" gcc warnings (RPM_OPT_FLAGS) and even trigger a fatal build error? I think we could safe David's resources (rebuilding each package and filing bugreports) and Novell's resources (bugreport handling) as well. -- 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 8

[Bug 367138] New: opensSUSE Amazon machine image examples
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=367138 Summary: opensSUSE Amazon machine image examples Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: openSUSE 10.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mvdv(a)spamcop.net QAContact: jsrain(a)novell.com Found By: Customer Hi, Appreciate yu have plenty on your plates, but it does seem like Novell/openSUSE have abandoned the compute-cloud market.... there are no public Amazon Machine Images's other than one 32bit example - mostly it is Fedora/RHEL/CentOS. I'd tend to view several 'typical' AMI's as being like DVD images. Are people really going to rush to run SLE on AWS's EC2 if opensuse has no history/'presense'? If it helps RightScale have provided the scripts they use to create some of their CentOS/Fedora images. This should flatten the curve required to get a similar opensuse build script publicized....? https://s3.amazonaws.com/rightscale_scripts/Cent5X86_64V1.12Install.sh HTH? -- 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 381648] New: query property OpenItems of Tree widget broken in Gtk
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=381648 Summary: query property OpenItems of Tree widget broken in Gtk Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: rpmcruz(a)alunos.dcc.fc.up.pt ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Querying the OpenItems property of the Tree widget is broken in Gtk. See ycp-ui-bindings/examples/Tree2.ycp. YaST SVN revision 46821 on openSUSE 10.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 9

[Bug 337657] New: Repository database may corrupt and leave zypper/yast/ opensuseupdater unusable
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=337657 Summary: Repository database may corrupt and leave zypper/yast/opensuseupdater unusable Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Critical Priority: P5 - None Component: libzypp AssignedTo: dmacvicar(a)novell.com ReportedBy: maacruz(a)gmail.com QAContact: dmacvicar(a)novell.com Found By: --- For some unknown circunstance the repository database zypp.db file (probably trying to add a community repository which failed) got damaged. Then: Opensuseupdater failed to show new updates giving no sign of failure or error messages. yast software installation module showed only part of the installed repositories (4 from 8) Trying to add a new repository would fail with a sql error message, both with yast and zypper. Trying to manually refresh one repository ("Update repository") caused yast to segfault. Deleting it and adding it again didn't solved the problem. After deleting all repositories, some could be added again, but trying to add one ("Main OSS repository") caused yast/zypper to hang forever with 100% CPU usage while building the cache Trying to rebuild the database with "zypper -b" didn't solved the problem. The only way I could recover from such situation was to manually deleting zypp.db and adding/refreshing everything again. Crashing/being unable to recover if zypp.db gets corrupted/damaged for whatever reason is a very bad situation. I suggest for yast/zypper, as recovery procedure if a database error is detected: giving an error message, deleting zypp.db and rebuilding everything again from scratch. The user should have an option in yast/zypper to delete and rebuild, too. -- 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 11

[Bug 378889] New: yast2 hostnames doesn't handle tabs in /etc/ hosts correctly
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=378889 Summary: yast2 hostnames doesn't handle tabs in /etc/hosts correctly Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Andreas.Stieger(a)gmx.de QAContact: jsrain(a)novell.com Found By: Customer Created an attachment (id=207285) --> (https://bugzilla.novell.com/attachment.cgi?id=207285) screenshot of incorrectly handled tab charactes when loaded into hostnames modules of yast2 /etc/hosts allows blanks and/or tabs as field separators, according to it's manpage. The YaST2 module Network / Hostnames can correctly handle tab as seperator between field 1 and 2: sam:~ # tail -n 2 /etc/hosts 192.168.1.101 sam.local sam 192.168.1.105 murphy.local murphy sam:~ # tail -n 2 /etc/hosts | hexdump -C 00000000 31 39 32 2e 31 36 38 2e 31 2e 31 30 31 09 73 61 |192.168.1.101.sa| 00000010 6d 2e 6c 6f 63 61 6c_20_ 73 61 6d 0a 31 39 32 2e |m.local sam.192.| 00000020 31 36 38 2e 31 2e 31 30 35 09 6d 75 72 70 68 79 |168.1.105.murphy| 00000030 2e 6c 6f 63 61 6c_20_6d 75 72 70 68 79 0a |.local murphy.| 0000003e but not between hostname and alias, field 2 and 3: sam:~ # tail -n 2 /etc/hosts 192.168.1.101 sam.local sam 192.168.1.105 murphy.local murphy sam:~ # tail -n 2 /etc/hosts | hexdump -C 00000000 31 39 32 2e 31 36 38 2e 31 2e 31 30 31 09 73 61 |192.168.1.101.sa| 00000010 6d 2e 6c 6f 63 61 6c_09_ 73 61 6d 0a 31 39 32 2e |m.local.sam.192.| 00000020 31 36 38 2e 31 2e 31 30 35 09 6d 75 72 70 68 79 |168.1.105.murphy| 00000030 2e 6c 6f 63 61 6c_09_6d 75 72 70 68 79 0a |.local.murphy.| 0000003e The names are not displayed correctly, see screenshot. The corresponding edit dialog is empty. -- 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 5

[Bug 387508] New: SiS662 - Mirage*1 drivers give vertical distortion
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=387508 Summary: SiS662 - Mirage*1 drivers give vertical distortion Product: openSUSE 11.0 Version: Beta 2 Platform: 32bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: bart(a)geesink.org QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- I have an Intel D201GLY board which comes with a SIS chipset. The video chip is a SIS662 Mirage*1. It has some issues: It gives vertical distortions. This was a problem already on openSUSE 10.3, which was fixable by using updated Intel drivers which are available on their website: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=N&Inst=Yes&ProductID=2… However, these do not work with openSUSE Beta2. When I install these (binary) drivers on openSUSE 11.0 Beta2 live CD I get this message in the Xorg logs: (II) Loading extension XFree86-DRI (II) LoadModule: "sis" (II) Loading /usr/lib/xorg/modules//drivers/sis_drv.so (II) Module sis: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 (EE) module ABI major version (1) doesn't match the server's version (2) (II) UnloadModule: "sis" (II) Unloading /usr/lib/xorg/modules//drivers/sis_drv.so (EE) Failed to load module "sis" (module requirement mismatch, 0) The same chipset is on the D201GLY2 board, so guess the same thing happens 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.

1 1

[Bug 280341] New: Inline GPG does not show up in Evolution
by bugzilla_noreply＠novell.com 07 May '08

07 May '08

https://bugzilla.novell.com/show_bug.cgi?id=280341 Summary: Inline GPG does not show up in Evolution Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: jonas(a)trinix.se QAContact: lakhil(a)novell.com When using GnuPG in Evolution inline signatures/crypted messages does not show up. All i get is "signature verified" and I have to klick Reply to see the message. -- 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 14