June 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 368800] New: build status wrongly inaccuracy
by bugzilla_noreply＠novell.com 29 Mar '09

29 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=368800 Summary: build status wrongly inaccuracy Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: poeml(a)novell.com QAContact: adrian(a)novell.com Found By: --- The build status "succeeded" often doesn't reflect reality. A packager frequently sees the following. First, after a commit: poeml@batavia510 ~/bs/openSUSE:Tools/osc % osc results CentOS_5 i586 scheduled CentOS_5 x86_64 building Debian_Etch i586 scheduled Debian_Etch x86_64 scheduled Fedora_7 i586 succeeded Fedora_7 x86_64 scheduled Fedora_8 i586 succeeded Fedora_8 x86_64 succeeded Fedora_Core_6 i586 succeeded Fedora_Core_6 x86_64 succeeded Mandriva_2006 i586 succeeded Mandriva_2007 i586 succeeded Mandriva_2007 x86_64 succeeded Mandriva_2008 i586 succeeded Mandriva_2008 x86_64 succeeded openSUSE_10.2 i586 succeeded openSUSE_10.2 x86_64 succeeded openSUSE_10.3 i586 succeeded openSUSE_10.3 x86_64 succeeded openSUSE_Factory i586 succeeded openSUSE_Factory x86_64 succeeded RHEL_5 i586 succeeded RHEL_5 x86_64 succeeded SLES_9 i586 disabled SLES_9 x86_64 disabled SLE_10 i586 succeeded SLE_10 x86_64 succeeded SUSE_Linux_10.1 i586 succeeded SUSE_Linux_10.1 x86_64 succeeded xUbuntu_6.06 i586 succeeded xUbuntu_7.04 i586 succeeded xUbuntu_7.10 i586 succeeded xUbuntu_7.10 x86_64 succeeded Fine -- I just don't believe it's succeeded already, because I committed only a minute ago. But I know what to think. Later, things get confusing: poeml@batavia510 ~/bs/openSUSE:Tools/osc % osc results CentOS_5 i586 finished CentOS_5 x86_64 building Debian_Etch i586 succeeded Debian_Etch x86_64 succeeded Fedora_7 i586 succeeded Fedora_7 x86_64 succeeded Fedora_8 i586 succeeded Fedora_8 x86_64 succeeded Fedora_Core_6 i586 finished Fedora_Core_6 x86_64 succeeded Mandriva_2006 i586 succeeded Mandriva_2007 i586 finished Mandriva_2007 x86_64 succeeded Mandriva_2008 i586 succeeded Mandriva_2008 x86_64 building openSUSE_10.2 i586 building openSUSE_10.2 x86_64 succeeded openSUSE_10.3 i586 finished openSUSE_10.3 x86_64 succeeded openSUSE_Factory i586 finished openSUSE_Factory x86_64 succeeded RHEL_5 i586 building RHEL_5 x86_64 succeeded SLES_9 i586 disabled SLES_9 x86_64 disabled SLE_10 i586 succeeded SLE_10 x86_64 succeeded SUSE_Linux_10.1 i586 succeeded SUSE_Linux_10.1 x86_64 succeeded xUbuntu_6.06 i586 succeeded xUbuntu_7.04 i586 succeeded xUbuntu_7.10 i586 finished xUbuntu_7.10 x86_64 succeeded Can you tell which of them are already succeeded, and which ones are still "succeeded"? It would be better if the commit would invalidate the "succeeded" state. The "succeeded should only be reached again once the package has actually been built (successfully of course). -- 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 405104] New: NetworkManager-kde-0.7r821737-5.7 doesn't connect
by bugzilla_noreply＠novell.com 29 Mar '09

29 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=405104 Summary: NetworkManager-kde-0.7r821737-5.7 doesn't connect Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dl9pf(a)gmx.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=225157) --> (https://bugzilla.novell.com/attachment.cgi?id=225157) Log of NetworkManager I updated to NetworkManager-kde-0.7r821737-5.7. But as before it refuses to connect to my wlan. nm-applet just works. Attached is /var/log/NetworkManager of a run with knetworkmanager and a run with nm-applet. I was able to establish a connection only with nm-applet. Environment: openSUSE 11.0 $ hwinfo --wlan 01: PCI 800.0: 0282 WLAN controller [Created at pci.310] UDI: /org/freedesktop/Hal/devices/pci_8086_4229 Unique ID: y9sn.AI5DsHTk+F7 Parent ID: hoOk.0O_DsNnPKTD SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:08:00.0 SysFS BusID: 0000:08:00.0 Hardware Class: network Model: "Intel PRO/Wireless 4965 AG or AGN Network Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4229 "PRO/Wireless 4965 AG or AGN Network Connection" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1101 Revision: 0x61 Driver: "iwl4965" Driver Modules: "iwl4965" Device File: wlan0 Features: WLAN Memory Range: 0xfa000000-0xfa001fff (rw,non-prefetchable) IRQ: 4345 (no events) HW Address: 00:13:e8:68:51:9b Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d00004229sv00008086sd00001101bc02sc80i00" Driver Info #0: Driver Status: iwl4965 is active Driver Activation Cmd: "modprobe iwl4965" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #13 (PCI bridge) AP: WEP, 128bit, SharedKey -- 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 10

[Bug 394552] New: Impossible to enter shares in the network.
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=394552 Summary: Impossible to enter shares in the network. Product: openSUSE 11.0 Version: Beta 3 Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: monkey9(a)iae.nl QAContact: qa(a)suse.de Found By: Beta-Customer Samba maintainers say it is a kde bug... (not me..) See error message in screenshot. -- 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 372261] New: Kdebase-samba module not accessible.
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=372261 Summary: Kdebase-samba module not accessible. Product: openSUSE 11.0 Version: Factory Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: monkey9(a)iae.nl QAContact: qa(a)suse.de Found By: Beta-Customer There is no option to set the proper options to login linuxshares, not from linux, nor from other os. This module is, unfortunately, needed to grant guest logins, or set passwords. As the samba alone, is not enough to arrange logins into linux shares. Now, the password requester pops up, but as there is no possibility to set a password or username, there is no possibility to get into the shares. If you ask me, why is samba alone not enough? -- 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 7

[Bug 400004] New: /etc/profile.d/desktop-data.sh causes DNS lookup
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=400004 Summary: /etc/profile.d/desktop-data.sh causes DNS lookup Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: stbinner(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- /etc/profile.d/desktop-data.sh runs hostname -f. This causes a DNS lookup that may take quite a while to fail on disconencted systems. Please find a solution that doesn't require network connectivity. -- 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 340331] New: Tray icon of KNetworkmanager not transparent
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=340331#c331580 Summary: Tray icon of KNetworkmanager not transparent Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: ma2412ma(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=182688) --> (https://bugzilla.novell.com/attachment.cgi?id=182688) Tray icon for KNetworkmanager should be transparent In addition to not redrawing correctly (see bug #331580), the icon is also not transparent in the background - see attached screenshot. -- 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 343874] New: If the system hybernates with an usb external drive mounted, weird things happen
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343874 Summary: If the system hybernates with an usb external drive mounted, weird things happen Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- I hibernated forgotting to umount a manually mounted external HD on USB. The disk was on sda1, and mounted using this fstab line: LABEL=usb_sg60 /mnt/usb/usb_sg60 reiserfs noatime,user,noauto,acl,user_xattr 0 0 After hibernating, the disk moves to sdb1: nimrodel:~ # l /dev/disk/by-label/ | grep usb_sg60 lrwxrwxrwx 1 root root 10 Nov 24 14:10 usb_sg60 -> ../../sdb1 but the kernel thinks it is still mounted on sda1: nimrodel:~ # mount -l | grep usb_sg60 /dev/sda1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) and it is possible to remount it correctly: nimrodel:~ # umount /mnt/usb/usb_sg60 nimrodel:~ # mount /mnt/usb/usb_sg60 nimrodel:~ # mount -l | grep usb_sg60 /dev/sdb1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) [usb_sg60] but sda has dissapeared: nimrodel:~ # l /dev/sd?* brw-r----- 1 root disk 8, 16 Nov 24 14:10 /dev/sdb brw-r----- 1 root disk 8, 17 Nov 24 14:10 /dev/sdb1 Here goes the kernel log: Nov 24 14:09:32 nimrodel kernel: swsusp: critical section: Nov 24 14:09:32 nimrodel kernel: swsusp: Need to copy 113403 pages Nov 24 14:09:32 nimrodel kernel: Intel machine check architecture supported. Nov 24 14:09:32 nimrodel kernel: Intel machine check reporting enabled on CPU#0. Nov 24 14:09:32 nimrodel kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) available Nov 24 14:09:32 nimrodel kernel: CPU0: Thermal monitoring enabled Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Nov 24 14:09:32 nimrodel kernel: PM: Writing back config space on device 0000:00:1f.5 at offset 1 (was 2800005, writing 2800001) Nov 24 14:09:32 nimrodel kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 19 Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 Nov 24 14:09:32 nimrodel kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 17 Nov 24 14:09:38 nimrodel kernel: usb usb2: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.1[B] -> GSI 19 (level, low) -> IRQ 18 Nov 24 14:09:38 nimrodel kernel: usb usb3: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.2[C] -> GSI 16 (level, low) -> IRQ 16 Nov 24 14:09:38 nimrodel kernel: usb usb1: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:08 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:09 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0b. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0c. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0d activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0e activated. Nov 24 14:09:38 nimrodel kernel: hda: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdb: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdc: selected mode 0x42 Nov 24 14:09:38 nimrodel kernel: hdd: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep00: PM: resume from 0, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb-storage 1-1:1.0: PM: resume from 1, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep02: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep86: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: host0: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: Restarting tasks ... <6>usb 1-1: USB disconnect, address 3 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7514 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7515 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: REISERFS abort (device sda1): Journal write error in flush_commit_list Nov 24 14:09:38 nimrodel kernel: done. Nov 24 14:09:38 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 24 14:09:38 nimrodel kernel: usb 1-1: new high speed USB device using ehci_hcd and address 4 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device found, idVendor=04b4, idProduct=6830 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device strings: Mfr=56, Product=78, SerialNumber=100 Nov 24 14:09:38 nimrodel kernel: usb 1-1: Product: USB2.0 Storage Device Nov 24 14:09:38 nimrodel kernel: usb 1-1: Manufacturer: Cypress Semiconductor Nov 24 14:09:38 nimrodel kernel: usb 1-1: SerialNumber: DEF10000CE2DB1A Nov 24 14:09:38 nimrodel kernel: usb 1-1: configuration #1 chosen from 1 choice Nov 24 14:09:38 nimrodel kernel: scsi1 : SCSI emulation for USB Mass Storage devices Nov 24 14:09:38 nimrodel kernel: usb-storage: device found at 4 Nov 24 14:09:38 nimrodel kernel: usb-storage: waiting for device to settle before scanning Nov 24 14:09:38 nimrodel kernel: scsi 1:0:0:0: Direct-Access ST360020 A 0000 PQ: 0 ANSI: 0 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sdb:<6>input: Power Button (FF) as /class/input/input18 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 24 14:09:38 nimrodel kernel: input: Power Button (CM) as /class/input/input19 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 24 14:09:38 nimrodel kernel: input: Sleep Button (CM) as /class/input/input20 Nov 24 14:09:38 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] Nov 24 14:10:03 nimrodel kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 4 Nov 24 14:10:04 nimrodel kernel: sdb1 Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Nov 24 14:10:04 nimrodel kernel: usb-storage: device scan complete Nov 24 14:43:26 nimrodel kernel: scsi 0:0:0:0: rejecting I/O to dead device I suppose I could add my own hook to umount the device if I forget, but I propose that you could add a generic hook to umount usb devices on hybernate, or ensure that they resurrect on the correct device. -- 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 49

[Bug 357354] New: lenovo X60s jw collector bug
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=357354 Summary: lenovo X60s jw collector bug Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: jw(a)novell.com ReportedBy: jw(a)novell.com QAContact: qa(a)suse.de Depends on: 355128 Found By: --- This defect depends on all issues found with my X60s -- 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 99

[Bug 384579] New: zypper should be able to download only
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=384579 Summary: zypper should be able to download only Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: cgoncalves(a)opensuse.org QAContact: dmacvicar(a)novell.com Found By: --- Sometimes users don't want to download and install packages at the same time because they just want to download and them install later. There are several reasons: - running on battery; - not the appropriate time to get their system under heavy resource usage; - or simply because they want to download everything first and install afterwards. So my request is if it would be possible to add a --download-only feature into update, upgrade, and install zypper commands. -- 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 390526] New: yast2-gtk: During automatic installation, some dialog boxes have abort, others don't
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=390526 Summary: yast2-gtk: During automatic installation, some dialog boxes have abort, others don't Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: captain.magnus(a)opensuse.org QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=215337) --> (https://bugzilla.novell.com/attachment.cgi?id=215337) Now Featuring... An abort button First, why do we have these really small and ugly dialog boxes information the user about "Detecting this" and "Detecting that"? Wouldn't it be better to have an icon row below the two status bars in the main window which are grayed out to start with, and as it progresses with hardware detection, light them up (Same as in the beginning of the installation). Anyway... During hardware detection, one dialog box stands out as it contains an abort button, whilst none of the others have it. It'd be nice to get some consistency. See attached screenshots. -- 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