April 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 596831] New: nano security fixes
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=596831 http://bugzilla.novell.com/show_bug.cgi?id=596831#c0 Summary: nano security fixes Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: crrodriguez(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- Your friendly security team received the following report via oss-security. Please respond ASAP. The issue is public. Minor, so fix for Factory sufficient. ------------------------------------------------------------------------------ Date: Wed, 14 Apr 2010 11:22:32 -0400 From: Dan Rosenberg <dan.j.rosenberg(a)gmail.com> Subject: [oss-security] CVE request: GNU nano (minor) Two issues were recently addressed upstream for GNU nano to provide better security when editing files owned by other untrusted users, especially when editing as root. I'm not sure if either of these issues require CVE identifiers due to the narrow circumstances in which they can be exploited, but I figured I'd leave that up to you. Changelog is at http://svn.savannah.gnu.org/viewvc/trunk/nano/ChangeLog?root=nano&view=log, relevant entries at revisions 4490, 4491, 4493, and 4496. 1. When editing a file owned by another user, the owner of the file may replace the file mid-editing with a symbolic link, resulting in the editor overwriting the target of the symbolic link on saving with the privileges of the user doing the editing, without any warning to the editor. Since this could be considered akin to replacing a target being chown'd or chmod'd with a symbolic link and requires a very targeted attack, I would lean towards this not needing a CVE, but that's your call. 2. When backup files are enabled and root is editing a file by an untrusted user, that user may exploit race conditions in the creation of backup files to take ownership of arbitrary files. While the scenario for exploitation is somewhat unlikely (root editing untrusted files), this attack can be done reliably and without requiring precise timing, so this seems to be a good candidate for a CVE. Thanks, Dan Rosenberg -- Configure bugmail: http://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 596105] New: splashy mkinitrd script needs DirectFB-devel
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=596105 http://bugzilla.novell.com/show_bug.cgi?id=596105#c0 Summary: splashy mkinitrd script needs DirectFB-devel Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: hmacht(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- # mkinird .. /lib/mkinitrd/setup/01-splashy.sh: line 67: directfb-config: command not found .. # rpm -q splashy splashy-0.3.13-7.6.x86_64 # rpm -V splashy S.5....T. c /etc/splashy/config.xml # -- Configure bugmail: http://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 597594] New: In gpk-application cancel button does not work
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=597594 http://bugzilla.novell.com/show_bug.cgi?id=597594#c0 Summary: In gpk-application cancel button does not work Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: neptunia(a)mail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 In gpk-application ('Install/remove software tool) cancel button does not work, but exit through the window's close button works well. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 366804] Can the boot time of 11.x be decreased ?
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=366804 http://bugzilla.novell.com/show_bug.cgi?id=366804#c4 --- Comment #4 from Glenn Doig <doiggl(a)velocitynet.com.au> 2010-04-19 05:51:28 UTC --- boot with parameter init=/sbin/bootchartd -- Configure bugmail: http://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 597626] New: zypper crash
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=597626 http://bugzilla.novell.com/show_bug.cgi?id=597626#c0 Summary: zypper crash Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- linux-xlya:/home/harald # rpm -q zypper zypper-1.4.1-1.1.x86_64 linux-xlya:/home/harald # zypper up Retrieving repository 'f-non-oss' metadata [\]Segmentation fault (core dumped) gdb zypper core (gdb) where #0 0x00007f0289f844d9 in zypp::parser::susetags::intrusive_ptr_release(zypp::parser::susetags::RepoIndex const*) () from /usr/lib64/libzypp.so.631 #1 0x00007f0289f85805 in zypp::parser::susetags::ContentFileReader::endParse() () from /usr/lib64/libzypp.so.631 #2 0x00007f0289f864b7 in zypp::parser::susetags::ContentFileReader::parse(zypp::InputStream const&, boost::function<bool ()(zypp::ProgressData const&)> const&) () from /usr/lib64/libzypp.so.631 #3 0x00007f028a0619fa in zypp::repo::susetags::Downloader::download(zypp::MediaSetAccess&, zypp::filesystem::Pathname const&, boost::function<bool ()(zypp::ProgressData const&)> const&) () from /usr/lib64/libzypp.so.631 #4 0x00007f028a1969b5 in zypp::RepoManager::refreshMetadata(zypp::RepoInfo const&, zypp::RepoManager::RawMetadataRefreshPolicy, boost::function<bool ()(zypp::ProgressData const&)> const&) () from /usr/lib64/libzypp.so.631 #5 0x0000000000481d7e in ?? () #6 0x000000000049db13 in void do_init_repos<std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >(Zypper&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) () #7 0x000000000049e8dd in void init_repos<std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >(Zypper&, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) () #8 0x0000000000492ba8 in init_repos(Zypper&) () #9 0x000000000045b212 in Zypper::doCommand() () #10 0x0000000000461f08 in Zypper::safeDoCommand() () #11 0x0000000000466391 in Zypper::main(int, char**) () #12 0x000000000043c8eb in main () (gdb) ^Z -- Configure bugmail: http://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 579799] New: UMTS (nozomi) does not work with NetworkManager
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=579799 http://bugzilla.novell.com/show_bug.cgi?id=579799#c0 Summary: UMTS (nozomi) does not work with NetworkManager Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: branislav.klocok(a)orava.sk QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.4 (like Gecko) SUSE When I insert my UMTS card into PCMCI slot KNetworkManager does not show the broadband network option. It show it only if it boots with the card inside, but it doues not connect anyhow. Kernel: 2.6.31.12-0.1-desktop #1 SMP PREEMPT 2010-01-27 08:20:11 +0100 i686 i686 i386 NetworkManager 0.7.1_git20090811-4.2NU/Linux ModemManager 0.2_20090810-2.1 UMTS Chip: 06:00.2 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip Modem manager log: modem-manager --debug ** Message: Loaded plugin MotoC ** Message: Loaded plugin Gobi ** Message: Loaded plugin Option ** Message: Loaded plugin Generic ** Message: Loaded plugin Huawei ** Message: Loaded plugin ZTE ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Novatel ** Message: Loaded plugin Sierra ** Message: Loaded plugin Nokia ** Message: Loaded plugin Ericsson MBM ** Message: (noz0) opening serial device... ** (modem-manager:15918): DEBUG: (noz0): probe requested by plugin 'Generic' ** Message: (noz1) opening serial device... ** (modem-manager:15918): DEBUG: (noz1): probe requested by plugin 'Generic' ** Message: (noz2) opening serial device... ** (modem-manager:15918): DEBUG: (noz2): probe requested by plugin 'Generic' ** Message: (noz3) opening serial device... ** (modem-manager:15918): DEBUG: (noz3): probe requested by plugin 'Generic' ** (modem-manager:15918): DEBUG: (noz0): --> 'AT+GCAP<CR>' ** (modem-manager:15918): DEBUG: (noz0): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:15918): DEBUG: (noz1): --> 'AT+GCAP<CR>' ** (modem-manager:15918): DEBUG: (noz2): --> 'AT+GCAP<CR>' ** (modem-manager:15918): DEBUG: (noz3): --> 'AT+GCAP<CR>' ** (modem-manager:15918): DEBUG: (noz2): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:15918): DEBUG: (noz3): <-- '<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' ** Message: (noz0) closing serial device... ** Message: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/0000:06:00.2 claimed port noz0 ** (modem-manager:15918): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/0000:06:00.2 ** (modem-manager:15918): WARNING **: signal "completed" (from "Completed") exported but not found in object class "MMGenericGsm" ** (modem-manager:15918): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/0000:06:00.2 as /org/freedesktop/ModemManager/Modems/0 ** Message: (noz2) closing serial device... ** Message: (noz3) closing serial device... ** Message: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/0000:06:00.2 claimed port noz2 ** Message: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/0000:06:00.2 claimed port noz3 ** (modem-manager:15918): DEBUG: (noz1): --> 'AT+GCAP<CR>' ** (modem-manager:15918): DEBUG: (noz1): --> 'AT+GCAP<CR>' ** Message: (noz1) closing serial device... NetworkManager log: etworkManager --no-daemon NetworkManager: <info> starting... -- Error received: File exists -- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC> sequence-nr=1266088103 pid=4210227 NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess NetworkManager: <info> Found new GSM modem device 'noz0' (driver: 'nozomi'). NetworkManager: <info> (noz0): exported as /org/freedesktop/ModemManager/Modems/0 libhal.c 2669 : invalid udi: /org/freedesktop/ModemManager/Modems/0 doesn't startwith '/org/freedesktop/Hal/devices/'. NetworkManager: <info> (noz0): now unmanaged NetworkManager: <info> Setting system hostname to 'localhost' (no default device) NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4227_rfkill_phy0_wlan NetworkManager: nm_device_ethernet_new: assertion `driver != NULL' failed NetworkManager: <info> Found new Ethernet device 'eth0' (driver: 'e1000e'). NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_16_d3_3e_3c_59 NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01). NetworkManager: <info> Found new 802.11 WiFi device 'wlan0' (driver: 'iwl3945'). NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1b_77_54_4a_25 NetworkManager: <info> Setting system hostname to 'brko-notebook' (from system configuration) NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSettingGsm' / '(null)' invalid: 3 NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2) NetworkManager: <info> (eth0): bringing up device. NetworkManager: <info> (eth0): preparing device. NetworkManager: <info> (eth0): deactivating device (reason: 2). NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2) NetworkManager: <info> (wlan0): bringing up device. NetworkManager: <info> (wlan0): preparing device. NetworkManager: <info> (wlan0): deactivating device (reason: 2). NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 0) NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready NetworkManager: <info> Activation (wlan0) starting connection 'brko' NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) NetworkManager: <info> Activation (wlan0/wireless): access point 'brko' has security, but secrets are required. NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0) NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'. NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'. NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0) NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) NetworkManager: <info> Activation (wlan0/wireless): connection 'brko' has security, and secrets exist. No new secrets needed. NetworkManager: <info> Config: added 'ssid' value 'brko' NetworkManager: <info> Config: added 'scan_ssid' value '1' NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' NetworkManager: <info> Config: added 'wep_key0' value '<omitted>' NetworkManager: <info> Config: added 'wep_key1' value '<omitted>' NetworkManager: <info> Config: added 'wep_key2' value '<omitted>' NetworkManager: <info> Config: added 'wep_key3' value '<omitted>' NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0' NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Config: set interface ap_scan to 1 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'brko'. NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0) NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. NetworkManager: <info> dhclient started with pid 15963 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit Listening on LPF/wlan0/00:1b:77:54:4a:25 Sending on LPF/wlan0/00:1b:77:54:4a:25 Sending on Socket/fallback DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.9 -- renewal in 42654 seconds. NetworkManager: <info> DHCP: device wlan0 state changed preinit -> reboot NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... NetworkManager: <info> address 192.168.1.9 NetworkManager: <info> prefix 24 (255.255.255.0) NetworkManager: <info> gateway 192.168.1.1 NetworkManager: <info> nameserver '192.168.1.1' NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0) (NetworkManager:15923): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GObject' (NetworkManager:15923): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (NetworkManager:15923): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GObject' (NetworkManager:15923): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed NetworkManager: <debug> [1266088120.028537] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' NetworkManager: <debug> [1266088120.066417] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.1.1' NetworkManager: <info> Clearing nscd hosts cache. NetworkManager: <info> Policy set 'brko' (wlan0) as default for routing and DNS. NetworkManager: <info> Activation (wlan0) successful, device activated. NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 591959] New: allow NetworkManager to setup wpa_supplicant with nl80211 driver
by bugzilla_noreply＠novell.com 19 Apr '10

19 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=591959 http://bugzilla.novell.com/show_bug.cgi?id=591959#c0 Summary: allow NetworkManager to setup wpa_supplicant with nl80211 driver Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kkhere.geo(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.2) Gecko/20100317 SUSE/3.6.2-1.2 Firefox/3.6.2 Apropos of bug 585802: "For openSUSE:11.3 it would be required to switch as many drivers as possible to the new "nl80211" driver to not to restricts any devices to "world" (ie. most restrictive) regulatory domain." As already proposed in bug 537708 comment 6, it makes sense to use the new driver as default, except in cases where it does not work." For users who use NetworkManager this will not work: in NetworkManager/src/supplicant-manager/nm-supplicant-interface.c:857 "wext" is hardcoded as the driver. This should be changed. The user should be allowed to choose nl80211 driver. Reproducible: Always Steps to Reproduce: 1. see NetworkManager/src/supplicant-manager/nm-supplicant-interface.c:857 2. 3. -- Configure bugmail: http://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 590468] New: kernel 2.6.31.12.0.2 causes mce with HDA Intel sound
by bugzilla_noreply＠novell.com 18 Apr '10

18 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c0 Summary: kernel 2.6.31.12.0.2 causes mce with HDA Intel sound Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jpschewe(a)mtu.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 2.6.31.12.0.1 boots for me and when it is initializing the sound I see this: <6>[ 14.349015] HDA Intel 0000:00:10.1: PCI INT B -> Link[LAZA] -> GSI 20 (level, low) -> IRQ 20 <7>[ 14.367078] alloc irq_desc for 27 on node 0 <7>[ 14.367081] alloc kstat_irqs on node 0 <7>[ 14.367092] HDA Intel 0000:00:10.1: irq 27 for MSI/MSI-X <7>[ 14.367122] HDA Intel 0000:00:10.1: setting latency timer to 64 <4>[ 14.424619] ALSA /usr/src/packages/BUILD/kernel-default-2.6.31.12/linux-2.6.31/sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x000f0000 However when I boot 2.6.31.12.0.2 that last line doesn't appear and I get an mce error with "4 bank 4:" and then either f200000000070f0f or b200000000070f0f. The motherboard is an MSI K8NGM2-FID with onboard sound, sata and video from NVidia. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 16

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 18 Apr '10

18 Apr '10

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&a… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! xrdp missing in repositories -> http://bugzilla.novell.com/show_bug.cgi?id=555830 scim-bridge version 0.4.15-116.3 -> http://bugzilla.novell.com/show_bug.cgi?id=556094

1 0

[Bug 593537] New: vpnc fails to create tun device with permission denied
by bugzilla_noreply＠novell.com 18 Apr '10

18 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=593537 http://bugzilla.novell.com/show_bug.cgi?id=593537#c0 Summary: vpnc fails to create tun device with permission denied Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: digiplan.pt(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.2) Gecko/20100317 SUSE/3.6.2-1.2 Firefox/3.6.2 using vpnc is supposed to work with user rights, however OpenSuse does not allow to create tun device to proceed. This following command works as root, but not as normal user. Reproducible: Always Steps to Reproduce: 1. /usr/sbin/vpnc 2. answer prompt questions 3. fails with the error Failed to bind to 0.0.0.0:500: Permission denied Actual Results: antocm@esprimo:~> /usr/sbin/vpnc --debug 99 WARNING! active debug level is >= 99, output includes username and password (hex encoded) WARNING! active debug level is >= 99, output includes username and password (hex encoded) Enter IPSec gateway address: <VPNserver> Enter IPSec ID for VPNserver: <ID> Enter IPSec secret for VPNserver: <secret> Enter username for VPNserver: <username> Enter password for username@VPNserver: vpnc version 0.5.3 hex_test: 00010203 S1 init_sockaddr [2010-04-02 23:00:57] S2 make_socket [2010-04-02 23:00:57] /usr/sbin/vpnc: Error binding to source port. Try '--local-port 0' Failed to bind to 0.0.0.0:500: Permission denied -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3