October 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 440530] New: button labeling in dhcp server modules
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=440530 Summary: button labeling in dhcp server modules Product: openSUSE 11.1 Version: Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement 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: --- When opening the module the user is presented with an overview. On the other hand wizard buttons are used for main navigation. Please change the buttons according to the YaST style guide (http://en.opensuse.org/YaST/Style_Guide#Single_Configuration.2FOverview.2FE…) from "Abort", "Back", "Finish" into "Cancel" / "OK" and do not show/drop the "Back " button. Please consider using the button box widget to maximize consistency with whichever desktop the user has chosen. -- 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 335172] New: yast2-product-creator: useless files
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=335172 Summary: yast2-product-creator: useless files Product: openSUSE 10.3 Version: Final Platform: PowerPC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pczanik(a)genesi-usa.com QAContact: jsrain(a)novell.com Found By: --- /boot/i386 and /boot/x86_64 have no use on PPC and occupy a lot of space (over two hundred megabytes, or one third of a CD). /boot/ppc should be enough. Tested on PPC using openSUSE 10.3 final FTP version. -- 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 421995] New: Product Creator errors
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=421995 Summary: Product Creator errors Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: deanjo(a)sasktel.net QAContact: jsrain(a)novell.com Found By: --- OK when trying to make an image using product creator it gives this error when a retail version of openSUSE 11.0 is used when copying the packages. "File './boot/x86_64/root.fonts' not found on medium 'dvd:///'" Also if a ftp mirror is enabled it gripes about not being able to find the necessary boot files despite the iso being selected as the base. As well on a x64 based system it wants to install a 32-bit pae kernel as well when it trys to create a 64-bit image. -- 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 367781] New: yast2-product-creator: too few packages
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=367781 Summary: yast2-product-creator: too few packages Product: openSUSE 11.0 Version: Alpha 2plus Platform: PowerPC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pczanik(a)genesi-usa.com QAContact: jsrain(a)novell.com Found By: --- Tested on today's factory (2008-03-06): yast2-product-creator puts only very few packages on to the created CD / directory tree. I wanted to create an XFCE CD, but only these packages are in suse/ppc: factory:~/efika_xfce/efika_xfce/suse/ppc # l total 48032 drwxr-xr-x 2 root root 4096 2008-03-06 16:00 ./ drwxr-xr-x 4 root root 4096 2008-03-06 16:00 ../ -rw-r--r-- 1 1002 192 424872 2008-03-03 20:07 autofs-5.0.3-16.ppc.rpm -rw-r--r-- 1 1002 192 392463 2008-02-29 22:50 bash-3.2-89.ppc.rpm -rw-r--r-- 1 1002 192 3734899 2008-02-26 01:10 binutils-2.18.50.20080225-2.ppc.rpm -rw-r--r-- 1 1002 192 14445379 2008-03-01 01:55 kernel-default-2.6.24.1-6.ppc.rpm -rw-r--r-- 1 1002 192 14065430 2008-03-01 01:59 kernel-ppc64-2.6.24.1-6.ppc.rpm -rw-r--r-- 1 1002 192 14250771 2008-03-01 01:30 kernel-vanilla-2.6.24.1-6.ppc.rpm -rw-r--r-- 1 1002 192 149867 2008-02-28 17:09 module-init-tools-3.2.99.pre11-50.ppc.rpm -rw-r--r-- 1 1002 192 1313943 2008-02-26 01:47 perl-base-5.10.0-15.ppc.rpm -rw-r--r-- 1 1002 192 118253 2008-02-26 03:07 perl-Bootloader-0.4.46-8.ppc.rpm -rw-r--r-- 1 1002 192 177481 2008-02-26 03:07 sed-4.1.5-87.ppc.rpm -- 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 420979] New: Unable to connect to the internet with CDMA modem using NetworkManager
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=420979 Summary: Unable to connect to the internet with CDMA modem using NetworkManager Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jaromir.hamala(a)gmail.com QAContact: qa(a)suse.de Found By: --- Hello, I'm using gnome network manager applet, which is supposed to be able to connect to the internet using CDMA modem. I have defined the connection in Network Connection - Mobile Broadband tab and added it as CDMA connection. Login and password are filled it, but when trying to use the connection, I see following in /var/log/messages: Aug 25 14:05:02 jester pppd[17612]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. Aug 25 14:05:02 jester pppd[17612]: pppd 2.4.4 started by root, uid 0 Aug 25 14:05:02 jester pppd[17612]: Using interface ppp0 Aug 25 14:05:02 jester pppd[17612]: Connect: ppp0 <--> /dev/ttyUSB0 Aug 25 14:05:02 jester pppd[17612]: Unable to obtain CHAP password for jester on from plugin Aug 25 14:05:02 jester pppd[17612]: No CHAP secret found for authenticating us to Aug 25 14:05:03 jester pppd[17612]: CHAP authentication failed Aug 25 14:05:03 jester pppd[17612]: CHAP authentication failed Aug 25 14:05:03 jester pppd[17612]: Connection terminated. Aug 25 14:05:04 jester pppd[17612]: Exit. So seems me like network manager doesn't push the credentials to the modem. When dialing with kinternet, logs looks like this: Aug 25 14:06:14 jester pppd[18728]: Plugin passwordfd.so loaded. Aug 25 14:06:14 jester pppd[18728]: pppd 2.4.4 started by root, uid 0 Aug 25 14:06:17 jester pppd[18728]: Serial connection established. Aug 25 14:06:17 jester kernel: ppp0 renamed to modem0 Aug 25 14:06:17 jester pppd[18728]: Renamed interface ppp0 to modem0 Aug 25 14:06:17 jester pppd[18728]: Using interface modem0 Aug 25 14:06:17 jester pppd[18728]: Connect: modem0 <--> /dev/ttyUSB0 Aug 25 14:06:17 jester pulseaudio[4623]: sap.c: sendmsg() failed: Invalid argument Aug 25 14:06:20 jester pppd[18728]: CHAP authentication succeeded Aug 25 14:06:20 jester pppd[18728]: CHAP authentication succeeded Aug 25 14:06:20 jester pppd[18728]: replacing old default route to wlan0 [172.24.2.1] Aug 25 14:06:20 jester pppd[18728]: local IP address 10.166.43.95 Aug 25 14:06:20 jester pppd[18728]: remote IP address 10.164.3.42 Aug 25 14:06:20 jester pppd[18728]: primary DNS address 160.218.10.200 Aug 25 14:06:20 jester pppd[18728]: secondary DNS address 160.218.43.200 So kinternet is working. this is from /var/log/NetworkManager when trying to connect with NM: Aug 25 14:16:51 jester NetworkManager: <info> Activation (ttyUSB0) starting connection 'CDMA connection 1' Aug 25 14:16:51 jester NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4 Aug 25 14:16:51 jester NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Aug 25 14:16:51 jester NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Aug 25 14:16:51 jester NetworkManager: <debug> [1219666611.911538] nm_serial_device_open(): (ttyUSB0) opening device... Aug 25 14:16:51 jester NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Aug 25 14:16:53 jester NetworkManager: <info> Connected, Woo! Aug 25 14:16:53 jester NetworkManager: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Aug 25 14:16:53 jester NetworkManager: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Aug 25 14:16:53 jester NetworkManager: <info> (ttyUSB0): device state change: 4 -> 5 Aug 25 14:16:53 jester NetworkManager: <info> Starting pppd connection Aug 25 14:16:53 jester NetworkManager: <debug> [1219666613.910926] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock ttyUSB0 refuse-eap refuse-pap refuse-mschap refuse-mschap-v2 usepeerdns plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so Aug 25 14:16:53 jester NetworkManager: <debug> [1219666613.912289] nm_ppp_manager_start(): ppp started with pid 29083 Aug 25 14:16:53 jester NetworkManager: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Aug 25 14:16:54 jester NetworkManager: <WARN> impl_ppp_manager_need_secrets(): Cleared secrets, but setting didn't need any secrets. Aug 25 14:16:54 jester NetworkManager: <info> (ttyUSB0): device state change: 5 -> 9 Aug 25 14:16:54 jester NetworkManager: <debug> [1219666614.421342] nm_serial_device_close(): Closing device 'ttyUSB0' Aug 25 14:16:54 jester NetworkManager: <info> Marking connection 'CDMA connection 1' invalid. Aug 25 14:16:54 jester NetworkManager: <info> Activation (ttyUSB0) failed. Aug 25 14:16:54 jester NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3 Aug 25 14:16:54 jester NetworkManager: <info> (ttyUSB0): deactivating device. Thank you very any help! -- 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 369263] New: first-time login / extraordinary k/b problems ...
by bugzilla_noreply＠novell.com 11 Mar '09

11 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=369263 Summary: first-time login / extraordinary k/b problems ... Product: openSUSE 11.0 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mmeeks(a)novell.com QAContact: qa(a)suse.de CC: rodrigo(a)novell.com Found By: --- as I log-in automatically on boot, my caps-swap-with-ctrl setting appears not to have any effect. Worse - after a few attempts to switch screen with caps-Alt-arrow, ctrl-alt-arrow (literal keys) - I apparently get some seemingly stuck modifier key that turns all the text I type into gibberish ;-) By gibberish I mean amazing foreign language characters. -- 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 84

[Bug 412527] New: dhcp function of knetworkmanager fails
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=412527 User rens.groenewegen(a)xs4all.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=412527#c1 Summary: dhcp function of knetworkmanager fails Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rens.groenewegen(a)xs4all.nl QAContact: qa(a)suse.de Found By: Customer dhcp configuration over wireless fails. the first time after install, it works. after that, not anymore. on wired networks there are no problems. if wlan0 IP setup is configured manually, (ip, gateway, nameserver etcetera) IP functions as it should. /var/log/NetworkManager shows messages that dhcp operation timed out. Linux klingon64 2.6.25.11-0.1-default #1 SMP 2008-07-13 20:48:28 +0200 x86_64 x86_64 x86_64 GNU/Linux NetworkManager-kde-0.7r821737-0.1 NetworkManager-0.7.0.r3685-7.1 bug noticed on various locations (I travel....), forced me to fall back on 10.3 install. -- 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 37

[Bug 355402] New: SuSEconfig.gtk2 kills processes
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=355402 Summary: SuSEconfig.gtk2 kills processes Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: james(a)usr-local-bin.org QAContact: qa(a)suse.de Found By: Beta-Customer See $SUMMARY - this means that everytime SuSEconfig as a whole is run or the gtk2 module is run stand-alone (such as at an update) processes (such as gecko i.e. FireFox) are killed. The culprit *could* be /usr/bin/gtk-update-icon-cache - will try to be sure the next time it happens. -- 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 422918] New: No traffic when connecting to Novell VPN on ppc
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=422918 Summary: No traffic when connecting to Novell VPN on ppc Product: openSUSE 11.1 Version: Factory Platform: Macintosh OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lchiquitto(a)novell.com QAContact: qa(a)suse.de Found By: Beta-Customer When connecting to Novell VPN using OpenSUSE (Factory and 11.0) on PPC I am unable to establish connections to any host inside the VPN. While I see ESP packets going through the network interface, it seems that no answer comes back. I'm discarding network setup/topology problems because using a x86/x86_64 machine works fine. More information and output from VPN troubleshooting script to follow. -- 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 370656] New: Only clone mode available when using 2x DVI-D (radeonhd)
by bugzilla_noreply＠novell.com 10 Mar '09

10 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=370656 Summary: Only clone mode available when using 2x DVI-D (radeonhd) Product: openSUSE 11.0 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: mhopf(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Date: Thu, 13 Mar 2008 18:55:44 +0100 From: Matthias Hopf <mhopf(a)suse.de> To: xorg(a)lists.freedesktop.org Subject: RandR: multi-referenced monitor sections & problems with them I just stumbled over some strange behavior, and it definitely changed past Xserver 1.4.0 (don't know the exact version yet, bisecting this would be probably worth it). A snippet of the config I'm testing is Section "Monitor" Identifier "M1" EndSection Section "Monitor" Identifier "M2" Option "Right-Of" "M1" EndSection Section "Device" Identifier "D" Driver "radeonhd" Option "monitor-DVI-I_1/digital" "M1" Option "monitor-DVI-I_2/digital" "M2" EndSection Section "Screen" [...] Identifier "S" Device "D" Monitor "M1" EndSection [...] So basically a static multi-monitor setup for RandR 1.2, with one of the monitors additionally referenced in the Screen section. This monitor reference shouldn't be used at all, because the driver sets use_screen_monitor to FALSE for all outputs. This used to work - however, beginning with 1.4.90 the multi-monitor setup fails if and only if I use the two digital DVI outputs on this card, with DVI and VGA it works fine, with DVI/d and DVI/a it also works fine. If I remove the reference to the M1 monitor in the Screen section it works fine. If I add another monitor and reference it in the Screen section instead it works fine. It's probably difficult to reproduce this with another driver, but this shouldn't be a driver issue. Does anybody have a clue WTF is going on here, is this considered standard behavior or rather a bug? If it's standard, why is its behavior depending on the outputs (and not on the monitors)? Thanks Matthias -- 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 31