January 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 764269] New: threading issue in libvdpau / flash plugin 11.2.202.235-21.1 crashes in firefox and chrome after online update
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=764269 https://bugzilla.novell.com/show_bug.cgi?id=764269#c0 Summary: threading issue in libvdpau / flash plugin 11.2.202.235-21.1 crashes in firefox and chrome after online update Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: Firefox AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: meissner(a)suse.com QAContact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com, dmueller(a)suse.com, wolfgang(a)rosenauer.org Depends on: 761975 Found By: --- Blocker: --- (copy of public facing bug which ahs too many people cced) i debugged flash-player a bit export MOZ_X_SYNC=1 firefox& gdb attach to plugin container wait for crash bt I get different backtraces every time, but libvdpau* and the main plugin gtk2 window are involved always. I attach the full backtrace too, but I see an assertion trigger: Thread 21 (Thread 0x7fc43dd2e700 (LWP 19486)): #0 0x00007fc46d098ab5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007fc46d099fb6 in abort () at abort.c:92 #2 0x00007fc46d091385 in __assert_fail (assertion=0x7fc469dbc050 "req == dpy->xcb->pending_requests", file=<value optimized out>, line=140, function=<value optimized out>) at assert.c:81 #3 0x00007fc469d464b1 in dequeue_pending_request (dpy=<value optimized out>, req=<value optimized out>) at xcb_io.c:140 #4 0x00007fc469d473f8 in _XReply (dpy=0x7fc464465000, rep=0x7fc43dd2d810, extra=0, discard=1) at xcb_io.c:563 #5 0x00007fc469d42b13 in XSync (dpy=0x7fc464465000, discard=0) at Sync.c:44 #6 0x00007fc469d42bbb in _XSyncFunction (dpy=<value optimized out>) at Synchro.c:35 No locals. #7 0x00007fc457037135 in ?? () from /usr/lib64/vdpau/libvdpau_nvidia.so.1 No symbol table info available. Thread 1 (Thread 0x7fc46fb43820 (LWP 19434)): #0 0x00007fc469d47265 in _XReply (dpy=0x7fc464465000, rep=0x7fff326344e0, extra=0, discard=1) at xcb_io.c:527 #1 0x00007fc469d42b13 in XSync (dpy=0x7fc464465000, discard=0) at Sync.c:44 #2 0x00007fc469d42bbb in _XSyncFunction (dpy=<value optimized out>) at Synchro.c:35 #3 0x00007fc469d28514 in XFreeGC (dpy=0x7fc464465000, gc=0x7fc464424740) at FreeGC.c:45 #4 0x00007fc4683cb5d8 in gdk_gc_x11_finalize (object=0x7fc45cb13040) at gdkgc-x11.c:84 #5 0x00007fc46a752114 in g_object_unref () from /lib64/libgobject-2.0.so.0 #6 0x00007fc46232e219 in ?? () from /usr/lib64/browser-plugins/libflashplayer.so The problem is here that _XReply is entered twice. -- 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 14

[Bug 796895] New: Firefox 18 etc
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=796895 https://bugzilla.novell.com/show_bug.cgi?id=796895#c0 Summary: Firefox 18 etc Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- Upcoming Firefox/Gecko security releases scheduled for public release 2013-01-08 Firefox 18.0 Thunderbird 17.0.2 SeaMonkey 2.15 requirements: mozilla-nspr 4.9.4 mozilla-nss 3.14.1 (also needed because of bug 796628) (Also released but not relevant for openSUSE: (will be provided from mozilla repo) Firefox 10.0.12esr Firefox 17.0.2esr Thunderbird 10.0.12esr Thunderbird 17.0.2esr xulrunner 10.0.12esr xulrunner 17.0.2esr ) probably additional needed dependent update: chmsee -- 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 795838] New: Installation on /dev/sdb fails on both: new installation or update from 12.1
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=795838 https://bugzilla.novell.com/show_bug.cgi?id=795838#c0 Summary: Installation on /dev/sdb fails on both: new installation or update from 12.1 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hw01(a)heisch.inka.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.1.1 Firefox/3.6.13 Starting Situation: ------------------- /dev/sda contains a (productive) opensuse 11.1 (Kde 3.5 :-) /dev/sdb has had a working opensuse 12.1 (only for software tests KDE4.. :-( Boot loader went to /dev/sdb, and from there to /dev/sda to start 11.1. Installation: ------------ While new installation of 12.2 on /dev/sdb : could not update by net. After first reboot: none of both installations could be started. I repaired the boot for /dev/sda for 11.1 to do my work. To get rid of the problem, I reinstalled 12.1 to try an update to 12.2 Reinstallation of 12.1 worked without a problem. After Updating to 12.2, I could not start 12.2, but with the help of the fallback, I am able to start 11.1, my productive system. What goes wrong? ---------------- Looking at /dev/sdb1/boot/grub/device.map: - - - - - - - - - - - - - - - (hd2) /dev/disk/by-id/ata-SanDisk_SDSSDP064G_121977404574 (hd1) /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 (hd0) /dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S ....... looks OK .. and looking at /dev/sdb1/boot/grub/menu.lst: - - - - - - - - - - - - - - - # Modified by YaST2. Last modification on Mo Dez 24 16:54:22 CET 2012 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader default 3 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 12.2 - 3.4.6-2.10 kernel (hd0,0)/boot/vmlinuz-3.4.6-2.10-desktop root=/dev/sdb1 ^^^^^ resume=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part2 splash=silent quiet video=1280x1024 showopts vga=0x31a initrd (hd0,0)/boot/initrd-3.4.6-2.10-desktop ^^^^^ ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.2 - 3.4.6-2.10 kernel (hd0,0)/boot/vmlinuz-3.4.6-2.10-desktop root=/dev/sdb1 ^^^^^ showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a initrd (hd0,0)/boot/initrd-3.4.6-2.10-desktop ^^^^^^ ###Don't change this comment - YaST2 identifier: Original name: linux### title GNU GRUB 2 -- openSUSE 12.2 - GNU GRUB 2 kernel (hd0,0)/boot/grub2/core.img root=/dev/sdb1 ^^^^^ resume=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part2 splash=silent quiet video=1280x1024 showopts vga=0x31a ###Don't change this comment - YaST2 identifier: Original name: SUSE LINUX 11.1 (/dev/sda1)### title SUSE LINUX 11.1 (/dev/sda1) rootnoverify (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Diskette rootnoverify (hd0) chainloader +1 .............. for me, it looks like the marked parts (^^^^) are pointing to the wrong disk. BTW: Bug report 773576 ======================= is pointing to the same problem. it was Opened: 2012-07-29 22:35 UTC Last modified: 2012-09-07 19:52:49 UTC Remember: we are not talking about one bug in one package, we are talking about the grave bugs of the installation. Bug 773576 was reported over 5 month ago, last time modified over 3 month ago Problem solved? NO, Who cares .. we a preparing a new release ...:-)) I'm selling communications software between Linux and the Siemens plc family Simatic ( http:/sites.inka.de/heisch ). We started with Suse in 1994 and always used Suse as development platform and for applications in industry. In times of Suse 6.3 or 8.1, it was quite easier to install Suse than Windows and also easier to switch to a other hd. ..and I'm sure that there would have been no need to write this bug report, 3 months after the release of the "stable" version. Meanwhile, I'm not quite sure, that opensuse still has the quality to be used in industrial installations. (KDE4 is not, but that's not your problem.) Reproducible: Always Steps to Reproduce: 1. 2 Disks, installing any no 12.2 OS on first disk 2. Installing 12.2 on second disk. Problem should happen after reboot. Actual Results: s.o. Expected Results: s.o. -- 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 22

[Bug 758732] New: linux-boot-prober doesn't read boot entries from openSUSE and Fedora Grub2.
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=758732 https://bugzilla.novell.com/show_bug.cgi?id=758732#c0 Summary: linux-boot-prober doesn't read boot entries from openSUSE and Fedora Grub2. Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 3 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: hippolyte(a)shaw.ca QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=487645) --> (http://bugzilla.novell.com/attachment.cgi?id=487645) support for openSUSE and Fedora grub.cfg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 When linux-boot-prober scans for openSUSE and Fedora boot entries (for example), it doesn't even get to read the boot menu ($mpoint/boot/grub2/grub.cfg), because it looks for it in $mpoint/boot/grub/grub.cfg - where the boot menu is actually located on Debian/Ubuntu. As a consequence, os-prober generates a "minimal" boot entry, which is correct because it knows the partition and the kernel name, but misses all kernel boot parameters, because it could not read them from grub.cfg. The problem is not specific to openSUSE. It affects any distro making use of os-prober to scan fo other distros' kernels - including Ubuntu, which fails to read openSUSE and Fedora. However, Ubuntu boot entries are correct when scanned from anoter distro - because in this case, linux-boot-prober looks for grub.cfg in the right directory (/boot/grub/) I attached a patch which solves the issue. Reproducible: Always Steps to Reproduce: 1.# os-prober /dev/sda2:openSUSE 12.2 Milestone 2 (x86_64):SuSE:linux 2. # linux-boot-prober /dev/sda2 Actual Results: /dev/sda2:/dev/sda2::/boot/vmlinuz-3.3.0-2-desktop:/boot/initrd-3.3.0-2-desktop:root=/dev/sda2 /dev/sda2:/dev/sda2::/boot/vmlinux-3.3.0-2-desktop.gz::root=/dev/sda2 Expected Results: /dev/sda2:/dev/sda2:openSUSE, with Linux 3.3.0-2-desktop:/boot/vmlinuz-3.3.0-2-desktop:/boot/initrd-3.3.0-2-desktop:root=UUID=b5f05dbc-ff30-407a-893f-a445b436b2d3 video=1920x1080 resume=/dev/disk/by-uuid/8ae0e410-f8bc-47ee-a290-f9567f725566 splash=silent quiet showopts /dev/sda2:/dev/sda2:openSUSE, with Linux 3.3.0-2-desktop (recovery mode):/boot/vmlinuz-3.3.0-2-desktop:/boot/initrd-3.3.0-2-desktop:root=UUID=b5f05dbc-ff30-407a-893f-a445b436b2d3 single A patched version of os-prober 1.52 is building in OBS and will be availalbe in my repo: https://build.opensuse.org/package/show?package=os-prober&project=home%3Apl… ... whenever OBS is done - you never know if it takes minutes, hours, days... I ran os-prober on 12.1 to scan for 12.2. It's actually Milestone 3 (bug is discussed here: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta…) -- 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 796896] New: NetworkManager can't activate wireless card
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=796896 https://bugzilla.novell.com/show_bug.cgi?id=796896#c0 Summary: NetworkManager can't activate wireless card Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jhu(a)novell.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- when I use NetControl , the wireless card works fine using a wifi . wlan0 Link encap:Ethernet HWaddr 00:1E:65:6E:90:AE inet addr:192.168.1.105 Bcast:255.255.255.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1 RX packets:62683 errors:0 dropped:0 overruns:0 frame:0 TX packets:73170 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23290188 (22.2 Mb) TX bytes:16478462 (15.7 Mb) but I switch to NetWorkManager, cant activate wireless card. junwork:/etc/NetworkManager # NetworkManager --no-daemon NetworkManager[6900]: <info> NetworkManager (version 0.9.4.0) is starting... NetworkManager[6900]: <info> Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[6900]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[6900]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[6900]: keyfile: parsing Wired connection 1 ... NetworkManager[6900]: keyfile: read connection 'Wired connection 1' NetworkManager[6900]: <info> modem-manager is now available NetworkManager[6900]: <info> monitoring kernel firmware directory '/lib/firmware'. NetworkManager[6900]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill0) (driver (unknown)) NetworkManager[6900]: <info> WiFi enabled by radio killswitch; disabled by state file NetworkManager[6900]: <info> WWAN enabled by radio killswitch; enabled by state file NetworkManager[6900]: <info> WiMAX enabled by radio killswitch; enabled by state file NetworkManager[6900]: <info> Networking is enabled by state file NetworkManager[6900]: <warn> failed to allocate link cache: (-10) Operation not supported NetworkManager[6900]: <info> (eth0): carrier is ON NetworkManager[6900]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2) NetworkManager[6900]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[6900]: <info> (eth0): now managed NetworkManager[6900]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[6900]: <info> (eth0): preparing device. NetworkManager[6900]: <info> (eth0): deactivating device (reason 'managed') [2] NetworkManager[6900]: <info> (wlan0): using nl80211 for WiFi device control NetworkManager[6900]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3) NetworkManager[6900]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[6900]: <info> (wlan0): now managed NetworkManager[6900]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[6900]: <info> (wlan0): bringing up device. NetworkManager[6900]: <info> (wlan0): deactivating device (reason 'managed') [2] NetworkManager[6900]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files NetworkManager[6900]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] ^CNetworkManager[6900]: <info> caught signal 2, shutting down normally. NetworkManager[6900]: <warn> quit request received, terminating... NetworkManager[6900]: <info> (eth0): now unmanaged NetworkManager[6900]: <info> (eth0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] NetworkManager[6900]: <info> (eth0): cleaning up... NetworkManager[6900]: <info> (eth0): taking down device. NetworkManager[6900]: <info> (wlan0): now unmanaged NetworkManager[6900]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[6900]: <info> exiting (success) junwork:/data # rpm -q NetworkManager NetworkManager-0.9.4.0-5.17.1.x86_64 where it goes 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 5

[Bug 797153] New: can't open "main menu" under cinnamon session
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797153 https://bugzilla.novell.com/show_bug.cgi?id=797153#c0 Summary: can't open "main menu" under cinnamon session Classification: openSUSE Product: openSUSE 12.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: jhu(a)novell.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- In gnome3, I search the application "main menu" , run it , ok. but under cinnamon session , can't open it. Always reproducible. junwork:~/Desktop # zypper info cinnamon Loading repository data... Reading installed packages... Information for package cinnamon: Repository: X11:Cinnamon:GNOME34 (12.2) Name: cinnamon Version: 1.6.7-1.1 Arch: x86_64 Vendor: obs://build.opensuse.org/X11 Installed: Yes Status: up-to-date Installed Size: 4.0 MiB Summary: A Linux Desktop similar to GNOME2 based on gnome-shell technology Description: The Cinnamon Desktop provides advanced innovative features and a traditional user experience. The underlying technology is forked from gnome-shell and the desktop layout is closer to GNOME2. The emphasis is put on making users look and feel at home and provide them an easy to use and confortable 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 0

[Bug 797150] New: home:dmitry_serpokryl:drivers/reiser4progs: Bug
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797150 https://bugzilla.novell.com/show_bug.cgi?id=797150#c0 Summary: home:dmitry_serpokryl:drivers/reiser4progs: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dmitry.serpokryl(a)gmail.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Update to latest source: [This has a recent date] http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/ reiser4progs-1.0.7.tar.gz 2011-11-13 845.4 kB And fix reiser4progs.spec error Thanks --Glenn [ 78s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.4qa4w6 [ 78s] + umask 022 [ 78s] + cd /home/abuild/rpmbuild/BUILD [ 78s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-2.1.x86_64 [ 78s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-2.1.x86_64 [ 78s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT [ 78s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-2.1.x86_64 [ 78s] + cd reiser4progs-1.0.7 [ 78s] + echo 'WARNING: REMOVE %suse_update_config. If your sources are really' [ 78s] WARNING: REMOVE %suse_update_config. If your sources are really [ 78s] + echo 'too old to cover current architectures, prefer autoreconf --force --install' [ 78s] too old to cover current architectures, prefer autoreconf --force --install [ 78s] + autoreconf --force --install [ 78s] /var/tmp/rpm-tmp.4qa4w6: line 33: autoreconf: command not found [ 78s] error: Bad exit status from /var/tmp/rpm-tmp.4qa4w6 (%build) -- 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 776385] New: mouse pointer keeps jumping to 0x0
by bugzilla_noreply＠novell.com 07 Jan '13

07 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=776385 https://bugzilla.novell.com/show_bug.cgi?id=776385#c0 Summary: mouse pointer keeps jumping to 0x0 Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- I have seen this initially in a hyper-v guest, but now it happens also with a Xen PV guest: In a GNOME desktop the mouse (or the focus?) suddenly jumps to 0x0, which causes the 'Activities' menu to show up. I have not checked yet if this happens also with KDE. -- 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 24

[Bug 791076] New: AY installation without reboot: syslog service in failed state
by bugzilla_noreply＠novell.com 07 Jan '13

07 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=791076 https://bugzilla.novell.com/show_bug.cgi?id=791076#c0 Summary: AY installation without reboot: syslog service in failed state Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: joschibrauchle(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11 After performing an AY installation without a final reboot, the syslog service is in failed state: ---------- # rcsyslog status redirecting to systemctl syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: failed (Result: exit-code) since Fri, 23 Nov 2012 17:39:07 +0100; 40min ago Process: 15328 ExecStart=/sbin/rsyslogd -c 5 -f /etc/rsyslog.conf (code=exited, status=1/FAILURE) Process: 15326 ExecStartPre=/var/run/rsyslog/addsockets (code=exited, status=0/SUCCESS) Process: 15324 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) Main PID: 804 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/syslog.service ---------- but actually syslog (or rsyslogd in my installation) is running: ---------- #ps auxf|grep syslog root 2027 0.0 0.0 316764 1508 ? Sl 17:05 0:00 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf ---------- Possibly, syslog is started in the second installation stage by Autoyast, but after installation finished, systemd does not know about this? Starting a second instance via systemd fails, as only one instance is allowed... Reproducible: Always Steps to Reproduce: 1. Install 12.2 via AY and no final reboot 2. systemctl status syslog 3. Actual Results: syslog service failed, but rsyslogd running Expected Results: syslog service should be OK -- 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 22

[Bug 795492] New: pam-config throws away entries for unknown modules
by bugzilla_noreply＠novell.com 07 Jan '13

07 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=795492 https://bugzilla.novell.com/show_bug.cgi?id=795492#c0 Summary: pam-config throws away entries for unknown modules Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lnussel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- pam-config throws away manually added entries in common* for modules unknown to pam-config in /etc/pam.d so an admin can not add global custom modules. Would it be possible to make pam-config preserve such entries? -- 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 11