March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 483252] New: swig/python detected a memory leak of type 'struct _Pool *', no destructor found.
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=483252 Summary: swig/python detected a memory leak of type 'struct _Pool *', no destructor found. Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)novell.com QAContact: qa(a)suse.de CC: jmatejek(a)novell.com, prusnak(a)novell.com Found By: Product Management Entering an unknown command on the shell triggers the following: % asdf swig/python detected a memory leak of type 'struct _Pool *', no destructor found. This is latest factory, with bash-4.0-4.1 command-not-found-0.1.0-28.35 python-2.6.0-9.9 -- 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 14

[Bug 490890] New: Unable to Upgrade Scribus with 11.1 GA DVD - missing dependencies
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490890 Summary: Unable to Upgrade Scribus with 11.1 GA DVD - missing dependencies Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: Patterns AssignedTo: coolo(a)novell.com ReportedBy: mrdocs(a)opensuse.org QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.8 >From a user on our mailing list: > Scribus wouldn't upgrade with the SuSE RPM on the upgrade dvd. > Error msg: "Requires python-imaging. > Search can't find it on the disk. > Online search of Open SuSE Software found it. > Python-imaging won't install because it requires Python-tk.\Python-tk is > on the disk. > With that installed, I could install python-imaging and then Scribus. > Just an annoying niggle. but I hope it may save someone else a bit of > frustration. Reproducible: Always Steps to Reproduce: 1. 2. 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 1

[Bug 490770] New: crash @ pci passthrough of pci/sata device to DomU
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490770 User pgnet.trash(a)gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490770#c1 Summary: crash @ pci passthrough of pci/sata device to DomU Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: pgnet.trash(a)gmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=283232) --> (https://bugzilla.novell.com/attachment.cgi?id=283232) xen console output for failed domu boot User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 this is referenced split from: "Bug 489846 - pci passthrough error non-page-aligned MMIO BAR found" https://bugzilla.novell.com/show_bug.cgi?id=489846 any help debuggung/fixing this is, of course, appreciated! i'm running openSUSE 11.1, uname -ri 2.6.27.21-7-xen x86_64 booting to Xen, @grub title Xen root (hd0,0) kernel /xen.gz dom0_mem=768M vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 module /vmlinuz-xen root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP vga=0x31a console=tty0 console=xvc0,57600 elevator=cfq max_loop=64 pci_devs_to_hide=(04:07.0)(00:14.0)(04:08.0) reassigndev=0004:07.0 module /initrd-xen passing through two devices to the DomU, cat nas.cfg ... pci = [ '04:07.0', '04:08.0' ] ... where, lspci | egrep "04:07.0|04:08.0" 04:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) 04:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) NOTE: really only want/need "04:08.0", but "04:07.0" needs to come along for the ride (cref: "Bug 489735 - pci passthrough of sata_sil24 device requires that firewire must be co-assigned to the same guest" https://bugzilla.novell.com/show_bug.cgi?id=48973 ) crashes @, xm create -c nas.cfg @console shown below; full output @ Dom0 & DomU is attached ... .. sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA vol_id[790]: segfault at 0 ip 0000000000000000 sp 00007ffffdb25220 error 14 in vol_id[400000+5000] ------------[ cut here ]------------ kernel BUG at mm/mmap.c:2145! invalid opcode: 0000 [1] SMP last sysfs file: /sys/devices/xen/pci-0/pci0000:00/0000:00:01.0/host1/target1:0:0/1:0:0:0/type CPU 0 Modules linked in: sg sd_mod crc_t10dif sata_sil24 libata ohci1394 scsi_mod forcedeth ieee1394 dock rtc_core rtc_lib joydev linear dm_snapshot dm_mod ext3 jbd mbcache xennet xenblk cdrom Supported: Yes Pid: 790, comm: vol_id Not tainted 2.6.27.21-4-xen #1 RIP: e030:[<ffffffff8028a96b>] [<ffffffff8028a96b>] exit_mmap+0xe6/0xf2 RSP: e02b:ffff8800172ddd78 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff8800013a0140 RCX: 0000000000000045 RDX: ffffffffff5fc000 RSI: ffff880016e9d820 RDI: ffff88001780f680 RBP: 0000000000000000 R08: 0000000000000000 R09: ffff880001d92200 R10: 0000000000000010 R11: ffffffff80320c8f R12: ffff880016e9d7c0 R13: ffff880016e9d820 R14: ffff8800172ddf58 R15: ffff8800172ddf08 FS: 00007fe1f5b12780(0000) GS:ffffffff80761080(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process vol_id (pid: 790, threadinfo ffff8800172dc000, task ffff8800168642c0) Stack: 000000000000007d ffff8800013a0140 ffff880016e9d7c0 ffff8800168642c0 ffff880016e9d7c0 ffffffff80230eaa ffff8800168648ac ffffffff80234adf 0000000001241000 ffff8800168642c0 0000000000000001 ffff8800168642c0 Call Trace: [<ffffffff80230eaa>] mmput+0x20/0xbc [<ffffffff80234adf>] exit_mm+0x101/0x10c [<ffffffff80236907>] do_exit+0x208/0x304 [<ffffffff80236aa2>] do_group_exit+0x9f/0xcb [<ffffffff8024028f>] get_signal_to_deliver+0x3b0/0x405 [<ffffffff8020ad3e>] do_signal+0x64/0x191 [<ffffffff8020ae78>] do_notify_resume+0xd/0x2c [<ffffffff8020ba3e>] retint_signal+0x57/0xa9 Code: 7b 18 e8 b5 76 00 00 c7 43 08 00 00 00 00 eb 0b 48 89 ef e8 d4 fe ff ff 48 89 c5 48 85 ed 75 f0 49 83 bc 24 e8 00 00 00 00 74 04 <0f> 0b eb fe 5f 41 58 5b 5d 41 5c c3 41 56 41 be f4 ff ff ff 41 RIP [<ffffffff8028a96b>] exit_mmap+0xe6/0xf2 RSP <ffff8800172ddd78> ---[ end trace de6d924e597e88a3 ]--- Fixing recursive fault but reboot is needed! ---------> xm destroy nas Adding 524280k swap on /dev/mapper/vg0-lv_swap. Priority:-1 extents:1 across:524280k general protection fault: 0000 [2] SMP last sysfs file: /sys/kernel/uevent_seqnum CPU 0 Modules linked in: sg sd_mod crc_t10dif sata_sil24 libata ohci1394 scsi_mod forcedeth ieee1394 dock rtc_core rtc_lib joydev linear dm_snapshot dm_mod ext3 jbd mbcache xennet xenblk cdrom Supported: Yes Pid: 829, comm: vgscan Tainted: G D 2.6.27.21-4-xen #1 RIP: e030:[<ffffffff802ee780>] [<ffffffff802ee780>] sysfs_readdir+0xd9/0x13e RSP: e02b:ffff8800172dfeb8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff8800178fcd20 RCX: ffffffffffffffff RDX: 0000000000000000 RSI: 14ed7f01c5e864b0 RDI: 14ed7f01c5e864b0 RBP: ffff880016e953c0 R08: 0000000000000aaa R09: 000000000000000a R10: 0000000013a97e56 R11: ffffffff803211c1 R12: ffffffff802aabbc R13: ffff8800172dff38 R14: 0000000000000000 R15: ffffffffffffffff FS: 00007fbcf58e0780(0000) GS:ffffffff80761080(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process vgscan (pid: 829, threadinfo ffff8800172de000, task ffff880016420300) Stack: 0000000013a97e56 00000000fffffffe ffff880016e953c0 ffff88001749d6e0 ffff88001749d798 ffffffff802aabbc ffff8800172dff38 ffffffff802aae3f 00000000000000ff 00000000fffffff7 ffff880016e953c0 0000000000000000 Call Trace: [<ffffffff802aae3f>] vfs_readdir+0x75/0xa7 [<ffffffff802aaeeb>] sys_getdents64+0x7a/0xbf [<ffffffff8020b3b8>] system_call_fastpath+0x16/0x1b [<00007fbcf40f4f3a>] 0x7fbcf40f4f3a Code: 61 17 00 48 8b 5b 28 eb 04 48 8b 5b 10 48 85 db 74 74 48 8b 43 38 48 39 45 38 77 ed eb 40 48 8b 73 18 44 88 f0 4c 89 f9 48 89 f7 <f2> ae 4c 89 ef 48 f7 d1 48 8d 41 ff 48 8b 4b 38 89 c2 48 89 4d RIP [<ffffffff802ee780>] sysfs_readdir+0xd9/0x13e RSP <ffff8800172dfeb8> ---[ end trace de6d924e597e88a3 ]--- Reproducible: Always Steps to Reproduce: 1. 2. 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 3

[Bug 483233] New: tap network device not fully supported and breaking routing
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=483233 Summary: tap network device not fully supported and breaking routing Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ralf(a)huelsmann.name QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; InfoPath.2; MS-RTC LM 8; .NET CLR 3.5.21022; OfficeLiveConnector.1.3; OfficeLivePatch.1.3) The tap device seems to be not implented in such way, that it works without a additional bridge. That does not make sense, since the tap itself act a a ethernet broadcast domain (hub) and many usecases (e.g. in virtualization) are perfectly fullfilled with "tap only". while this would not be a big deal, it even breaks the routing by removing the standard gateway each time the network module in Yast is run and brings up partly information about the tap in Yast. Restart parameters seem to be not definable via the sysconfig/network/ifcfg-tap0 . Reproducible: Always Steps to Reproduce: 1. set up a system without a tap, including functional network config with a standard gateway 2. add a tapp via Yast2 (does not matter wether GUI or CLI) 3. try to add an IP-adress to the tap 4. close Yast2 with the tap configured Actual Results: 1. you are not able to add an IP via Yast2 2. your standard gatway is lost (at least on 4 seperate testmachnines on X86, X86_64) Expected Results: 1. you could configure a persistent IP 2. standard gateway is untouched The bad thing is: it breaks the standard gateway. And it breaks it each time you call the network module and finish saving it. The not so bad thing is: IP must be configured at CLI via ifconfig tap0 192.168.100.1. Furthermore the tap is not persistent, so next time you need to go through Yast again (but be beware, standardgateway gets lost) or use CLI tunctl –u root -t tap0 . The setup is documente (in german) at http://www.ralf-haifisch.biz/DE-vbox_auf_suse_11.shtml -- 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 18

[Bug 490568] New: Bootloader sets a wrong root partition on kernel update
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490568 Summary: Bootloader sets a wrong root partition on kernel update Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: mvyskocil(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=283076) --> (https://bugzilla.novell.com/attachment.cgi?id=283076) Yast logs I use a following layout of partitions: /dev/sda1 ext2 /boot /dev/sda2 xfs / /dev/sda3 xfs /media/11_1 /dev/sda4 (extended) /dev/sda5 ext3 /media/11_0 /dev/sda6 xfs /home /dev/sda7 swap So kernel's are placed in separate partition as system. This works well until 11.2. Nowadays every kernel update broke my /boot/grub/menu.lst by changing a root= to sda5 and it must be manually fixed in grub and afterwards in menu.lst. Next boot hangs on 'cannot mount a root partition', because initrd contains only xfs module. But this is correct because root partition is xfs and mkinitrd detects it properly. Used versions: kernel-default-2.6.29-5.2 grub-0.97-157.4 yast2-bootloader-2.18.3-1.7 perl-Bootloader-0.4.90-1.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 5

[Bug 488563] New: Not able to set up wifi on eee-pc-901, after update.
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=488563 User monkey9(a)iae.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=488563#c486267 Summary: Not able to set up wifi on eee-pc-901, after update. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: 32bit OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: zoz(a)novell.com ReportedBy: monkey9(a)iae.nl QAContact: qa(a)suse.de Found By: Beta-Customer As subject: wifi does not work anymore, configuring it manualy does not work. Nm did not work from the start, but now ifup sees the network, but does not connect. I tried the workaround from bug #486267, but that file or folder does not exist: EEE-PC-901-ROB:/home/oddball # rm -r /var/run/dbus/at_console/root rm: kan '/var/run/dbus/at_console/root' niet verwijderen: Bestand of map bestaat niet EEE-PC-901-ROB:/home/oddball # rcnetwork restart Shutting down network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) done ra0 device: RaLink RT2860 done Shutting down service network . . . . . . .done . Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) eth0 is controlled by ifplugd waiting ra0 device: RaLink RT2860 ra0 warning: using NO encryption command 'iwconfig ra0 mode Master' returned Error for wireless request "Set Mode" (8B06) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 nick EEE-PC-901-ROB' returned Error for wireless request "Set Nickname" (8B1C) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 key off' returned Error for wireless request "Set Encode" (8B2A) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 essid linksys' returned Error for wireless request "Set ESSID" (8B1A) : SET failed on device ra0 ; Network is down. done Setting up service network . . . . . . . .done . EEE-PC-901-ROB:/home/oddball # rcnetwork restart Shutting down network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) done ra0 device: RaLink RT2860 done Shutting down service network . . . . . . .done . Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) eth0 is controlled by ifplugd waiting ra0 device: RaLink RT2860 ra0 warning: using NO encryption command 'iwconfig ra0 mode Managed' returned Error for wireless request "Set Mode" (8B06) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 nick EEE-PC-901-ROB' returned Error for wireless request "Set Nickname" (8B1C) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 key off' returned Error for wireless request "Set Encode" (8B2A) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 essid linksys' returned Error for wireless request "Set ESSID" (8B1A) : SET failed on device ra0 ; Network is down. ra0 Starting DHCP4 client. . . . . . . . ra0 DHCP4 continues in background waiting Setting up service network . . . . . . . .done . EEE-PC-901-ROB:/home/oddball # iwconfig lo no wireless extensions. eth0 no wireless extensions. ra0 RT2860 Wireless ESSID:"" Nickname:"RT2860STA" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=10/100 Signal level:0 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 EEE-PC-901-ROB:/home/oddball # iwconfig lo no wireless extensions. eth0 no wireless extensions. ra0 RT2860 Wireless ESSID:"" Nickname:"RT2860STA" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=10/100 Signal level:0 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 EEE-PC-901-ROB:/home/oddball # iwconfig ra0 mode managed EEE-PC-901-ROB:/home/oddball # iwconfig ra0 essid "linksys" EEE-PC-901-ROB:/home/oddball # iwconfig ra0 key open EEE-PC-901-ROB:/home/oddball # iwconfig ra0 channel auto Error for wireless request "Set Frequency" (8B04) : SET failed on device ra0 ; Invalid argument. EEE-PC-901-ROB:/home/oddball # rcnetwork restart Shutting down network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) done ra0 device: RaLink RT2860 done Shutting down service network . . . . . . . . done Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) eth0 is controlled by ifplugd waiting ra0 device: RaLink RT2860 ra0 warning: using NO encryption command 'iwconfig ra0 mode Managed' returned Error for wireless request "Set Mode" (8B06) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 nick EEE-PC-901-ROB' returned Error for wireless request "Set Nickname" (8B1C) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 key off' returned Error for wireless request "Set Encode" (8B2A) : SET failed on device ra0 ; Network is down. command 'iwconfig ra0 essid linksys' returned Error for wireless request "Set ESSID" (8B1A) : SET failed on device ra0 ; Network is down. ra0 Starting DHCP4 client. . . . . . . . ra0 DHCP4 continues in background waiting Setting up service network . . . . . . . . . done EEE-PC-901-ROB:/home/oddball # -- 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 20

[Bug 490004] New: UMTS support broken after latest updates: not allowed to own the service "org.freedesktop.NetworkManager.PPP"
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490004 Summary: UMTS support broken after latest updates: not allowed to own the service "org.freedesktop.NetworkManager.PPP" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Mobile Devices AssignedTo: zoz(a)novell.com ReportedBy: gp(a)novell.com QAContact: qa(a)suse.de CC: security-team(a)suse.de Found By: Product Management After the latest set of updates, I no longer am able to establish a UMTS connection via NetworkManager. >From /var/log/NetworkManager: Mar 28 09:12:22 rana NetworkManager: <info> (/dev/noz0): device state change: 4 -> 5 Mar 28 09:12:22 rana NetworkManager: <WARN> constructor(): Failed to acquire PPP manager service: Connection ":1.6" is not allowed to own the service "org.freedesktop.NetworkManager.PPP" due to security policies in the configuration file Mar 28 09:12:22 rana NetworkManager: nm_ppp_manager_start: assertion `NM_IS_PPP_MANAGER (manager)' failed Mar 28 09:12:22 rana NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace... -- 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 12

[Bug 469784] New: Nautilus : disapearing scroll bar using tabs
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=469784 Summary: Nautilus : disapearing scroll bar using tabs Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jc(a)phocean.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=267925) --> (https://bugzilla.novell.com/attachment.cgi?id=267925) nautilus scroll bar issue User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 When I open a new tab in Nautilus and then go back to the first tab, the scroll bar has disapeared. Refreshing the window makes the scroll bar reappearing. Please check the screenshots. Reproducible: Always Steps to Reproduce: 1. Open Nautilus on a folder that requires scrolling 2. Open a new tab (ctrl-t) 3. Go back to the first tab : the scroll bar has disappeared 4. Refreshing the window (F5) makes the scroll reappearing -- 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 463365] New: Vertcal scroll-bar disappears while switching tabs using Nautilus
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=463365 Summary: Vertcal scroll-bar disappears while switching tabs using Nautilus Product: openSUSE 11.1 Version: Final Platform: 32bit OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: russo.giansergio(a)tiscali.it QAContact: qa(a)suse.de Found By: Community User Vertical scrollbar disappears when switching from one tab to another one in Nautilus (icon-view mode with more than one tab opened). To reinstate the bar a window refresh or resize is needed. -- 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 442475] New: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=442475 Summary: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: Customer If a Yast Application stalls at any point, using the Cancel Button has NO effect on the Yast Application. There needs to have both Cancel and Skip Refresh and Abort buttons operate with a much higher Priority that the Yast Application itself. Using the 'Skip Refresh' button certainly does work most of the time but not 100% of the time - Its Priority still needs to be higher. The cancel or Abort buttons - never close or stop a misbehaving Yast Application or abouts the saving of a Yast Application and is essentially useless. Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU authority or always higher than the Yast Application itself. We have taken for granted that both cancel or Abort buttons never function after we commit to any changes via a Yast Application Window and perhaps it is long overdue for us to correct this -- 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 16