January 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 413904] New: Ricoh MMC card reader doesn't function
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=413904 Summary: Ricoh MMC card reader doesn't function Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jos.baudrez(a)telenet.be QAContact: qa(a)suse.de Found By: --- When an SD card gets inserted in the slot on my Thinkpad x61s, I do not get any response; fdisk -l doesn't see anything in there and the var/log/messages file says: sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci: SDHCI controller found at 0000:05:00.2 [1180:0822] (rev 21) ACPI: PCI Interrupt 0000:05:00.2[C] -> GSI 18 (level, low) -> IRQ 18 sdhc0:slot0: Will use DMA mode even though HW doesn't fully claim to support it. PCI: Setting latency timer of device 0000:05:00.2 to 64 mmc0: SDHCI at 0xf8301800 irq 18 DMA mmc0: new high speed SD card at address b368 mmcblk0: mmc0:b368 SD 1997312KiB mmcblk0:<3>mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 printk: 3 messages suppressed. Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 ldm_validate_partition_table(): Disk read failed. mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 24 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 unable to read partition table mmcblk0: error -84 transferring data end_request: I/O error, dev mmcblk0, sector 0 end_request: I/O error, dev mmcblk0, sector 8 end_request: I/O error, dev mmcblk0, sector 16 end_request: I/O error, dev mmcblk0, sector 24 I have been told this is a 'new' bug, so i start a new thread. If i can be of any further use pls. let me know! -- 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 466894] New: single-user boot with /boot on RAID-1 fails to find existing boot & some-not-all other devices
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=466894 User pgnet.trash(a)gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466894#c1 Summary: single-user boot with /boot on RAID-1 fails to find existing boot & some-not-all other devices Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pgnet.trash(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 I'm running uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux I've patched OS 11.1's "/lib/mkinitrd/scripts/setup-md.sh", per, "Bug 461673 - xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0" https://bugzilla.novell.com/show_bug.cgi?id=461673 my setup is RAID-1 based, disks sdc+sdd /boot on /dev/md0, fmt=ext3 swap on /dev/md1, fmt=swap /root on /dev/md2:VG(VG_Dom0):LV(LV_ROOT), fmt=ext3 /home/store on /dev/md3:VG(VG_DomU):LV(store), fmt=ext3 /home/work on /dev/md3:VG(VG_DomU):LV(work), fmt=ext3 disks sda+sdb 'other' on /dev/md4 'other' on /dev/md5 & boots OK, df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/VG_Dom0-LV_ROOT 13G 5.5G 6.6G 46% / udev 4.2G 213k 4.2G 1% /dev /dev/md0 152M 53M 91M 37% /boot none 68M 0 68M 0% /tmp /dev/mapper/VG_DomU-store 5.3G 4.5G 572M 89% /home/store /dev/mapper/VG_DomU-work 11G 451M 9.6G 5% /home/work with all RAID devs available (i'm curious/concerned about the "resync=PENDING .. tbd later ...), cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [linear] md5 : active (auto-read-only) raid1 sda2[0] sdb2[1] 347606300 blocks super 1.0 [2/2] [UU] resync=PENDING bitmap: 332/332 pages [1328KB], 512KB chunk md4 : active (auto-read-only) raid1 sda1[0] sdb1[1] 629145424 blocks super 1.0 [2/2] [UU] resync=PENDING bitmap: 293/300 pages [1172KB], 1024KB chunk md3 : active raid1 sdc4[0] sdd4[1] 230934236 blocks super 1.0 [2/2] [UU] bitmap: 0/441 pages [0KB], 256KB chunk md0 : active raid1 sdc1[0] sdd1[1] 152604 blocks super 1.0 [2/2] [UU] bitmap: 0/10 pages [0KB], 8KB chunk md1 : active raid1 sdc2[0] sdd2[1] 522100 blocks super 1.0 [2/2] [UU] bitmap: 0/8 pages [0KB], 32KB chunk md2 : active raid1 sdc3[0] sdd3[1] 12578820 blocks super 1.0 [2/2] [UU] bitmap: 5/192 pages [20KB], 32KB chunk If I reboot this setup to single user, title OS 11.1 SINGLE_USER root (hd0,0) kernel /vmlinuz single root=/dev/system/ROOT iommu=force irqpoll initrd /initrd @ shell prompt, ls /boot is completely empty. looks like /boot on /dev/md0 is not mounted at all. checking cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [linear] md1 : active (auto-read-only) raid1 sdc2[0] sdd2[1] 522100 blocks super 1.0 [2/2] [UU] bitmap: 0/8 pages [0KB], 32KB chunk md2 : active raid1 sdc3[0] sdd3[1] 12578820 blocks super 1.0 [2/2] [UU] bitmap: 7/192 pages [28KB], 32KB chunk md0, md3, md4 & md5 are missing. md4/5, i suspect, because the associated drives are hanging off of a PCI/SATA card ... but shouldn't md0 & md3 both be there & mounted? attempting to mount mount -a mount: special device /dev/md0 does not exist mount: special device /dev/VG_DomU/store does not exist mount: special device /dev/VG_DomU/work does not exist they're apparently not-mountable :-/ Reading @ possibly relevant, Bug 445490 - boot stops on mounting a software RAID - Invalid root filesystem https://bugzilla.novell.com/show_bug.cgi?id=445490#c19 it looked worth a try. applying the referenced patch to, /lib/mkinitrd/scripts/boot-md.sh and rebooting, unfortunately, makes no difference; md0/3/4/5 are still missing in single-user. 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 4

[Bug 467272] New: logwatch is missing directory /etc/logwatch/scripts/services
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=467272 Summary: logwatch is missing directory /etc/logwatch/scripts/services Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: asvetter(a)cip.physik.uni-wuerzburg.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-0.1 Firefox/3.0.5 The logwatch rpm does not create the directory /etc/logwatch/scripts/services on installation. The result is the following error message: wpyc001:/root # /etc/cron.daily/0logwatch ################### Logwatch 7.3.6 (05/19/07) #################### Processing Initiated: Mon Jan 19 10:23:10 2009 Date Range Processed: yesterday ( 2009-Jan-18 ) Period is day. Detail Level of Output: 0 Type of Output: unformatted Logfiles for Host: wpyc001 ################################################################## --------------------- Dmeventd Errors Begin ------------------------ No such file or directory at /usr/share/logwatch/scripts/services/dmeventd line 44. ---------------------- Dmeventd Errors End ------------------------- Workaround: mkdir /etc/logwatch/scripts/services Reproducible: Always Steps to Reproduce: 1. Install logwatch rpm 2. run /etc/cron.daily/0logwatch or wait for execution of the daily cronjob 3. notice error message 4. mkdir /etc/logwatch/scripts/services 5. run /etc/cron.daily/0logwatch again 6. no error 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.

1 7

[Bug 436688] New: zypper "Sort the list by repository priority" doesn' t uses numeric sort
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=436688 Summary: zypper "Sort the list by repository priority" doesn't uses numeric sort Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: cmorve69(a)yahoo.es QAContact: qa(a)suse.de Found By: Community User zypper "Sort the list by repository priority" doesn't uses numeric sort. See packman postion... $ LC_ALL=C zypper lr -P # | Alias | Name | Enabled | Refresh | Priority ---+----------------------+----------------------+---------+---------+--------- 5 | home_reddwarf | RedDwarf's Home | Yes | Yes | 1 6 | kde3 | KDE3 | Yes | Yes | 25 8 | kde4_factory_desktop | KDE4 Factory Desktop | Yes | Yes | 25 10 | kde_qt | Current Qt 4.x | Yes | Yes | 25 11 | mozilla | Mozilla | Yes | Yes | 25 13 | nvidia | NVIDIA | Yes | Yes | 25 14 | openoffice | OpenOffice.org | Yes | Yes | 25 21 | smart | Smart | Yes | Yes | 25 25 | wine | Wine | Yes | Yes | 25 15 | opensuse-dvd | openSUSE DVD | Yes | No | 50 18 | repo-debug | openSUSE Debug | No | No | 50 19 | repo-non-oss | openSUSE Non-Oss | Yes | No | 50 20 | repo-oss | openSUSE Oss | Yes | No | 50 22 | updates | Updates | Yes | Yes | 50 1 | education | Education | Yes | Yes | 75 2 | emulators | Emulators | Yes | Yes | 75 3 | games | Games | Yes | Yes | 75 7 | kde4_community | KDE4 Community | Yes | Yes | 75 9 | kde_backports | KDE Backports | Yes | Yes | 75 12 | network_utilities | Network Utilities | Yes | Yes | 75 16 | opensuse_tools | openSUSE tools | Yes | Yes | 75 24 | virtualbox | VirtualBox | Yes | Yes | 75 26 | yast_svn | YaST svn snapshots | Yes | Yes | 75 27 | zypp_svn | ZYPP SVN Builds | Yes | Yes | 75 17 | packman | Packman | Yes | Yes | 8 4 | home_mvyskocil | mvyskocil's Home | Yes | Yes | 93 23 | videolan | VideoLan | Yes | Yes | 99 -- 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 464727] New: yast product creator mixes up architectures
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=464727 Summary: yast product creator mixes up architectures Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bart(a)geesink.org QAContact: jsrain(a)novell.com Found By: --- When I try to make a installation CD with yast product creator it creates an unbootable CD. /boot/i386 is completely empty. I think the problem is related to architecture. When I choose the installation source, this message is displayed: source http://192.168.1.240/suse/11.1 does not support the current architecture (i386). Change the target architecture? Then a checkbox where you can only choose i586. This same problem also prevents making a kiwi image. There you get this message: Target architecure of the current configuration (i586) does not match the system configuration (i386). Kiwi cannot create images for different architectures. Attached my y2log. The image is used for testing this is named test_for_begreport (yes that was a typo, my English is not *that* bad ;)). Thanks! -- 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 13

[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

[Bug 457046] New: documentation for apparmor included twice and confusingly packaged ...
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=457046 Summary: documentation for apparmor included twice and confusingly packaged ... Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: felix(a)derklecks.de QAContact: ke(a)novell.com Found By: --- I was just looking for apparmor documentation and found two packages: # zypper se -s apparmor-admin_en-pdf Daten des Repositorys laden... Installierte Pakete lesen... S | Name | Typ | Version | Arch | Repository --+--------------------------------+-------+-----------+--------+----------- i | apparmor-admin_en-pdf | Paket | 10.3-8.86 | noarch | oss i | opensuse-apparmor-admin_en-pdf | Paket | 11.1-28.2 | noarch | oss # rpm -ql apparmor-admin_en-pdf opensuse-apparmor-admin_en-pdf /usr/share/doc/manual /usr/share/doc/manual/apparmor-admin_en-pdf /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/LICENSE.txt /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf The supposingly SLES documentation has the following pdf metadata: fm@macbook:~> pdfinfo /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf | head -n 3 Title: openSUSE Documentation Author: Unknown Creator: Unknown The openSUSE one has: fm@macbook:~> pdfinfo /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf | head -n 3 Title: Documentation Author: SUSE Creator: DocBook V1.74.0 So are really two packages needed? And at least the title of APPARMOR-admin_en.pdf is wrong ... -- 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 458891] New: Cannot set IPv6 default gateway
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458891 Summary: Cannot set IPv6 default gateway Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mstopka(a)opensuse.org QAContact: qa(a)suse.de Found By: --- IPv6 support in YaST is not so good yet, because YaST make ma able to set an IPv6 addresses for interfaces, but not make me able to set default IPv6 gateway. Currently I can set addresses like this: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:16:d4:61:ae:81 brd ff:ff:ff:ff:ff:ff inet 82.209.54.76/29 brd 82.209.54.79 scope global eth0 inet6 2001:15c0:668e::2/48 scope global valid_lft forever preferred_lft forever inet6 2002:52d1:364a::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::216:d4ff:fe61:ae81/64 scope link valid_lft forever preferred_lft forever but I have two choices I can set default IPv4 gateway like default via 82.209.54.73 dev eth0 or IPv6 gateway, not both so dual stack IPv4 and IPv6 is not possible, at least not easily possible only using YaST. I can set as default gateway 2001:15c0:668e::1 but then I have IPv6 up and running, but not IPv4 for global communication, only for 82.209.54.72/29. I think YaST should detect if there is any IPv6 address on any interface (?except loopback) and if so, YaST should show one more field for default gateway marked like "Default IPv6 gateway". I think something like this would be fine also for IPv4 networking... I mean if there is no IPv4 address on any interface (?except loopback) YaST should not show me an field marked as "Default gateway"... Or to be more precise I think "Default gateway" field should be renamed as "IPv4 default gateway" and this one filed should not be seeing if there is no IPv4 address on any interface. -- 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