August 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 293026] New: syntax errors in /etc/pam_pkcs11/pam_pkcs11.conf
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=293026 Summary: syntax errors in /etc/pam_pkcs11/pam_pkcs11.conf Product: openSUSE 10.3 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: sbrabec(a)novell.com ReportedBy: jsuchome(a)novell.com QAContact: qa(a)suse.de Found By: --- /etc/pam_pkcs11/pam_pkcs11.conf will probably need to be parsed by YaST (feature 302132). However, I'm not sure about its syntax: it looks like each line must end with semicolon, but in the default configuration file present in the package some lines don't: mapper generic { debug = true; module = /usr/lib/pam_pkcs11/generic_mapper.so; # ignore letter case on match/compare ignorecase = false; # Use one of "cn" , "subject" , "kpn" , "email" , "upn" or "uid" cert_item = cn; # Define mapfile if needed, else select "none" mapfile = file:///etc/pam_pkcs11/generic_mapping # Decide if use getpwent() to map login use_getpwent = false; } Either it is an error, or my assumption about the required semicolon is incorrect (in which case i must ask how should I write modified lines). -- 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 294613] New: knetworkmanager doesn' t automatically reconnect WPA2 WLAN when the connection is lost
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=294613 Summary: knetworkmanager doesn't automatically reconnect WPA2 WLAN when the connection is lost Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lyehust(a)gmail.com QAContact: qa(a)suse.de Found By: --- I installed opensuse 10.2 (final) in my laptop (T60). The network card is the Thinkpad a/g/b card and uses madwifi driver. I often use the laptop in an university library, the wireless network uses PEAP (WPA2). I use knetworkmanager (ver 0.1) to connect the WLAN by choosing "WPA enterprise" in "Encryption" and choosing "WPA2", and it succeeds. However, when the connection is lost, knetworkmanager can't reconnect the WLAN. Thus, I have to choose "connect to other wireless network" option in the knetworkmanager and input all necessary items again. Then, I get the connection again. I have a wireless router in my home and set up the WLAN using WPA. The knetworkmanager can connect the WLAN automatically when the laptop boots. Therefore, I thought that the knetworkmanager can't reconnect the WLAN in the library maybe because theknetworkmanager didn't save the user name and password in the kwallet. The following is the log. -------------------- Success: Jul 25 15:28:12 T60 NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / UN-Wireless-WPA2 Jul 25 15:28:12 T60 NetworkManager: <info> Deactivating device ath0. Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0): cancelling... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) cancellation handler scheduled... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0): waiting for device to cancel activation. Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) cancellation handled. Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0): cancelled. Jul 25 15:28:12 T60 NetworkManager: <info> Device ath0 activation scheduled... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) started... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, and a key exists. No new key needed. Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'INTERFACE_ADD ath0 madwifi /var/run/wpa_supplicant ' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was '0' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 55492d576972656c6573732d57504132' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA2' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-EAP' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 eap PEAP' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 identity "user"' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 password <password>' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Jul 25 15:28:12 T60 NetworkManager: <info> SUP: response was 'OK' Jul 25 15:28:12 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:28:14 T60 NetworkManager: <info> Old device 'ath0' activating, won't change. Jul 25 15:28:15 T60 NetworkManager: <info> Activation (ath0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'UI-Wireless-WPA2'. Jul 25 15:28:15 T60 NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) scheduled. Jul 25 15:28:15 T60 NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) started... Jul 25 15:28:16 T60 NetworkManager: <info> Activation (ath0) Beginning DHCP transaction. Jul 25 15:28:16 T60 NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) complete. Jul 25 15:28:16 T60 NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface ath0 Jul 25 15:28:16 T60 NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface ath0 Jul 25 15:28:25 T60 NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface ath0 Jul 25 15:28:25 T60 NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) scheduled... Jul 25 15:28:25 T60 NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) started... Jul 25 15:28:25 T60 NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon: Jul 25 15:28:25 T60 NetworkManager: <info> address 128.255.*.* Jul 25 15:28:25 T60 NetworkManager: <info> netmask 255.255.254.0 Jul 25 15:28:25 T60 NetworkManager: <info> broadcast 255.255.255.255 Jul 25 15:28:25 T60 NetworkManager: <info> gateway 128.255.*.* Jul 25 15:28:25 T60 NetworkManager: <info> nameserver 128.255.*.* Jul 25 15:28:25 T60 NetworkManager: <info> nameserver 128.255.*.* Jul 25 15:28:25 T60 NetworkManager: <info> nameserver 128.255.*.* Jul 25 15:28:25 T60 NetworkManager: <info> hostname 'T60' Jul 25 15:28:25 T60 NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) scheduled... Jul 25 15:28:25 T60 NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) complete. Jul 25 15:28:25 T60 NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) started... Jul 25 15:28:26 T60 NetworkManager: <info> Clearing nscd hosts cache. Jul 25 15:28:26 T60 NetworkManager: <info> Restarting mdnsd (pid=3170). Jul 25 15:28:26 T60 NetworkManager: <info> Activation (ath0) Finish handler scheduled. Jul 25 15:28:26 T60 NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) complete. Jul 25 15:28:26 T60 NetworkManager: <info> Activation (ath0) successful, device activated. -------------------- Failure: Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, but NO valid key exists. New key needed. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'UN-Wireless-WPA2'. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key for network 'UN-Wireless-WPA2' received. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, but NO valid key exists. New key needed. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'UN-Wireless-WPA2'. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key for network 'UN-Wireless-WPA2' received. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, but NO valid key exists. New key needed. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'UN-Wireless-WPA2'. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key for network 'UN-Wireless-WPA2' received. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, but NO valid key exists. New key needed. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'UN-Wireless-WPA2'. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key for network 'UN-Wireless-WPA2' received. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0/wireless): access point 'UN-Wireless-WPA2' is encrypted, but NO valid key exists. New key needed. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'UN-Wireless-WPA2'. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 25 15:27:28 T60 NetworkManager: <info> Activation (ath0) New wireless user key for network 'UN-Wireless-WPA2' received. -- 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 295657] New: audacity - Hungarian translation update
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295657 Summary: audacity - Hungarian translation update Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kkemenczy(a)novell.com QAContact: qa(a)suse.de Found By: --- PLease find the attached hungarion translation for audacity. Please put it to the source, I will also send it to the authors. 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 3

[Bug 292662] New: Inconsistent behaviour of numeric keypad
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=292662 Summary: Inconsistent behaviour of numeric keypad Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DrDiettrich1(a)aol.com QAContact: qa(a)suse.de Found By: Customer Keyboard layout: German (cannot test with other keyboards). With numlock off, the numpad emulates cursor etc. keys as expected, e.g. num-4 acts as CURSOR-LEFT, num-0 as INSERT. But modifier keys (SHIFT, CTRL...) break the expected behaviour, e.g. SHIFT-num-0 is not interpreted as SHIFT-INSERT (Paste), instead digits are echoed in the console, editors or other applications. The same misbehaviour can be found in other Linux distributions. It might be subject to configuration, but I have no idea where to start searching. DoDi -- 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 2

[Bug 296418] New: NX sessions from Windows nxclient get wrong keyboard mapping
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=296418 Summary: NX sessions from Windows nxclient get wrong keyboard mapping Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: R.Vickers(a)cs.rhul.ac.uk QAContact: sndirsch(a)novell.com Found By: Customer Since upgrading to OpenSuSE 10.2 we found that people connecting to NX sessions from the latest nxclient on Windows always got the default American keyboard mapping instead of the appropriate local one (British, in our case). I believe the problem is in nxagent, because the binary includes the string /usr/X11R6/lib/X11/xkb which is a non-existent directory: $ strings /usr/lib/NX/nxagent | grep X11/xkb /usr/share/X11/xkb/X0-config.keyboard /usr/X11R6/lib/X11/xkb I have tested a workround, which is to set up a link /usr/X11R6/lib/X11/xkb -> /usr/share/X11/xkb We are running filesystem-10.2-22 NX-1.5.0-73 (32-bit version) xkeyboard-config-0.9-24 nxclient for Windows 3.0.0.68 (from nomachine.com) Note that connections from the Linux nxclient do not suffer from this problem. -- 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 295074] New: gnome-xgl-settings broken
by bugzilla_noreply＠novell.com 02 Aug '07

02 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295074 Summary: gnome-xgl-settings broken Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Other AssignedTo: dreveman(a)novell.com ReportedBy: jigish.gohil(a)gmail.com QAContact: qa(a)suse.de CC: mhopf(a)novell.com Found By: --- Desktop Effects (gnome-xgl-settings) fails to launch on Alpha6 and Factory. ---------------- (gdb) run Starting program: /usr/bin/gnome-xgl-settings Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread 0xb6d406c0 (LWP 11256)] Bonobo accessibility support initialized GTK Accessibility Module initialized Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6d406c0 (LWP 11256)] update_plugins (plugins=0x80f5a58) at plugins.c:176 176 for (i = 0; supports[i].plugin; i++) { ------------- Let me know if any other information is required. -- 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 2

[Bug 295818] New: Package fuse-2.7.0-5.1.i586 need licenses
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295818 Summary: Package fuse-2.7.0-5.1.i586 need licenses Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: freespacer(a)gmx.de QAContact: qa(a)suse.de Found By: --- Hello, I want to update from fuse-2.6.5-15.1 to fuse-2.7.0-5.1 from the "Build Service": http://download.opensuse.org/repositories/filesystems/openSUSE_10.2/i586/ But I can't update fuse-2.7.0 because I get an error message from rpm below. #rpm -Uhv * error: Failed dependencies: licenses is needed by fuse-2.7.0-5.1.i586 I assume this rpm-packages was build 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 4

[Bug 169799] YaST Xen Manamgent locks down package database.
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=169799#c19 --- Comment #19 from Stephen Shaw <stshaw(a)novell.com> 2007-08-01 16:20:55 MST --- Someone mentioned that I might not have explained myself well enough. To me this seems a critical/blocker bug. The idea is that once you have yast2 open and select a module (ie. dns server or dhcp server) that it locks the rpm db. In order for the rpm db to be released you have to close the module AND close yast2. So for example if you wanted to update your dns server and add a couple packages right after without closes yast2 you would not be able to. You would have to close out the dns server module (which is fine), close yast2, open yast2, and then open software management. As a user this would bug me a lot. I imagine that the average user would be bugged by it as well. As Axel mentioned, this is a usability issue. And a good reason not to use yast for administrative actions. -- 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 0

[Bug 246684] Reading fstab when upgrading
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=246684#c7 Lukas Ocilka <locilka(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |LATER --- Comment #7 from Lukas Ocilka <locilka(a)novell.com> 2007-08-01 15:06:03 MST --- for 'after 10.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 0

[Bug 272899] New: intltool missing dependency on perl XML::Parser
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=272899 Summary: intltool missing dependency on perl XML::Parser Product: openSUSE 10.3 Version: Alpha 3plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-gnome-build(a)forge.provo.novell.com ReportedBy: contact(a)i-nz.net QAContact: qa(a)suse.de >From a build log of a package against factory: checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool -- 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, or are watching someone who is.

1 1