June 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 696813] New: After zypper dup to 12.1 Milestone 1 and reboot Xorg fails on input devices
by bugzilla_noreply＠novell.com 11 Jun '11

11 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=696813 https://bugzilla.novell.com/show_bug.cgi?id=696813#c0 Summary: After zypper dup to 12.1 Milestone 1 and reboot Xorg fails on input devices Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: sboyce(a)blueyonder.co.uk QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Running the same kernel and NVidia driver as before the update to Milestone 1. Output from /var/log/Xorg.0.log ================================= [ 1840.386] (II) Initializing built-in extension XKEYBOARD [ 1840.386] (II) Initializing built-in extension XC-MISC [ 1840.386] (II) Initializing built-in extension SECURITY [ 1840.386] (II) Initializing built-in extension XINERAMA [ 1840.386] (II) Initializing built-in extension XFIXES [ 1840.386] (II) Initializing built-in extension RENDER [ 1840.386] (II) Initializing built-in extension RANDR [ 1840.386] (II) Initializing built-in extension COMPOSITE [ 1840.386] (II) Initializing built-in extension DAMAGE [ 1840.388] (II) Initializing extension GLX [ 1840.419] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-8AA988DD479FAABEC4FC3CCCF4CC29B4948840B4.xkm [ 1840.425] (II) config/udev: Adding input device Power Button (/dev/input/event6) [ 1840.425] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 1840.425] (**) Power Button: Applying InputClass "LocalKeyboard" [ 1840.425] (II) LoadModule: "evdev" [ 1840.425] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so [ 1840.425] (II) Module evdev: vendor="X.Org Foundation" [ 1840.425] compiled for 1.9.3, module version = 2.6.0 [ 1840.425] Module class: X.Org XInput Driver [ 1840.425] ABI class: X.Org XInput driver, version 11.0 [ 1840.425] (**) Power Button: always reports core events [ 1840.425] (**) Power Button: Device: "/dev/input/event6" [ 1840.425] (--) Power Button: Found keys [ 1840.425] (II) Power Button: Configuring as keyboard [ 1840.425] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 1840.425] (**) Option "xkb_rules" "evdev" [ 1840.425] (**) Option "xkb_model" "evdev" [ 1840.425] (**) Option "xkb_layout" "gb" [ 1840.427] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-44AA24B5111FC5EE0AF6A03B7063C3BC9743BCE5.xkm [ 1840.428] (II) config/udev: Adding input device Power Button (/dev/input/event5) [ 1840.428] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 1840.428] (**) Power Button: Applying InputClass "LocalKeyboard" [ 1840.428] (**) Power Button: always reports core events [ 1840.428] (**) Power Button: Device: "/dev/input/event5" [ 1840.428] (--) Power Button: Found keys [ 1840.428] (II) Power Button: Configuring as keyboard [ 1840.428] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 1840.428] (**) Option "xkb_rules" "evdev" [ 1840.428] (**) Option "xkb_model" "evdev" [ 1840.428] (**) Option "xkb_layout" "gb" [ 1840.432] (II) config/udev: Adding input device Logitech Trackball (/dev/input/event0) [ 1840.432] (**) Logitech Trackball: Applying InputClass "evdev pointer catchall" [ 1840.432] (**) Logitech Trackball: always reports core events [ 1840.432] (**) Logitech Trackball: Device: "/dev/input/event0" [ 1840.432] (--) Logitech Trackball: Found 3 mouse buttons [ 1840.432] (--) Logitech Trackball: Found scroll wheel(s) [ 1840.432] (--) Logitech Trackball: Found relative axes [ 1840.432] (--) Logitech Trackball: Found x and y relative axes [ 1840.432] (II) Logitech Trackball: Configuring as mouse [ 1840.432] (II) Logitech Trackball: Adding scrollwheel support [ 1840.432] (**) Logitech Trackball: YAxisMapping: buttons 4 and 5 [ 1840.432] (**) Logitech Trackball: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 1840.432] (II) XINPUT: Adding extended input device "Logitech Trackball" (type: MOUSE) [ 1840.432] (**) Logitech Trackball: (accel) keeping acceleration scheme 1 [ 1840.432] (**) Logitech Trackball: (accel) acceleration profile 0 [ 1840.432] (**) Logitech Trackball: (accel) acceleration factor: 2.000 [ 1840.432] (**) Logitech Trackball: (accel) acceleration threshold: 4 [ 1840.432] (II) Logitech Trackball: initialized for relative axes. [ 1840.432] (II) config/udev: Adding input device Logitech Trackball (/dev/input/mouse0) [ 1840.432] (II) No input driver/identifier specified (ignoring) [ 1840.434] (II) config/udev: Adding input device NOVATEK Kensington U+P Keyboard (/dev/input/event1) [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Applying InputClass "evdev keyboard catchall" [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Applying InputClass "LocalKeyboard" [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: always reports core events [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Device: "/dev/input/event1" [ 1840.434] (--) NOVATEK Kensington U+P Keyboard: Found keys [ 1840.434] (II) NOVATEK Kensington U+P Keyboard: Configuring as keyboard [ 1840.434] (II) XINPUT: Adding extended input device "NOVATEK Kensington U+P Keyboard" (type: KEYBOARD) [ 1840.434] (**) Option "xkb_rules" "evdev" [ 1840.434] (**) Option "xkb_model" "evdev" [ 1840.434] (**) Option "xkb_layout" "gb" [ 1840.434] (II) config/udev: Adding input device NOVATEK Kensington U+P Keyboard (/dev/input/event2) [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Applying InputClass "evdev keyboard catchall" [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Applying InputClass "LocalKeyboard" [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: always reports core events [ 1840.434] (**) NOVATEK Kensington U+P Keyboard: Device: "/dev/input/event2" [ 1840.434] (--) NOVATEK Kensington U+P Keyboard: Found keys [ 1840.434] (II) NOVATEK Kensington U+P Keyboard: Configuring as keyboard [ 1840.434] (II) XINPUT: Adding extended input device "NOVATEK Kensington U+P Keyboard" (type: KEYBOARD) [ 1840.434] (**) Option "xkb_rules" "evdev" [ 1840.434] (**) Option "xkb_model" "evdev" [ 1840.434] (**) Option "xkb_layout" "gb" [ 1840.435] (II) config/udev: Adding input device CH PRODUCTS CH PRO PEDALS USB (/dev/input/event3) [ 1840.435] (II) No input driver/identifier specified (ignoring) [ 1840.435] (II) config/udev: Adding input device CH PRODUCTS CH PRO PEDALS USB (/dev/input/js0) [ 1840.435] (II) No input driver/identifier specified (ignoring) [ 1840.435] (II) config/udev: Adding input device CH PRODUCTS CH FLIGHT SIM YOKE USB (/dev/input/event4) [ 1840.435] (II) No input driver/identifier specified (ignoring) [ 1840.436] (II) config/udev: Adding input device CH PRODUCTS CH FLIGHT SIM YOKE USB (/dev/input/js1) [ 1840.436] (II) No input driver/identifier specified (ignoring) [ 1840.470] (II) Power Button: Close [ 1840.470] (II) UnloadModule: "evdev" [ 1840.486] (II) Power Button: Close [ 1840.486] (II) UnloadModule: "evdev" [ 1840.502] (II) Logitech Trackball: Close [ 1840.502] (II) UnloadModule: "evdev" [ 1840.518] (II) NOVATEK Kensington U+P Keyboard: Close [ 1840.518] (II) UnloadModule: "evdev" [ 1840.534] (II) NOVATEK Kensington U+P Keyboard: Close [ 1840.534] (II) UnloadModule: "evdev" Reproducible: Always Steps to Reproduce: 1.Reboot to init 5 or going to init 5 from init 3 2. 3. Actual Results: kdm keeps running, Xorg crashes Expected Results: Xorg should be running and kdm login screen should be presented. -- 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 34

[Bug 671845] New: git-config does not save global preferences
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=671845 https://bugzilla.novell.com/show_bug.cgi?id=671845#c0 Summary: git-config does not save global preferences Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: gilles.sabourin(a)free.fr QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729) I wanted to use git with colored output and passed this command : git config --global color.ui true git output is appearing colored, but whenever I close the terminal and restart a new one, this configuration is lost. if $HOME/.gitconfig file does not exist, and this is the case when a new development environment is set up from scratch, this file is not created and configuration changes are not saved. As a workaround, simply pass the command below, before doing any global configuration : touch ~/.gitconfig Reproducible: Always Steps to Reproduce: 1. delete your $HOME/.gitconfig file or rename it 2. modify git global configuration with a command like : git config --global color.ui true Actual Results: $HOME/.gitconfig file is not created. As a consequence, git global configuration is not saved Expected Results: $HOME/.gitconfig file creation with valid content. With the command above, this content should be : [color] ui = true -- 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 699350] New: Device Mapper Multipath is too slow at issuing failback to large number of LUs under heavy load
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=699350 https://bugzilla.novell.com/show_bug.cgi?id=699350#c0 Summary: Device Mapper Multipath is too slow at issuing failback to large number of LUs under heavy load Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: sean.stewart(a)netapp.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.71 Safari/534.24 After issuing a controller reboot while running I/O to 256 volumes with Device Mapper, it can take up to 40 minutes for the failback process to complete and all paths to be seen as expected. When running a reboot interval of 10 minutes for an automated reboot test case, this almost inevitably leads to I/Os timing out. Reproducible: Always Steps to Reproduce: 1. Map 255 volumes from an external storage array to a host running SLES 11 SP 1 and DMMP 2. Run I/O to these LUs using an I/O tool, to bog down the system 3. Reboot one of the controllers Actual Results: The process of transferring and transferring back after the controller reboot completes takes almost 40 minutes. This can lead to I/Os timing out if successive controller reboots take place, because DMMP can have no available paths for some devices, even though the system has complete access to the devices at the lower level. Expected Results: DMMP should be quicker to discover the reinstated paths and failback to the preferred paths. -- 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 684044] New: mini-xml-2.5's pkg-config typo in mxml.pc.in
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=684044 https://bugzilla.novell.com/show_bug.cgi?id=684044#c0 Summary: mini-xml-2.5's pkg-config typo in mxml.pc.in Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: vadimuzzz(a)inbox.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 cat /usr/lib64/pkgconfig/mxml.pc : prefix=/usr exec_prefix=/usr libdir=/usr/lib64 includedir=/usr/include Name: Mini-XML Description: Lightweight XML support library Version: 2.5 Libs: -L/usr/lib64 -lmxml @PHTREAD_LIBS@ Cflags: -D_THREAD_SAFE -D_REENTRANT This bug was fixed in version 2.6 Reproducible: Always Steps to Reproduce: 1. install mxml-devel 2. cat cat /usr/lib64/pkgconfig/mxml.pc 3. typo: @PHTREAD_LIBS@ -- 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 648595] New: Missing Perl Module Convert::BinHex.pm
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=648595 https://bugzilla.novell.com/show_bug.cgi?id=648595#c0 Summary: Missing Perl Module Convert::BinHex.pm Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: 64bit OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gjn(a)gjn.priv.at QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-30.2 Firefox/3.6.10 The Convert::BinHex is not used directly by amavisd nor by SpamAssassin. It is a dependancy from a MIME-Tools perl module. Seems like whoever did the package for MIME-Tools forgot to specify this dependency. (Mark Matinec) .. please insert it on next update 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 13

[Bug 698243] New: Cannot Delete Temp Files From orbit-gdm
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=698243 https://bugzilla.novell.com/show_bug.cgi?id=698243#c0 Summary: Cannot Delete Temp Files From orbit-gdm Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: drichard(a)largo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 The temp files in /tmp/orbit-gdm continue to grow in number and are never purged, and any attempt to delete them cause GDM to fail. I tried to delete them first based on date, and this issue happened...so I assumed that a live socket/file was deleted. So I used /usr/bin/linc-cleanup-sockets which only deletes dead files and the same thing happened again. What happens is that gconfd processes begin to spin and consume all of the memory on the server until it's so busy swapped that it requires a reboot. So it seems like just *touching* anything that folder causes this failure. It's almost like gdm has the whole folder locked and assumes nothing will change. Before I knew about the files, at one point we had grown to over 1 million linc* files, and as the number grows it seems like gdm begins to get slower. Obviously one could get them at reboot, but if your goal is to have the servers running for months at a time, this isn't a good solution. 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 3

[Bug 699149] New: networkmanager does not connect to Android Mobile Hotspot
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=699149 https://bugzilla.novell.com/show_bug.cgi?id=699149#c0 Summary: networkmanager does not connect to Android Mobile Hotspot Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dpbasti(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 New Android phones enable network tethering. They create hotspot and i'm able to connect this hotspot both with ubuntu and windoze but i can't with opensuse 11.3 the connection says activating and nothing happens. Then it keeps asking for network password and retries to connect without success. No matter what encription i choose- wep, wpa1 , wpa2 or open - it never succeeds. Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Activation (wlan0/wireless): connection 'polrus' has security, and secrets exist. No new secrets needed. Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'ssid' value 'polrus' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'scan_ssid' value '1' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'key_mgmt' value 'NONE' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'auth_alg' value 'OPEN' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'wep_key0' value '<omitted>' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'wep_key1' value '<omitted>' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'wep_key2' value '<omitted>' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'wep_key3' value '<omitted>' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: added 'wep_tx_keyidx' value '0' Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> Config: set interface ap_scan to 1 Jun 9 22:10:47 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 9 22:10:48 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: scanning -> associating Jun 9 22:10:58 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: associating -> disconnected Jun 9 22:10:58 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 9 22:10:59 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: scanning -> associating Jun 9 22:11:09 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: associating -> disconnected Jun 9 22:11:09 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: disconnected -> scanning Jun 9 22:11:10 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: scanning -> associating Jun 9 22:11:13 sebastian-dell NetworkManager[1362]: <warn> Activation (wlan0/wireless): association took too long. Jun 9 22:11:13 sebastian-dell NetworkManager[1362]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Jun 9 22:11:13 sebastian-dell NetworkManager[1362]: <warn> Activation (wlan0/wireless): asking for new secrets Jun 9 22:11:13 sebastian-dell NetworkManager[1362]: <info> (wlan0): supplicant connection state: associating -> disconnected Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <info> (wlan0): device state change: 6 -> 9 (reason 7) Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <warn> Activation (wlan0) failed for access point (polrus) Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <info> Marking connection 'polrus' invalid. Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <warn> Activation (wlan0) failed. Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Jun 9 22:11:14 sebastian-dell NetworkManager[1362]: <info> (wlan0): deactivating device (reason: 0). Reproducible: Always Steps to Reproduce: 1.try to connect both by kde4 or gnome networkmanager applet 2. 3. Actual Results: fails to connect and asks for password again and again -- 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 633719] New: y2base always returns code 020 at exit
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=633719 https://bugzilla.novell.com/show_bug.cgi?id=633719#c0 Summary: y2base always returns code 020 at exit Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rpmcruz(a)alunos.dcc.fc.up.pt QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-PT; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Ant.com Toolbar 2.0.1 Firefox/3.6.8 y2base always returns code non-zero even when exiting successfully. Code 020 to be precise. You can tell by running it through gdb. That's of course heterodox behavior, and presumably that was not always how it behaved, because /sbin/yast2 checks whether y2base returns 0 or not (see exit_trap()). Such check is obviously unnecessary now. It is annoying because any little error message is displayed by /sbin/yast2 as if it crashed (see bug 629020). Reproducible: Always -- 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 699282] New: not helpful error when repomd.xml.asc is 0 bytes
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=699282 https://bugzilla.novell.com/show_bug.cgi?id=699282#c0 Summary: not helpful error when repomd.xml.asc is 0 bytes Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: meissner(a)novell.com QAContact: qa(a)suse.de Found By: Third Party Developer/Partner Blocker: --- we had packman repomd.xml.asc being 0 byte, which lead to a kind of unreadable errors. zypper: Retrieving repository 'PACKMANTEST' metadata [\] File 'repomd.xml' from repository 'PACKMANTEST' is signed with an unknown key ''. Continue? [yes/no] (no): other zypp users display a similar message. Perhaps a different error handling could be done here. -- 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 699240] New: after "zypper up" "startx" is broken
by bugzilla_noreply＠novell.com 10 Jun '11

10 Jun '11

https://bugzilla.novell.com/show_bug.cgi?id=699240 https://bugzilla.novell.com/show_bug.cgi?id=699240#c0 Summary: after "zypper up" "startx" is broken Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i386 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: andreas.roehler(a)online.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 after `zypper up' `startx' doesn't work any more. Get a warning pointing at permissions of /usr/bin/Xorg After a chmod a+s it works again. Best regards, Andreas Linux noname 2.6.37.6-0.5-default #1 SMP 2011-04-25 21:48:33 +0200 i686 athlon i386 GNU/Linux 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 2