June 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 575584] New: Kfloppy crashes with signal 11 segment fault
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=575584 http://bugzilla.novell.com/show_bug.cgi?id=575584#c0 Summary: Kfloppy crashes with signal 11 segment fault Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: d_k(a)linuxmail.org QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=339829) --> (http://bugzilla.novell.com/attachment.cgi?id=339829) crash debug output from dos format full option User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Kfloppy is crashing with a message of signal 11 segmentation fault. The versions of kfloppy used were from openSUSE 11.2 x86-64; both the 4.3.1 KDE and the upgrade to 4.3.4 KDE. Several combinations of formatting requests were performed for a 3.5" 1.44MB floppy located at /dev/fd0. All of the following combinations caused a crash: quick format dos full format dos full format dos with verify full format ext2 full format minix The debug version of kfloppy was used and two files are attached to this report. One is the DOS full format request and the second is the DOS quick format request. File system programs appearing in the text window as present prior to crashing were: mkdosfs mke2fs mkfs.minix fdformat dd Symptoms: The format program proceeds through the formatting request with progress bar showing 100% completion. In the case of verify it then proceeds by resetting the progress bar and re-going to 100% completion. At that time the disk remains spinning (short time for format, longer time for verify-almost appears to start over) before crashing. Once (unrepeatable) a full format was requested with a volume label, and kfloppy did not crash. It formatted the floppy and then gave a message "The program /sbin/mkdosfs terminated with an error." within the kfloppy message box. If a known defective floppy disk is formatted with verify request, kfloppy does not crash. It formats the floppy then during the verify step gives an error message "Low-level formatting error at track 42. The program fdformat terminated with an error." within the kfloppy message box. [note: this is expected behavior - the floppy has a bad sector.] Operating the fdformat program from a terminal completes successfully. Operating the mkdosfs program from a terminal completes successfully. Kfloppy was operating successfully under KDE 3.5.8 from openSUSE 10.3, and immediately failed upon upgrade. Hardware and disks are sound. Speculation: The crash appears when underlying programs have completed and kfloppy should be giving a success message. If the format is a failure then the failure reporting system appears to be operating correctly. Code around the successful completion message should be checked. Reproducible: Always Steps to Reproduce: 1 format floppy disk with kfloppy Actual Results: crash - segmentation fault -- Configure bugmail: http://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 558898] New: pam_env does not process /etc/environment if autologin is enabled
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=558898 http://bugzilla.novell.com/show_bug.cgi?id=558898#c0 Summary: pam_env does not process /etc/environment if autologin is enabled Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: rbyshko(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 Hi, in order to have my sound use PulseAudio I ran setup-pulseaudio which adds several variables to /etc/environment. The problem is: this file is NOT processed if I have autologin enabled. Is it hidden feature? :) Please feel free to ask me any other additional information. Reproducible: Always Steps to Reproduce: 1.Add some environment variable to /etc/environment 2.Enable autologin 3.Reboot 4.Check if the environment variable set. Actual Results: Environment variable is not set. Expected Results: Environment variable should be set even for autologin case. -- Configure bugmail: http://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 557052] New: audio cds not mounted properly in KDE 4.3.3
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=557052 http://bugzilla.novell.com/show_bug.cgi?id=557052#c0 Summary: audio cds not mounted properly in KDE 4.3.3 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: dafydd(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 after yesterday's update to: kdemultimedia4-4.3.3-1.8.i586 and other kde components when i tried to open an audio cd, Amarok considered the CD to have been empty while dolphin refused to open it noting that the user has no permission to browse the CD. i tried a workaround and added the user to the cdrom group. it helped as the cds started to mount. however, the cds cannot be read by any music player nor can i open any files stored on the cds (permission denied) unless i copy them to my hard drive. what's interesting, i browsed the /var/log/messages file and found the following information appearing when mounting the cds: Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412285] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412304] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412316] Info fld=0x0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412322] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412335] end_request: I/O error, dev sr0, sector 0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412344] __ratelimit: 25 callbacks suppressed Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412351] Buffer I/O error on device sr0, logical block 0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412363] Buffer I/O error on device sr0, logical block 1 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412371] Buffer I/O error on device sr0, logical block 2 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412379] Buffer I/O error on device sr0, logical block 3 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412387] Buffer I/O error on device sr0, logical block 4 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412395] Buffer I/O error on device sr0, logical block 5 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412402] Buffer I/O error on device sr0, logical block 6 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412410] Buffer I/O error on device sr0, logical block 7 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412418] Buffer I/O error on device sr0, logical block 8 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.412425] Buffer I/O error on device sr0, logical block 9 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.413766] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 19 09:47:15 linux-iy98 kernel: [ 6788.413785] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Nov 19 09:47:15 linux-iy98 kernel: [ 6788.413797] Info fld=0x0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.413802] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Nov 19 09:47:15 linux-iy98 kernel: [ 6788.413816] end_request: I/O error, dev sr0, sector 0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.488080] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 19 09:47:15 linux-iy98 kernel: [ 6788.488104] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Nov 19 09:47:15 linux-iy98 kernel: [ 6788.488116] Info fld=0x0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.488121] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Nov 19 09:47:15 linux-iy98 kernel: [ 6788.488135] end_request: I/O error, dev sr0, sector 0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.489562] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 19 09:47:15 linux-iy98 kernel: [ 6788.489580] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Nov 19 09:47:15 linux-iy98 kernel: [ 6788.489591] Info fld=0x0 Nov 19 09:47:15 linux-iy98 kernel: [ 6788.489597] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Nov 19 09:47:15 linux-iy98 kernel: [ 6788.489609] end_request: I/O error, dev sr0, sector 0 adding the user to the audio and disk groups does not help. data cds and dvds work fine. before the update, everything worked flawlessly. Reproducible: Always Steps to Reproduce: 1. update KDE using the KDE:/43 repository 2. try to play a CD Actual Results: a cd will mount if you add your user to the cdrom group but you won't be able to open any file on the cd (but you can copy it to your hard drive). Expected Results: tracks on audio cds should be played directly from the cds without the need to copy them to hard drive -- Configure bugmail: http://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 616762] New: Khmer fonts not included
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=616762 http://bugzilla.novell.com/show_bug.cgi?id=616762#c0 Summary: Khmer fonts not included Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jl.verissimo(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=371244) --> (http://bugzilla.novell.com/attachment.cgi?id=371244) Installer language selection (screenshot) User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.4) Gecko/20100527 SUSE/3.6.4-2.2 Firefox/3.6.4 Khmer fonts not included in the installer (11.3 RC1 Gnome Live). I haven't performed a complete installation, but both the language selection window and the partitioning screen show many characters that cannot be represented (see screenshot). Reproducible: Always Steps to Reproduce: 1.Select khmer language in the installer. 2. 3. Actual Results: Khmer characters cannot be represented. Expected Results: Khmer characters should appear. -- Configure bugmail: http://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 618514] New: Multiple warnings and error messages in installing vanilla 2.6.34 kernel
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=618514 http://bugzilla.novell.com/show_bug.cgi?id=618514#c0 Summary: Multiple warnings and error messages in installing vanilla 2.6.34 kernel Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: suse(a)tlinx.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=372698) --> (http://bugzilla.novell.com/attachment.cgi?id=372698) linux kernel configuration file User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 I built the 2.6.34 kernel and upon intalling, I see several warnings and messages. Some of the warnings are because the build process assumes I am including old hardware in my build that doesn't apply to my system. Error messages are as follows: Ishtar:linux/ish-2634> sudo make install modules_install sh /home/linux/ish-2634/arch/x86/boot/install.sh 2.6.34T610-Vanilla arch/x86/boot/bzImage \ System.map "/boot" Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.34T610-Vanilla Initrd image: /boot/initrd-2.6.34T610-Vanilla Root device: /dev/disk/by-id/scsi-360024e8078d76a00ff000049049b00b0-part1 (/dev/sdb1) (mounted on / as xfs) modprobe: Module pata_acpi not found. WARNING: no dependencies for kernel module 'pata_acpi' found. modprobe: Module ata_piix not found. WARNING: no dependencies for kernel module 'ata_piix' found. modprobe: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. modprobe: Module ohci_hcd not found. WARNING: no dependencies for kernel module 'ohci_hcd' found. Kernel Modules: edd Features: block usb resume.userspace resume.kernel 20320 blocks 2010-06-29 16:18:45 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev 2010-06-29 16:18:51 ERROR: UDEVMAPPING: dmdev /dev/dm-0 doesn't have defined DM_NAME in udev ... Then lilo needs the DEVMAPPER option: shtar:linux/ish-2634> sudo lilo Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Warning: device-mapper (252) referenced in /proc/partitions, but LILO is configured without DEVMAPPER option. Skipping device. Added 2634-Van * Added 26334-Van Added 26332-Van Added 26331-Van Added Params-1 Added Linux_2631123 Added SUSE_LINUX Added Failsafe 12 warnings were issued. --------------- Now the lilo messages can be ignored if you are not booting from a logical volume, but if you are -- it's not likely to work. I want it to work -- as I want to move all my files systems to lvm. Please support lilo again in full -- I have way too many recurring problems with grub, and grub has serious bugs when you use xfs as a boot disk that lilo DOESN'T have. I'll include my config file -- that should allow you to generate the same kernel and see whatever problems I have. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 618891] New: NetworkManager from today is not updating resolv.conf anymore
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=618891 http://bugzilla.novell.com/show_bug.cgi?id=618891#c0 Summary: NetworkManager from today is not updating resolv.conf anymore Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: adrian(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: Yes I do not get nameserver lines anymore in /etc/resolv.conf after updating to todays factory. It did almost only update the NetworkManager package itself. IP is set and I see correct nameserver in logfile: Jun 30 21:18:11 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Jun 30 21:18:11 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete. Jun 30 21:18:11 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.020365] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.021824] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012 Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.021880] write_to_netconfig(): Writing to netconfig: DNSSERVERS='10.99.0.1'#012 Jun 30 21:18:12 localhost NetworkManager: <info> Clearing nscd hosts cache. Jun 30 21:18:12 localhost NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0) Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.024391] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.027794] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012 Jun 30 21:18:12 localhost NetworkManager: <debug> [1277925492.027914] write_to_netconfig(): Writing to netconfig: DNSSERVERS='10.99.0.1'#012 Jun 30 21:18:12 localhost NetworkManager: <info> Clearing nscd hosts cache. Jun 30 21:18:12 localhost NetworkManager: <info> Policy set 'zu Hause' (wlan0) as default for routing and DNS. Jun 30 21:18:12 localhost NetworkManager: <info> Activation (wlan0) successful, device activated. Jun 30 21:18:12 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Jun 30 21:18:12 localhost nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 591697] New: 'Failed to get channel info for channel 140' error with iwl3945 using NetworkManager
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=591697 http://bugzilla.novell.com/show_bug.cgi?id=591697#c0 Summary: 'Failed to get channel info for channel 140' error with iwl3945 using NetworkManager Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: korossy.p(a)freemail.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=351023) --> (http://bugzilla.novell.com/attachment.cgi?id=351023) /var/log/NetworkManager User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.1 (like Gecko) SUSE If I switch to NetworkManager, according to KNetworkmanager my iwl3945 interface seems to be connected to my WPA-PSK AP, but in fact I cannot reach the internet through it. I've got 'Failed to get channel info for channel 140' error messages in dmesg. Switching back to traditional ifup method it connets and works without problem. Reproducible: Always Steps to Reproduce: 1.Switch to Networkmanager in Yast - no internet connection 2.Switch back to ifup/ifdown in Yast - internet connection works 3. Actual Results: No internet connection with Networkmanager via iwl3945 Expected Results: Working internet connection with NetworkManager via iwl3945 -- Configure bugmail: http://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 618704] New: network manager disabled when login after hibernation.
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=618704 http://bugzilla.novell.com/show_bug.cgi?id=618704#c0 Summary: network manager disabled when login after hibernation. Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suvarchal.kumar(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100527 SUSE/3.6.4-2.7 Firefox/3.6.4 although this bug was reported before in "http://bugzilla.novell.com/show_bug.cgi?id=589978 " it's current status is closed. The bug still exists when login after hibernation and successive restarts thereafter. There is temporary fix to the bug by deleting /var/lib/NetworkManager/NetworkManager.state after login from hibernation so that it doesn’t reappear after next restarts. Reproducible: Always Steps to Reproduce: 1.connect to a network 2.hibernate 3.relogin from hibernation --bug exists 4.restart - the bug still exists Actual Results: network manager disabled Expected Results: network manager disabled -- Configure bugmail: http://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 590853] New: Lights Off game crashes at start
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=590853 http://bugzilla.novell.com/show_bug.cgi?id=590853#c0 Summary: Lights Off game crashes at start Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: schaiba(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 When clicking on its entry in the Gnome menu, Lights Off creates a window for a moment, which then disappears. Starting from console gives me : arares@linux-5ayr:~> lightsoff /home/arares/.themes/Clearlooks-NeXT/gtk-2.0/gtkrc:49: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/arares/.themes/Clearlooks-NeXT/gtk-2.0/gtkrc:50: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/arares/.themes/Clearlooks-NeXT/gtk-2.0/gtkrc:51: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. The program 'seed' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadContextTag'. (Details: serial 463 error_code 170 request_code 153 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I notice that /usr/bin/lightsoff is a sh script and I can't tell where is the executable in order to debug it. Reproducible: Always Steps to Reproduce: 1.Start lightsoff 2. 3. -- Configure bugmail: http://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 618880] New: openSUSE 11.2 and 11.3 RC1 remote install via VNC fails
by bugzilla_noreply＠novell.com 01 Jul '10

01 Jul '10

http://bugzilla.novell.com/show_bug.cgi?id=618880 http://bugzilla.novell.com/show_bug.cgi?id=618880#c0 Summary: openSUSE 11.2 and 11.3 RC1 remote install via VNC fails Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: clifford(a)taylormade.ae QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; InfoPath.2; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322; OfficeLiveConnector.1.4; OfficeLivePatch.1.3) Hello, Remote installation of openSUSE 11.2 and 11.3 RC1 via VNC fails, used to work fine on openSUSE 11.1. During installation vnc=1 vncpassword=PASSWORD would start the remote installation and I used to connect via the browser http://ipaddress:5801 Please help to report this bug to openSUSE Development Team before openSUSE 11.3 is released. Clifford Gonsalves Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1