August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 931762] New: yast2 kdump: segfault
by bugzilla_noreply＠novell.com 06 Feb '17

06 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=931762 Bug ID: 931762 Summary: yast2 kdump: segfault Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mpluskal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 634953 --> http://bugzilla.opensuse.org/attachment.cgi?id=634953&action=edit backtrace: coredumpctl gdb 354 I am not sure if related to boo#931291 Program terminated with signal SIGSEGV, Segmentation fault. #0 QMapNode<QWidget*, QList<QWidget*> >::copy (this=0x7fc4441b9a60, d=d@entry=0x3e0b1b0) at /usr/include/qt5/QtCore/qbasicatomic.h:110 110 /usr/include/qt5/QtCore/qbasicatomic.h: No such file or directory. (gdb) bt #0 QMapNode<QWidget*, QList<QWidget*> >::copy (this=0x7fc4441b9a60, d=d@entry=0x3e0b1b0) at /usr/include/qt5/QtCore/qbasicatomic.h:110 #1 0x00007fc4520a8f56 in detach_helper (this=0x7fc4440694c8) at /usr/include/qt5/QtCore/qmap.h:955 #2 detach (this=0x7fc4440694c8) at /usr/include/qt5/QtCore/qmap.h:364 #3 remove (akey=<synthetic pointer>, this=0x7fc4440694c8) at /usr/include/qt5/QtCore/qmap.h:892 #4 QY2Styler::unregisterWidget (this=0x7fc4440694b0, widget=widget@entry=0x7fc4440bcd70) at /usr/src/debug/libyui-qt-2.46.18/src/QY2Styler.cc:197 #5 0x00007fc4520bd82a in YQDialog::~YQDialog (this=0x7fc4440c3520, __in_chrg=<optimized out>) at /usr/src/debug/libyui-qt-2.46.18/src/YQDialog.cc:144 #6 0x00007fc4520bd859 in YQDialog::~YQDialog (this=0x7fc4440c3520, __in_chrg=<optimized out>) at /usr/src/debug/libyui-qt-2.46.18/src/YQDialog.cc:147 #7 0x00007fc45b390d5e in YDialog::deleteAllDialogs () at /usr/src/debug/libyui-3.1.5/src/YDialog.cc:566 #8 0x00007fc45b366ac9 in YUI::~YUI (this=0x410aaf0, __in_chrg=<optimized out>) at /usr/src/debug/libyui-3.1.5/src/YUI.cc:99 #9 0x00007fc4520e4dd9 in YQUI::~YQUI (this=0x410aaf0, __in_chrg=<optimized out>) at /usr/src/debug/libyui-qt-2.46.18/src/YQUI.cc:354 #10 0x00007fc45b5ee353 in YUIComponent::result (this=<optimized out>) at YUIComponent.cc:251 #11 0x00007fc45e5bde79 in main (argc=<optimized out>, argv=<optimized out>) at genericfrontend.cc:773 #12 0x00007fc45c90b8c5 in __libc_start_main (main=0x4006c0 <main@plt>, argc=3, argv=0x7ffdca246888, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdca246878) at libc-start.c:289 #13 0x00000000004006f9 in _start () at ../sysdeps/x86_64/start.S:118 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 854323] New: libpgf OpenMP digikam memory leak when thumbnailing and face recognition - fix available in pgf SVN
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

https://bugzilla.novell.com/show_bug.cgi?id=854323 https://bugzilla.novell.com/show_bug.cgi?id=854323#c0 Summary: libpgf OpenMP digikam memory leak when thumbnailing and face recognition - fix available in pgf SVN Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: rickscafe.casablanca(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The version of libpgf that is shipped with 13.1 produces a massive memory leak with digikam. This happens when initially thumbnailing a larger picture collection or when trying face recognition on a collection. In both cases digikam will eat up all RAM plus swap. At least part of the problem is libpgf and it was fixed in SVN, though has not been released yet. See http://sourceforge.net/p/libpgf/code/HEAD/tree/ *** trunk 2013-11-08 rs [r123] fix memory leak in Encoder w/ OpenMP *** I compiled r123 which identifies as 6.13.45 and it does indeed fix the memory leak with digikam. The fix should be included in a libpgf update to 13.1 RH Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1023241 KDE Bug: https://bugs.kde.org/show_bug.cgi?id=326525 Reproducible: Always Steps to Reproduce: 1. backup digikam collection db and start from scratch 2. initial scan/tumbnailing uses all available RAM 3. face recognition uses all available RAM Actual Results: system runs out of memory or gets very slow due to digikam eating all RAM Expected Results: memory usage should be stable -- 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 937652] New: nbd shutdown crash
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=937652 Bug ID: 937652 Summary: nbd shutdown crash Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: cbosdonnat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 640583 --> http://bugzilla.suse.com/attachment.cgi?id=640583&action=edit test script triggering the problem When shutting down a libvirt-lxc container with an NBD mounts, we sometimes get a crash. Steps to reproduce: * Get libvirt, and virt-sandbox from the Virtualization project * Install guestfs-tools * systemctl start libvirtd * Run the attached test script. The QEMU tests can be commented in it as those aren't the ones triggering the bug. Note that the crash may not happen at each run of the script, don't hesitate to run it several times if needed. What happens: * the 'sandbox' container isn't correctly terminated due to the qemu-nbd segfaulting. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 908499] New: systemd: Many stale rfkill services accumulates after suspend/resume cycles
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908499 Bug ID: 908499 Summary: systemd: Many stale rfkill services accumulates after suspend/resume cycles Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See http://lists.freedesktop.org/archives/systemd-devel/2014-November/025321.ht… for details. For systems where rfkill devices are connected via USB they get new names after each suspend/resume causing large number of stale services to be accumulated (and defeating the purpose of rfkill.service to store device state). This apparently was fixed in upstream 4844262f25a3ff6bd23de05a0a6f84a8e2983d74 + 812bd1e6ab4c463507557f2bdbb8875fedd92ade. Please consider including it in systemd update (fix is very much self contained and should be non-intrusive). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 932362] New: D-Bus prints warning due to faulty NetworkManager config file
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=932362 Bug ID: 932362 Summary: D-Bus prints warning due to faulty NetworkManager config file Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thiago(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time the system dbus-daemon reloads its configuration, it prints the following warning to syslog: dbus-daemon[1147]: Unknown username "srvGeoClue" in message bus configuration file That is caused by https://build.opensuse.org/package/view_file/openSUSE:Factory/NetworkManage… added in commit https://build.opensuse.org/request/show/223859. The warning happens when you don't have geoclue installed. The patch is a big hammer for a problem that should be fixed in GeoClue's side. Please move any required D-Bus rules to its package, to be installed if and only if GeoClue itself is installed. It would also be nice to work with upstream to make sure that they're not making calls they shouldn't be making. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 902612] New: systemd automounts manually umounted devices again
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902612 Bug ID: 902612 Summary: systemd automounts manually umounted devices again Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sweet_f_a(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just noticed that systemd automatically mounts devices again allthough I've manually umounted them. Here is what I did $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) ## umount and disable that lvm device $ umount /mnt/local $ lvchange -an vg0/local systemd[1]: Stopping File System Check on /dev/vg0/local... systemd[1]: Stopped File System Check on /dev/vg0/local. ## enable device again $ lvchange -ay vg0/local systemd[1]: Found device /dev/mapper/vg0-local. systemd[1]: Found device /dev/disk/by-uuid/177a415d-174d-4c30-8897-5502c0419ef8. systemd[1]: Found device /dev/disk/by-id/dm-uuid-LVM-uF33oY4c9yu00EPAP42a8A2XZCfQTRRPGfiv0cNZRwPKIRJnOboscsc1z60174dd. systemd[1]: Found device /dev/disk/by-id/dm-name-vg0-local. systemd[1]: Found device /dev/dm-0. systemd[1]: Found device /sys/devices/virtual/block/dm-0. systemd[1]: Starting File System Check on /dev/vg0/local... systemd-fsck[6386]: /dev/mapper/vg0-local: clean, 648240/3276800 files, 9308645/13107200 blocks systemd[1]: Started File System Check on /dev/vg0/local. systemd[1]: Mounting /mnt/local... kernel: [ 5542.579700] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr systemd[1]: Mounted /mnt/local. $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) So what kind of automount is this? How to disable this odd behaviour? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 907715] New: Predictable iSCSI device links are not being created any more in /dev/disks/by-path
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907715 Bug ID: 907715 Summary: Predictable iSCSI device links are not being created any more in /dev/disks/by-path Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f+novell(a)congenio.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When an iSCSI target is connected, its corresponding device link under /dev/disk/by-path/ip-<IP_ADDR>:<PORT>-iscsi-<IQN>-iscsi-lun-<LUN#>-part<PART#> is not being created any more. This is extremely limiting, because the real scsi device (say, /dev/sdg1) is quite unpredictable. The reason for this is a patch in upstream systemd: http://cgit.freedesktop.org/systemd/systemd/commit/?id=e98bbfd2074e2b1079b7… Lee Duncan of SuSE Labs has pointed that one out to upstream maintainers (http://lists.freedesktop.org/archives/systemd-devel/2014-October/024155.html) but the bug is still in openSUSE 13.2. Fedora had that one fixed as well (see https://bugzilla.redhat.com/show_bug.cgi?id=1161779) In order to fix this, this patch should be applied: Index: systemd-210/src/udev/udev-builtin-path_id.c =================================================================== --- systemd-210.orig/src/udev/udev-builtin-path_id.c +++ systemd-210/src/udev/udev-builtin-path_id.c @@ -547,6 +547,7 @@ } else if (streq(subsys, "scsi")) { parent = handle_scsi(parent, &path); supported_transport = true; + supported_parent = true; } else if (streq(subsys, "cciss")) { parent = handle_cciss(parent, &path); supported_transport = true; -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 917221] New: Unable to resume after long hibernation
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=917221 Bug ID: 917221 Summary: Unable to resume after long hibernation Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: wguy4biz(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 622691 --> http://bugzilla.opensuse.org/attachment.cgi?id=622691&action=edit pm-suspend.log, sections of journal and Xorg.0.log for failed hibernation/thaw When i suspend to disk and resume, resume sometimes works and sometimes does not. The determining factor appears to be the amount of time that is between the completion of the suspend and when it is resumed. If i try to resume immediately after suspend, the resume is always successful; if the resume is a couple of hours after the suspend completes (not clear exactly how long is required), the resume fails. Prior to upgrading to SuSE 13.2, i was able to successfully hibernate/resume on this machine many times after long suspensions, even suspensions of days. I am less certain of how well this worked on 13.1, because i did not use the machine much when it had SuSE 13.1 on it, but it worked extremely well for many months with SuSE 12.3. The differences between 13.2 and previous releases is that i put in 2 new hard drives and did a fresh install onto a RAID1 configuration using BTRFS, whereas previously it had been an ext4 boot drive, no RAID. I am using GRUB2 with MBR for the boot loader. The pm-suspend log shows the final stages of hibernation being executed, but there does not appear to be any thaw steps executed. When the thaw is performed, i see some variation of video output; sometimes i see a very faint image of the background shown when booting from shutdown, sometimes that same image flashes briefly at full strength and others there is no apprent video, but there is a signal (my monitor detects no signal and reports this). The machine does not show up on my router's network map, so the network does not appear to be active after the thaw. I have attached a file with segments, or entire file contents of the following: - pm-suspend.log for failed hibernate/thaw (entire file) - journal entries for failed hibernate/thaw - journal entries for successful hibernate/thaw - Xorg.0.log showing both successful and unsuccessful hibernate/thaw (entire file) -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 908798] New: systemd re-adds itself to pam-config with every update
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908798 Bug ID: 908798 Summary: systemd re-adds itself to pam-config with every update Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got rid of the useless pam_systemd by running "pam-config --delete --systemd". (See http://seifesrants.blogspot.de/2014/11/pamsystemd-on-server-wtf.html) However, today I found that it magically reappeared and is spamming my system logs for no good reason. Checking, I noticed that systemd was updated lately. Looking into the postinstall stuff, I found the following "gem": postinstall scriptlet (using /bin/sh): /usr/sbin/pam-config -a --systemd || : /sbin/ldconfig [...] This unconditional adding is not really a good idea IMNSHO, if it is done at all, it should only be done at initial install of systemd. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 908567] New: init 3, kdm and X does not stop
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908567 Bug ID: 908567 Summary: init 3, kdm and X does not stop Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sweet_f_a(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Somehow my X was chrashed (running at 100% CPU). That's why I issued "init 3". Firstly I noticed that "init 3" took about 2 minutes to finish, which I find odd. After runlevel change X and kdm is still running. Another try gives me $ rckdm stop redirecting to systemctl stop rcxdm.service Failed to issue method call: Unit rcxdm.service not loaded. BTW what is the right systemctl command to stop kdm? Don't see any rcxdm.service... This is the log of "init 3" 2014-12-05T12:35:30.309597+01:00 bart systemd[1]: Stopping Daemon for power management... 2014-12-05T12:35:30.310007+01:00 bart systemd[1]: Stopping Disk Manager... 2014-12-05T12:35:30.310316+01:00 bart systemd[1]: Stopping Authorization Manager... 2014-12-05T12:35:30.310604+01:00 bart systemd[1]: Stopping User Manager for 1001... 2014-12-05T12:35:30.310891+01:00 bart systemd[1]: Stopping Execution Queue Daemon... 2014-12-05T12:35:30.311222+01:00 bart systemd[1]: Stopping User Manager for 1102... 2014-12-05T12:35:30.311514+01:00 bart systemd[1]: Stopping user-1000.slice. 2014-12-05T12:35:30.311800+01:00 bart systemd[1]: Removed slice user-1000.slice. 2014-12-05T12:35:30.314391+01:00 bart systemd[1]: Stopping user-1006.slice. 2014-12-05T12:35:30.314872+01:00 bart systemd[1]: Removed slice user-1006.slice. 2014-12-05T12:35:30.315258+01:00 bart systemd[1]: Stopping user-0.slice. 2014-12-05T12:35:30.315648+01:00 bart systemd[1]: Removed slice user-0.slice. 2014-12-05T12:35:30.315993+01:00 bart systemd[1]: Stopping LVM2 metadata daemon... 2014-12-05T12:35:30.316437+01:00 bart systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup. 2014-12-05T12:35:30.316795+01:00 bart systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup. 2014-12-05T12:35:30.317139+01:00 bart systemd[1]: Stopping Cleanup of Temporary Directories... 2014-12-05T12:35:30.317513+01:00 bart systemd[1]: Stopping Graphical Interface. 2014-12-05T12:35:30.317850+01:00 bart systemd[1]: Stopped target Graphical Interface. 2014-12-05T12:35:30.318206+01:00 bart systemd[1]: Stopping LSB: X Display Manager... 2014-12-05T12:35:30.527111+01:00 bart systemd[1]: Started Purge old kernels. 2014-12-05T12:35:30.527509+01:00 bart systemd[1]: Started Manage Sound Card State (restore and store). 2014-12-05T12:35:30.527847+01:00 bart systemd[1]: Starting Restore Sound Card State... 2014-12-05T12:35:30.610220+01:00 bart systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... 2014-12-05T12:35:30.610647+01:00 bart systemd[1]: Mounted Configuration File System. 2014-12-05T12:35:30.610954+01:00 bart systemd[1]: Starting Show Plymouth Boot Screen... 2014-12-05T12:35:30.611266+01:00 bart systemd[1]: Mounted FUSE Control File System. 2014-12-05T12:35:30.611607+01:00 bart systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... 2014-12-05T12:35:31.879886+01:00 bart systemd[19793]: Stopping Default. 2014-12-05T12:35:32.124898+01:00 bart systemd[19793]: Stopped target Default. 2014-12-05T12:35:32.125265+01:00 bart systemd[19793]: Starting Shutdown. 2014-12-05T12:35:32.125617+01:00 bart systemd[19793]: Reached target Shutdown. 2014-12-05T12:35:32.125951+01:00 bart systemd[19793]: Starting Exit the Session... 2014-12-05T12:35:32.126294+01:00 bart systemd[1]: Stopped LVM2 metadata daemon. 2014-12-05T12:35:32.126618+01:00 bart systemd[1]: Stopped Execution Queue Daemon. 2014-12-05T12:35:32.126940+01:00 bart systemd[1]: Stopped Authorization Manager. 2014-12-05T12:35:32.129139+01:00 bart systemd[1]: Stopped Disk Manager. 2014-12-05T12:35:32.129564+01:00 bart systemd[1]: Stopped Daemon for power management. 2014-12-05T12:35:32.129951+01:00 bart systemd[1]: Started Tell Plymouth To Write Out Runtime Data. 2014-12-05T12:35:32.130346+01:00 bart systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. 2014-12-05T12:35:32.697776+01:00 bart systemd[19575]: Stopping Default. 2014-12-05T12:35:32.698270+01:00 bart systemd[19575]: Stopped target Default. 2014-12-05T12:35:32.717529+01:00 bart systemd[19575]: Starting Shutdown. 2014-12-05T12:35:32.717997+01:00 bart systemd[19575]: Reached target Shutdown. 2014-12-05T12:35:32.718387+01:00 bart systemd[19575]: Starting Exit the Session... 2014-12-05T12:35:35.062984+01:00 bart systemd[1]: Stopped User Manager for 1001. 2014-12-05T12:35:35.063411+01:00 bart systemd[1]: Stopping user-1001.slice. 2014-12-05T12:35:35.063717+01:00 bart systemd[1]: Removed slice user-1001.slice. 2014-12-05T12:35:35.734627+01:00 bart systemd[1]: Stopped User Manager for 1102. 2014-12-05T12:35:35.735046+01:00 bart systemd[1]: Stopping user-1102.slice. 2014-12-05T12:35:35.735400+01:00 bart systemd[1]: Removed slice user-1102.slice. 2014-12-05T12:35:43.478476+01:00 bart kdm: :0[17392]: pam_unix(xdm:session): session closed for user wiesing 2014-12-05T12:35:47.420488+01:00 bart xdm[21427]: Shutting down service kdm..done 2014-12-05T12:35:47.422104+01:00 bart systemd[1]: Stopped LSB: X Display Manager. 2014-12-05T12:36:02.082804+01:00 bart /usr/sbin/cron[24007]: pam_unix(crond:session): session opened for user freundt by (uid=0) 2014-12-05T12:36:06.015422+01:00 bart systemd[1]: Stopped Cleanup of Temporary Directories. 2014-12-05T12:36:06.015851+01:00 bart systemd[1]: Stopping Replay Read-Ahead Data... 2014-12-05T12:36:06.016165+01:00 bart systemd[1]: Stopped Replay Read-Ahead Data. 2014-12-05T12:36:06.016456+01:00 bart systemd[1]: Starting File System Quota Check... 2014-12-05T12:36:06.376098+01:00 bart systemd[1]: Started Set Up Additional Binary Formats. 2014-12-05T12:36:06.376513+01:00 bart systemd[1]: Started File System Check on Root Device. 2014-12-05T12:36:06.376828+01:00 bart systemd[1]: Started File System Quota Check. 2014-12-05T12:36:06.379674+01:00 bart systemd[1]: Starting Enable File System Quotas... 2014-12-05T12:36:06.854571+01:00 bart systemd[1]: Stopped User Manager for 1102. 2014-12-05T12:36:06.855940+01:00 bart systemd[1]: Removed slice user-1102.slice. 2014-12-05T12:36:06.897699+01:00 bart systemd[1]: Started Restore Sound Card State. 2014-12-05T12:36:06.902554+01:00 bart systemd[1]: Starting user-1006.slice. 2014-12-05T12:36:06.902936+01:00 bart systemd[1]: Created slice user-1006.slice. 2014-12-05T12:36:06.903247+01:00 bart systemd[1]: Starting Session 121762 of user freundt. 2014-12-05T12:36:06.903550+01:00 bart systemd[1]: Started Session 121762 of user freundt. 2014-12-05T12:36:07.610356+01:00 bart /USR/SBIN/CRON[24007]: pam_unix(crond:session): session closed for user freundt 2014-12-05T12:36:18.354363+01:00 bart quotaon[24562]: quotaon: using /mnt/tmpdirs/aquota.group on /dev/mapper/vg0-tmpdirs [/mnt/tmpdirs]: Device or resource busy 2014-12-05T12:36:22.120689+01:00 bart quotaon[24562]: quotaon: using /mnt/tmpdirs/aquota.user on /dev/mapper/vg0-tmpdirs [/mnt/tmpdirs]: Device or resource busy 2014-12-05T12:36:22.121061+01:00 bart systemd[1]: quotaon.service: main process exited, code=exited, status=2/INVALIDARGUMENT 2014-12-05T12:36:22.121439+01:00 bart systemd[1]: Failed to start Enable File System Quotas. 2014-12-05T12:36:22.121792+01:00 bart systemd[1]: Unit quotaon.service entered failed state. 2014-12-05T12:36:36.446772+01:00 bart sudo: rudi : TTY=pts/17 ; PWD=/home/rudi ; USER=root ; COMMAND=/usr/bin/su 2014-12-05T12:36:36.447238+01:00 bart sudo: pam_unix(sudo:session): session opened for user root by rudi(uid=0) 2014-12-05T12:36:36.447977+01:00 bart sudo: pam_systemd(sudo:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR 2014-12-05T12:36:36.491023+01:00 bart su: (to root) rudi on none 2014-12-05T12:36:36.494087+01:00 bart su: pam_unix(su:session): session opened for user root by rudi(uid=0) 2014-12-05T12:36:36.494459+01:00 bart su: pam_systemd(su:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR 2014-12-05T12:37:01.618555+01:00 bart /usr/sbin/cron[29439]: pam_unix(crond:session): session opened for user freundt by (uid=0) 2014-12-05T12:37:01.623809+01:00 bart systemd[1]: Starting Session 121763 of user freundt. 2014-12-05T12:37:01.624823+01:00 bart systemd[1]: Started Session 121763 of user freundt. 2014-12-05T12:37:02.092316+01:00 bart /USR/SBIN/CRON[29439]: pam_unix(crond:session): session closed for user freundt 2014-12-05T12:37:06.818431+01:00 bart systemd[1]: Started Show Plymouth Boot Screen. 2014-12-05T12:37:06.819204+01:00 bart systemd[1]: Started Dispatch Password Requests to Console Directory Watch. 2014-12-05T12:37:06.821258+01:00 bart systemd[1]: Starting Wait for Plymouth Boot Screen to Quit... 2014-12-05T12:37:06.821596+01:00 bart systemd[1]: Starting Terminate Plymouth Boot Screen... 2014-12-05T12:37:06.847800+01:00 bart systemd[1]: Started Wait for Plymouth Boot Screen to Quit. 2014-12-05T12:37:06.848209+01:00 bart systemd[1]: Started Terminate Plymouth Boot Screen. 2014-12-05T12:37:06.848528+01:00 bart systemd[1]: Reached target Multi-User System. 2014-12-05T12:37:06.848831+01:00 bart systemd[1]: Starting Update UTMP about System Runlevel Changes... 2014-12-05T12:37:07.330171+01:00 bart systemd[1]: Started Update UTMP about System Runlevel Changes. -- You are receiving this mail because: You are on the CC list for the bug.

1 2