April 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 456004] New: mount encrypted /home before user config
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=456004 Summary: mount encrypted /home before user config Product: openSUSE 11.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development When installing with an encrypted /home partition I am informed during user creation that the /home partition is not mounted (see screenshot). What is missing here is the possibility to enter the password for the partition, mount the partiton and continue with the user configuration. -- 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 19

[Bug 490895] New: libzypp has Unused dependencies
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490895 Summary: libzypp has Unused dependencies Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Development ldd -u -r libzypp.so.602.0.2 Unused direct dependencies: /usr/lib/libssl.so.0.9.8 /usr/lib/libboost_signals.so.1.38.0 Less unused dependencies, less likely to get broken on upgrades between different products or factory snapshots, try to use -Wl --as-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 1

[Bug 474186] New: Atheros wireless does not work
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=474186 User hub(a)figuiere.net added comment https://bugzilla.novell.com/show_bug.cgi?id=474186#c1 Summary: Atheros wireless does not work Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hub(a)figuiere.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 The Atheros wireless does not work. It goes up, associate to the access point was NetworkManager (WPA encryption) but ping to the gateway is very unreliable. Device is 13:00.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01) (ThinkPad Z60t) The driver is ath5k as provided by the kernel: Linux grinch 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux dmesg shows: ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: authenticate with AP 00:0f:66:dc:fa:c6 wlan0: authenticated wlan0: associate with AP 00:0f:66:dc:fa:c6 wlan0: RX AssocResp from 00:0f:66:dc:fa:c6 (capab=0x411 status=0 aid=4) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready martian source 255.255.255.255 from 172.18.2.1, on dev wlan0 ll header: ff:ff:ff:ff:ff:ff:00:1c:10:49:a7:91:08:00 wlan0: no IPv6 routers present martian source 255.255.255.255 from 172.18.2.1, on dev wlan0 ll header: ff:ff:ff:ff:ff:ff:00:1c:10:49:a7:91:08:00 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=172.18.2.1 DST=172.18.2.112 LEN=356 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=1900 DPT=52479 LEN=336 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=172.18.2.1 DST=172.18.2.112 LEN=356 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=1900 DPT=47910 LEN=336 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=172.18.2.1 DST=172.18.2.112 LEN=358 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=1900 DPT=47910 LEN=338 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=195.238.1.7 DST=172.18.2.112 LEN=52 TOS=0x00 PREC=0x00 TTL=48 ID=21474 DF PROTO=TCP SPT=80 DPT=51383 WINDOW=6432 RES=0x00 ACK FIN URGP=0 OPT (0101080A7717A6ED0062FA8F) SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=66.163.181.167 DST=172.18.2.112 LEN=1154 TOS=0x00 PREC=0x00 TTL=47 ID=46406 DF PROTO=TCP SPT=5050 DPT=47244 WINDOW=33120 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A21FDA8670062AE9F) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=208.93.0.128 LEN=177 TOS=0x00 PREC=0x00 TTL=64 ID=59718 DF PROTO=TCP SPT=58266 DPT=5222 WINDOW=108 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=34484 DF PROTO=TCP SPT=45393 DPT=443 WINDOW=92 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=50811 DF PROTO=TCP SPT=45394 DPT=443 WINDOW=92 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=43496 DF PROTO=TCP SPT=45395 DPT=443 WINDOW=92 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=38704 DF PROTO=TCP SPT=45396 DPT=443 WINDOW=92 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=29496 DF PROTO=TCP SPT=45397 DPT=443 WINDOW=92 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=69.63.176.174 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=10134 DF PROTO=TCP SPT=41015 DPT=80 WINDOW=108 RES=0x00 ACK FIN URGP=0 OPT (0101080A0064D83C9087CA39) SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:15:e9:b5:44:9b:08:00 SRC=172.18.2.32 DST=172.18.2.112 LEN=124 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=53 DPT=43970 LEN=104 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=206.248.154.170 DST=172.18.2.112 LEN=147 TOS=0x00 PREC=0x00 TTL=61 ID=41198 PROTO=UDP SPT=53 DPT=57238 LEN=127 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=206.248.154.170 DST=172.18.2.112 LEN=151 TOS=0x00 PREC=0x00 TTL=61 ID=41204 PROTO=UDP SPT=53 DPT=38572 LEN=131 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=206.248.154.170 DST=172.18.2.112 LEN=153 TOS=0x00 PREC=0x00 TTL=61 ID=41474 PROTO=UDP SPT=53 DPT=50646 LEN=133 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:15:e9:b5:44:9b:08:00 SRC=172.18.2.32 DST=172.18.2.112 LEN=122 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=53 DPT=57857 LEN=102 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=69.63.176.174 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=10135 DF PROTO=TCP SPT=41015 DPT=80 WINDOW=108 RES=0x00 ACK FIN URGP=0 OPT (0101080A00650D9C9087CA39) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=69.63.176.174 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=10136 DF PROTO=TCP SPT=41015 DPT=80 WINDOW=108 RES=0x00 ACK FIN URGP=0 OPT (0101080A0065785C9087CA39) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=54019 DF PROTO=TCP SPT=37540 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=46428 DF PROTO=TCP SPT=37541 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=72.2.112.185 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=15713 DF PROTO=TCP SPT=49065 DPT=80 WINDOW=992 RES=0x00 ACK FIN URGP=0 OPT (0101080A0066CF4F83FBA389) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=54020 DF PROTO=TCP SPT=37540 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=72.14.205.17 DST=172.18.2.112 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=9461 PROTO=TCP SPT=443 DPT=51738 WINDOW=150 RES=0x00 ACK FIN URGP=0 OPT (0101080AA688DBC50066EC7F) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=72.14.205.17 LEN=79 TOS=0x00 PREC=0x00 TTL=64 ID=54686 DF PROTO=TCP SPT=51738 DPT=443 WINDOW=225 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00678B84A687ED19) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18597 DF PROTO=TCP SPT=40308 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=130.57.4.16 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=61535 DF PROTO=TCP SPT=443 DPT=40308 WINDOW=10283 RES=0x00 ACK PSH FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=130.57.4.16 DST=172.18.2.112 LEN=63 TOS=0x00 PREC=0x00 TTL=116 ID=9320 DF PROTO=TCP SPT=443 DPT=40308 WINDOW=10283 RES=0x00 ACK PSH FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=130.57.4.16 DST=172.18.2.112 LEN=63 TOS=0x00 PREC=0x00 TTL=116 ID=61812 DF PROTO=TCP SPT=443 DPT=40308 WINDOW=10283 RES=0x00 ACK PSH FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=130.57.4.16 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=12464 DF PROTO=TCP SPT=443 DPT=37539 WINDOW=0 RES=0x00 ACK RST URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=69.63.180.12 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=56047 DF PROTO=TCP SPT=56293 DPT=80 WINDOW=117 RES=0x00 ACK FIN URGP=0 OPT (0101080A0067EFBF5E41D851) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18598 DF PROTO=TCP SPT=40308 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=72.14.205.189 LEN=79 TOS=0x00 PREC=0x00 TTL=64 ID=27196 DF PROTO=TCP SPT=46224 DPT=443 WINDOW=108 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00682CCAA6947F17) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=69.63.180.12 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=56048 DF PROTO=TCP SPT=56293 DPT=80 WINDOW=117 RES=0x00 ACK FIN URGP=0 OPT (0101080A006841DF5E41D851) SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=130.57.4.16 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18599 DF PROTO=TCP SPT=40308 DPT=443 WINDOW=178 RES=0x00 ACK PSH FIN URGP=0 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=66.135.209.243 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=21959 DF PROTO=TCP SPT=36133 DPT=80 WINDOW=10720 RES=0x00 ACK FIN URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=66.135.209.243 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=20752 PROTO=TCP SPT=80 DPT=36133 WINDOW=8201 RES=0x00 RST URGP=0 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:15:e9:b5:44:9b:08:00 SRC=172.18.2.32 DST=172.18.2.112 LEN=120 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=53 DPT=54857 LEN=100 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:15:e9:b5:44:9b:08:00 SRC=172.18.2.32 DST=172.18.2.112 LEN=120 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=53 DPT=47313 LEN=100 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=208.93.0.128 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=16419 DF PROTO=TCP SPT=80 DPT=41853 WINDOW=0 RES=0x00 ACK RST URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=208.93.0.128 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=34293 DF PROTO=TCP SPT=80 DPT=41853 WINDOW=0 RES=0x00 ACK RST URGP=0 SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=208.93.0.128 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=40235 DF PROTO=TCP SPT=80 DPT=41853 WINDOW=0 RES=0x00 ACK RST URGP=0 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=206.248.154.22 DST=172.18.2.112 LEN=149 TOS=0x00 PREC=0x00 TTL=61 ID=20615 PROTO=UDP SPT=53 DPT=54975 LEN=129 SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=206.248.154.22 DST=172.18.2.112 LEN=149 TOS=0x00 PREC=0x00 TTL=61 ID=21064 PROTO=UDP SPT=53 DPT=59539 LEN=129 SFW2-OUT-ERROR IN= OUT=wlan0 SRC=172.18.2.112 DST=72.14.205.189 LEN=79 TOS=0x00 PREC=0x00 TTL=64 ID=49960 DF PROTO=TCP SPT=34848 DPT=443 WINDOW=108 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0069B0E3A68CE1F3) SFW2-INext-DROP-DEFLT-INV IN=wlan0 OUT= MAC=00:14:a4:61:ac:29:00:1c:10:49:a7:91:08:00 SRC=72.14.205.189 DST=172.18.2.112 LEN=40 TOS=0x00 PREC=0x00 TTL=57 ID=18457 PROTO=TCP SPT=443 DPT=34848 WINDOW=0 RES=0x00 RST URGP=0 The network controller used to work with madwifi. 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 27

[Bug 466484] New: on shutdown the home-partition does not clearly unmount.
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=466484 Summary: on shutdown the home-partition does not clearly unmount. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: svenzielke(a)gmx.de QAContact: qa(a)suse.de Found By: --- Sorry for my English! Often some applications accesses the /home-partition (if it exists) and so unmounting on shutdown fails. Solutions seems to be moving the follwing block echo "Sending all processes the TERM signal..." killall5 -15 echo -e "$rc_done_up" # wait between last SIGTERM and the next SIGKILL rc_wait /sbin/blogd /sbin/splash echo "Sending all processes the KILL signal..." killall5 -9 echo -e "$rc_done_up" between test -s /etc/init.d/.depend.halt || RUN_PARALLEL="no" type -p startpar &> /dev/null || RUN_PARALLEL="no" startpar -v &> /dev/null || RUN_PARALLEL="no" and # # set back system boot configuration # if test "$RUN_PARALLEL" = "yes" ; then startopt="-p4 -t 30 -T 3" eval $(startpar $startopt -M halt) unset failed_service skipped_service -- 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 120

[Bug 445878] New: Separate better step done with actual job remaining during setup
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=445878 Summary: Separate better step done with actual job remaining during setup Product: openSUSE 11.1 Version: Beta 5 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: romain.pelissier(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- I have noticed that during the setup at the end of the installation there are a smal part about the configuration of the user printer. In my case, I do not have a printer so the page displayed juste says Printer Setup or something like that with some text below like 'Finish printer configuration' The issue that that the progress bar at the botom still show that some stuff are being downloaded and installed. Could a clean page be added after the printer setup to not confused the user so download and installed all parts needed at the end of the hardware setup? No bug issue but could improve the setup experience. -- 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 490673] New: power management module not found
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=490673 Summary: power management module not found Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: jsrain(a)novell.com Found By: --- After selecting power management module via software management and clicking on the icon in YaST control center a pop up appeared that the module couldn't be found. ("No such client module power management"). If you need any additional logs to y2log please let me know. Cu, Martin -- 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 389386] New: vnc installation crashes
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=389386 User mmrazik(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=389386#c358865 Summary: vnc installation crashes Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: sndirsch(a)novell.com ReportedBy: mmrazik(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=214455) --> (https://bugzilla.novell.com/attachment.cgi?id=214455) y2logs This might be a duplicate of bug #358865 but I'm observing this on a i386 machine (it is a x86_64 host with i386 installation). VNC installation crashes right after connection of the VNC client. The VNC client is asked for a password and right after the password is entered the installation crashes with "An error occurred during the installation" message. y2logs attached. Unfortunately I don't know how to debug this better so if you need more logs please let me know. I think this one may be easy to reproduce. Attached are 2 screenshots from the text console (from KVM). This host doesn't have serial port thus I'm unable to attach the whole output. -- 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 69

[Bug 479195] New: Install-time VNC server crashes on connection
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=479195 Summary: Install-time VNC server crashes on connection Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jra(a)baylink.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 When attempting to use the VNC installation to install the OS remotely on a bare machine, the VNC server crashes when a VNC viewer client attempts to connect to it, after the VNC password is given and accepted. I've tried this with the current UltraVNC viewer, 1.0.5, as well as the TightVNC viewer 1.3.10; I also tried switching the Ultra viewer from ZRLE to Tight mode. The crash happens just after connection, after (or as) the first desktop screen is being painted on the viewer window -- sometimes I can see the entire screen, and then a memory-scribble stride pattern is painted across it before the disconnect ("error WriteExact"); sometimes it crashes in the middle of painting the screen. This has happened on 2 separate servers; one an ASUS P5WDG with an RTL8169 card; one a SuperMicro C2SBC-Q with whatever the stock NIC is on that. I gather another bug on this was merged into a 10.3 bug about after-install VNC problems; I would recommend against merging this bug with *anything* -- if there's another bug on this problem, BZ declines to provide it to me in a search. I'm going to install a *LOT* of 11.0 server this year; this is a P2 bug for me. Reproducible: Always Steps to Reproduce: 1. Start an 11.0 install with "VNC=1" on the command line 2. Specify a static IP, net mask, no gateway, and hit ESC at DNS 3. Try to connect and observe crash 4. Blather, wince, repeat Actual Results: The VNC server crashes, leaving a red error dialog on the system console screen saying "A failure occurred during the installation" (or something within 5% of that) Expected Results: I should be able to perform a graphical install through the VNC connection -- 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 465930] New: Very slow upload speeds with iwl3945 driver
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=465930 Summary: Very slow upload speeds with iwl3945 driver Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: victorrz(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 Upload speeds are around 50-80KB/s with downloads speeds approx 1MB/s on the iwl3945 wireless connection to a 54G router running WPA2. Windows XP upload and download rates are equal at around 1MB/s. This behavior seems similar to the bug report in this thread: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288948 dmesg ouptput: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks iwl3945: Copyright(c) 2003-2008 Intel Corporation iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 0000:03:00.0: setting latency timer to 64 iwl3945: Detected Intel Wireless WiFi Link 3945ABG iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels phy0: Selected rate control algorithm 'iwl-3945-rs' iwl3945 0000:03:00.0: PCI INT A disabled iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006) firmware: requesting iwlwifi-3945-1.ucode Registered led device: iwl-phy0:radio Registered led device: iwl-phy0:assoc Registered led device: iwl-phy0:RX Registered led device: iwl-phy0:TX Reproducible: Always Steps to Reproduce: 1.Use the iwl3945 wireless connection to copy a large file using ssh or smb. 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 20

[Bug 370872] New: "pccardctl eject" hangs in state D
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=370872 Summary: "pccardctl eject" hangs in state D Product: openSUSE 11.0 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: seife(a)novell.com QAContact: qa(a)suse.de CC: fseidel(a)novell.com Found By: Development During suspend, one thing we do is eject PCMCIA card with "pccardctl eject". I quite frequently see that command hanging in state D, which makes suspend fail. Attempting to shut down the machine cleanly lead to a hang when the sound modules are unloaded, a clean shutdown does only happen if i do a sysrq-e to kill the hanging processes and make init proceed. I have seen this with various 3G/UMTS CardBus cards, both USB-serial based and nozomi based, so i believe this to be a generic PCMCIA issue. Will attach sysrq-T -- 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 108