May 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 841573] New: gdm does not start up after installation
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=841573 https://bugzilla.novell.com/show_bug.cgi?id=841573#c0 Summary: gdm does not start up after installation Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed 13.1 beta 1 on a new machine (no update) from the NET media. (package selection: basically just default Gnome) After installation gdm/gnome didn't start. I just had an X mouse cursor without any gdm UI but just previous background. Interesting part of logging: Sep 20 19:59:25 ox.rosenauer.org gdm-launch-environment][1307]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (unknown)(uid=0) Sep 20 19:59:25 ox.rosenauer.org xdm[1274]: GLib: g_variant_new_string: assertion 'string != NULL' failed Sep 20 19:59:25 ox.rosenauer.org xdm[1274]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files Sep 20 19:59:25 ox.rosenauer.org gnome-session[1311]: gnome-session[1311]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is ge Sep 20 19:59:25 ox.rosenauer.org gnome-session[1311]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. With Dimstar's help on IRC we checked /etc/pam.d/common-session but there was no trace of pam_systemd: #%PAM-1.0 # # This file is autogenerated by pam-config. All changes # will be overwritten. # # Session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive # session required pam_limits.so session required pam_unix.so try_first_pass session optional pam_umask.so session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm session optional pam_env.so After running /usr/sbin/pam-config -a --systemd >/dev/null 2>&1 || : it created a new one: ox:/etc/pam.d # diff -wu common-session.pam-config-backup common-session --- common-session.pam-config-backup 2013-09-16 16:33:19.000000000 +0200 +++ common-session 2013-09-20 18:25:16.951741777 +0200 @@ -1,12 +1,18 @@ +#%PAM-1.0 # -# /etc/pam.d/common-session - session-related modules common to all services +# This file is autogenerated by pam-config. All changes +# will be overwritten. +# +# Session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and -# non-interactive). +# non-interactive # session required pam_limits.so session required pam_unix.so try_first_pass session optional pam_umask.so +session optional pam_systemd.so +session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm session optional pam_env.so Now gdm is starting up correctly and I can log in to Gnome -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 842093] New: systemd crash during zypper dup
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=842093 https://bugzilla.novell.com/show_bug.cgi?id=842093#c0 Summary: systemd crash during zypper dup Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: fcrozat(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- in the middle of a zypper dup from 12.3 to 13.1 Beta1 systemd left a core file in /. It was not possible to log into the system anymore. #0 0x00007f534149c8cb in raise () from /lib64/libpthread.so.0 #1 0x000000000040cbdb in crash (sig=6) at src/core/main.c:143 #2 <signal handler called> #3 0x00007f5341113849 in raise () from /lib64/libc.so.6 #4 0x00007f5341114cd8 in abort () from /lib64/libc.so.6 #5 0x00000000004652c3 in log_assert (text=text@entry=0x4c5e78 "a >= 0 && a < _JOB_TYPE_MAX_MERGING", file=file@entry=0x4c58f1 "src/core/job.c", line=line@entry=338, func=func@entry=0x4c63b0 <__PRETTY_FUNCTION__.12538> "job_type_lookup_merge", format=format@entry=0x4c08a0 "Assertion '%s' failed at %s:%u, function %s(). Aborting.") at src/shared/log.c:699 #6 0x0000000000465b60 in log_assert_failed (text=text@entry=0x4c5e78 "a >= 0 && a < _JOB_TYPE_MAX_MERGING", file=file@entry=0x4c58f1 "src/core/job.c", line=line@entry=338, func=func@entry=0x4c63b0 <__PRETTY_FUNCTION__.12538> "job_type_lookup_merge") at src/shared/log.c:704 #7 0x0000000000480976 in job_type_lookup_merge (a=a@entry=_JOB_TYPE_MAX_MERGING, b=<optimized out>) at src/core/job.c:338 #8 0x0000000000415003 in job_type_is_superset (b=<optimized out>, a=_JOB_TYPE_MAX_MERGING) at src/core/job.h:198 #9 transaction_is_destructive (e=0x7fff61431620, mode=JOB_REPLACE, tr=0x1f48d70) at src/core/transaction.c:509 #10 transaction_activate (tr=tr@entry=0x1f48d70, m=m@entry=0x1f0a620, mode=mode@entry=JOB_REPLACE, e=e@entry=0x7fff61431620) at src/core/transaction.c:714 #11 0x000000000040f1df in manager_add_job (m=0x1f0a620, type=_JOB_TYPE_MAX_MERGING, type@entry=_JOB_TYPE_MAX_IN_TRANSACTION, unit=unit@entry=0x2006860, mode=mode@entry=JOB_REPLACE, override=override@entry=true, e=e@entry=0x7fff61431620, _ret=_ret@entry=0x7fff61431640) at src/core/manager.c:980 #12 0x0000000000445031 in bus_unit_queue_job (connection=connection@entry=0x1fa9070, message=message@entry=0x1fe1dd0, u=0x2006860, type=type@entry=_JOB_TYPE_MAX_IN_TRANSACTION, mode=mode@entry=JOB_REPLACE, reload_if_possible=reload_if_possible@entry=false) at src/core/dbus-unit.c:796 #13 0x0000000000440a10 in bus_manager_message_handler (connection=0x1fa9070, message=message@entry=0x1fe1dd0, data=data@entry=0x1f0a620) at src/core/dbus-manager.c:1877 #14 0x00007f53416c8d66 in _dbus_object_tree_dispatch_and_unlock (tree=0x1f94af0, message=message@entry=0x1fe1dd0, found_object=found_object@entry=0x7fff614319b4) at dbus-object-tree.c:862 #15 0x00007f53416bb931 in dbus_connection_dispatch (connection=connection@entry=0x1fa9070) at dbus-connection.c:4693 #16 0x000000000043eeaa in bus_dispatch (m=m@entry=0x1f0a620) at src/core/dbus.c:525 #17 0x0000000000412f2f in manager_loop (m=0x1f0a620) at src/core/manager.c:1825 #18 0x000000000040ad54 in main (argc=<optimized out>, argv=0x7fff61432388) at src/core/main.c:1651 quit -- 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 803007] New: Network applet and apper stop working after upgrade from OpenSuse 12.2
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c0 Summary: Network applet and apper stop working after upgrade from OpenSuse 12.2 Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: ansgar.radermacher(a)cea.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Network applet and apper stopped working after upgrade from OpenSuse 12.2. In case of apper, I get a list of updates, but the installation is refused with a remark of insuffient rights. The network applet claims that the network manager is not running, although the latter is well running. I figured out that the problems are caused by console kit reporting (via ck-list-sessions)) that my session is not-local and not active. The error shows same symptoms as bug 790222. Since I needed my system back working quickly, I made a clean install instead of the previous upgrade and everything worked. I then realized that the console-kit is not used any more by default. I don't know why it was used on my 12.2 system (which -I think- was already an upgrade from 12.1), but it worked fine before. => the upgrade should check and eventually de-install console-kit (or properly reconfigure it) Reproducible: Always Steps to Reproduce: 1. Upgrade from 12.2 with user console kit for session authorization 2. try to user-defined open a network connection 3. Actual Results: claims network manager not running Expected Results: working connection (or at least a suitable error message indicating that insufficient rights cause this claim). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 809914] New: "zypper dup" looses activated services
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=809914 https://bugzilla.novell.com/show_bug.cgi?id=809914#c0 Summary: "zypper dup" looses activated services Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bugzilla(a)singvogel.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 Installing from openSUSE-12.1 to openSUSE-12.3 via "zypper dup" results in lost activated daemons. In openSUSE-12.1 were activated services, "chkconfig" said "on": atd, auditd, sshd In openSUSE-12.3 the same services are disabled, "chkconfig" said "off". Reproducible: Always This is a openSUSE-12.3 bugzillla entry, but selection of "openSUSE-12.3" is missing, so I choosed "SUSE Other". -- 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

[Bug 809916] New: systemd floods "/var/log/messages" when syslog-ng is used
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c0 Summary: systemd floods "/var/log/messages" when syslog-ng is used Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bugzilla(a)singvogel.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 When booting openSUSE-12.3 and having syslog-ng chosen, the systemd floods /var/log/messages when the same message: systemd[1]: syslog-ng.service start request repeated too quickly, refusing to start. This message is around 1100 times in /var/log/messages. This only happens when booting only. The syslog-ng daemon is running as expected after boot: 1x. The fault is the number of same messages in /var/log/messages. Reproducible: Always This is a openSUSE-12.3 bugzilla entry, but I cannot choose the 12.3 in selection field at the moment. -- 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 19

[Bug 811804] New: not all requested demons started at initialization
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=811804 https://bugzilla.novell.com/show_bug.cgi?id=811804#c0 Summary: not all requested demons started at initialization Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ulrich.deiters(a)uni-koeln.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=531904) --> (http://bugzilla.novell.com/attachment.cgi?id=531904) /var/log/boot.log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 When the system is booted, not all demons listed as /etc/init.d/rc5.d/S... are started. Example: ... S08alsasound S08avahi-daemon S08mcelog S08sshd S09ntp S10atd S10cups S10postfix S10xdm S11cron S11smartd After completing the boot sequence, ntp, xdm, and cron were running. Sshd, atd, and smartd were not. On some other machines, sshd came up, but not the apache server and the UPS handler. It is not clear to me why different machines behave differently. Reproducible: Always Steps to Reproduce: atd and smartd are most likely to be forgotten. Let us assume you want to run jobs in the background by means of "at": 1. Link atd script to rc5.d directory: cd /etc/init.d/rc5.d ln -s ../atd S10atd 2. Reboot 3. Check whether atd is running: ps -ef | grep atd Alternatively, try to submit a background job to "at". Actual Results: "ps -ef" did not list "atd" as running. Jobs could not be submitted to "at". Expected Results: after "ps -ef | grep atd": at 4553 1 0 Mär25 ? 00:00:00 /usr/sbin/atd operating system: openSUSE 12.3 THe problem has been observed with 12.1 and 12.2, too. The workaround is, evidently, to start the missing demons manually. That succeeded without any problems. But if it is the sshd demon that does not come up, and the machine is on another floor of the building, one has to walk over to the other place, and that can be a nuisance. -- 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 812256] New: rescue system (in text mode) fails to restart on Ctrl+Alt+Del
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=812256 https://bugzilla.novell.com/show_bug.cgi?id=812256#c0 Summary: rescue system (in text mode) fails to restart on Ctrl+Alt+Del Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=532453) --> (http://bugzilla.novell.com/attachment.cgi?id=532453) Screen Shot when system stopped doing anything User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 When I press Ctrl+Alt+Del in the rescue system, the system hangs after a few commands and never restarts (as expected). Reproducible: Didn't try Steps to Reproduce: 1. Boot Rescue system in text mode 2. Login, logout 3. Press Ctrl+Alt+Del Actual Results: System performs a few commands, the stops to do anything (see screen shot). Expected Results: system should reboot (as done for ages) -- 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 12

[Bug 845649] New: 70-persistent-net.rules is empty
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c0 Summary: 70-persistent-net.rules is empty Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: thomas.e.schreiner(a)t-online.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 the file /etc/udev/rules.d/70-persistent-net.rules is emtty. tes04:/etc/udev/rules.d # ll 70-persistent-net.rules -rw-r--r-- 1 root root 0 Oct 13 15:52 70-persistent-net.rules Reproducible: Always Steps to Reproduce: 1. New Installation of openSUSE 13.1 RC1 and reboot 2. ifconfig : netwok interface enp3s0f2 Link encap:Ethernet HWaddr 00:90:F5:E0:7B:D5 for netcard "03:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0a)" 3. Actual Results: We had the same Problem at the beginning with openSUSE 12.3. The problem has been fixed after a while by patch. Expected Results: without a working udev rules you are unable to control the numbering of your interfaces. -- 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 19

[Bug 858429] New: do not restart libvirt-guests during libvirt updates!
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=858429 https://bugzilla.novell.com/show_bug.cgi?id=858429#c0 Summary: do not restart libvirt-guests during libvirt updates! Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KVM AssignedTo: jfehlig(a)suse.com ReportedBy: mrueckert(a)suse.com QAContact: jdouglas(a)suse.com Found By: --- Blocker: --- Why are we restarting the libvirt guests during a libvirt update? the kvm/xen are in a different package so no files from libvirt should be affected by leaving those running. this broke me one of my virtualization hosts twice now. I kind of have the feeling this behavior is new in 13.1 and wasnt there on sles 11 sp3 could we please disable this behavior or is there a good reason to keep it? -- 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 848053] New: booting into runlevel 3 fails
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=848053 https://bugzilla.novell.com/show_bug.cgi?id=848053#c0 Summary: booting into runlevel 3 fails Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de CC: werner(a)suse.com Found By: Outsourced Testing Blocker: --- 13.1-rc2, build 00080, gnome desktop, root on primary, two data partitions on unencrypted lvm, 2 data partitions on encrypted lvm. I tried to boot into runlevel 3 by appending 3 to the kernel cmdline. The result was an unresponsive system. It was nearly impossible to enter the passphrase for the lvm volume. Keyboard input was not accepted, and if it was it was delayed by many seconds. Sometimes just one of the keystrokes was recognized. There was appearently no cpu bound activity, at least the fans remained silent. Once I managed to enter the passphrase the gnome desktop appeared just as I had booted without the 3 in /proc/cmdline. Did systemd break that established interface named "3" as well by any chance? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10