Reproduced on trusty (using just the test124 part of reproduction
instructions above):
Aug 22 13:08:23 gx1 sshd[11844]: pam_unix(sshd:session): session opened for
user test124 by (uid=0)
Aug 22 13:08:23 gx1 systemd-logind[1275]: New session 4 of user test124.
Aug 22 13:09:22 gx1 passwd[11988]:
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/890337
Title:
gvfs-gdu-volume-monitor high cpu usage during raid-resync
To manage notifications
** Attachment added: cpu usage does not drop after several hours of raid
resync, uses a lot of memory too
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+attachment/2609183/+files/after_resync_status.txt
** Visibility changed to: Public
--
You received this bug notification
Simply creating that file would not be entirely enough. As in while that
seems to force the fsck, said file does not get removed automatically.
And maybe even shouldn't be removed, unless it was created by gdu.
--
You received this bug notification because you are a member of Ubuntu
Desktop
http://bazaar.launchpad.net/~vcs-imports/gnome-disk-
utility/master/view/head:/src/gdu/gdu-linux-lvm2-volume-
group.c?start_revid=930 has the following comment in find_pvs():
187/* TODO: do incremental list management instead of recomputing on
188 * each add/remove/change event
Public bug reported:
After running palimpsest during a raid-resync cpu usage seemed high - in
fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an hour).
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gvfs 1.8.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-12.51-generic
** Attachment added: backtrace.txt
https://bugs.launchpad.net/bugs/889779/+attachment/2595320/+files/backtrace.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/889779
Title:
https://bugzilla.redhat.com/show_bug.cgi?id=575381 may be related.
** Bug watch added: Red Hat Bugzilla #575381
https://bugzilla.redhat.com/show_bug.cgi?id=575381
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
As passwd is setuid, setting environment variable of
G_DEBUG=fatal_criticals or G_DEBUG=fatal-warnings before running it does
not help.
DebuggingProcedures / DebuggingGNOME / DebuggingProgramCrash do not seem
to contain information on how to set the necessary environment for
setuid programs like
Public bug reported:
Binary package hint: gnome-settings-daemon
Got the following in .xsession_errors when printing to printer that was
offline at the time. Ubuntu theming disappeared as result, window
decorations reset to gnome defaults.
The program 'gnome-settings-daemon' received an X Window
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/765595
Title:
gnome-settings-daemon crashed on printing, BadMatch (invalid parameter
attributes)
--
desktop-bugs
Related part of .xsession_errors:
(firefox-bin:8554): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:8554): Gtk-WARNING **: Unknown paper size A4
(firefox-bin:8554): Gtk-WARNING **: Unknown paper size A4
(firefox-bin:8554): Gtk-WARNING **: Unknown paper size A4
Public bug reported:
Binary package hint: gnome-screensaver
After couple of the most recent updates, gnome-screensaver has stopped
recognizing any users as existing on the system and as such, refuses to
unlock. One attempt (+ killall gnome-screensaver from console) as seen
in auth.log below:
** Attachment added: /etc/pam.d/gnome-screensaver
https://bugs.launchpad.net/bugs/742321/+attachment/1939354/+files/gnome-screensaver
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
** Attachment added: /etc/pam.d/common-account
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/742321/+attachment/1939364/+files/common-account
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
** Attachment added: /etc/pam.d/common-auth
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/742321/+attachment/1939365/+files/common-auth
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
** Attachment added: /etc/pam.d/common-password
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/742321/+attachment/1939366/+files/common-password
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver
** Attachment added: /etc/pam.d/common-session
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/742321/+attachment/1939371/+files/common-session
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in
** Attachment added: /etc/pam.d/common-session-noninteractive
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/742321/+attachment/1939372/+files/common-session-noninteractive
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Could you attach /etc/default/rcS and /etc/timezone please?
P.S. next DST change is going to happen soon.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/553928
Title:
LP:#742321 (on Maverick) may be related.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/515155
Title:
unlocking screensaver hangs when ecryptfs is unmounted
--
desktop-bugs mailing list
gp11-module.c has only two instances of g_return_val_if_fail
(data-funcs, NULL); of which only one is in gp11_module_get_slots(), at
line 843 for 2.92.92.is.2.30.3-0ubuntu1.1.
I think DebuggingProgramCrash does not apply here as such, since
g_return_if_fail does not really abort the program, it
Looks wrong:
-rw-r- 1 rootroot 1276 2011-03-25 01:16 shadow
Fixed by chgrp:ing it back to shadow. Guess this one is user error, or
possibly an issue with etckeeper instead of gnome-screensaver.
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Invalid
--
You
Public bug reported:
Binary package hint: gnome-keyring
Changing password remotely results in the following assertion failures
in auth.log:
Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password changed
for test123
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
https://bugs.launchpad.net/bugs/738063
Title:
gnome-keyring-daemon assertion failures when changing password
remotely
--
desktop-bugs mailing list
$ egrep -v '^#|^$' /etc/pam.d/common-password
passwordrequisite pam_cracklib.so retry=3
minlen=8 difok=3
password[success=1 default=ignore] pam_unix.so obscure use_authtok
try_first_pass sha512
passwordrequisite
26 matches
Mail list logo
