There is no beeps and no warning messages in syslog when rebooting PC
after software/security update (via "blue arrows" icon appearing on top
Gnome panel).
--
console-kit-daemon: glibgobject warning value location for gachararray passed
as null
https://bugs.launchpad.net/bugs/374397
You received
I don't have much knowledge in linux or programming but I think that Matthias
Clasen on bugzilla is right: should be an & before session_type. No matter will
it solve our problem or not.
See
http://library.gnome.org/devel/gobject/unstable/gobject-The-Base-Object-Type.html#g-object-get
This erro
Public bug reported:
Binary package hint: consolekit
Computer makes about 5 very fast beeps at shutdown.
The problem is similar to this:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397
Contents of syslog just before shutdown:
May 16 21:13:06 eugene-desk console-kit-daemon[2396]:
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/26849129/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/26849130/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/26849132/ProcStatus.txt
--
consol
** Summary changed:
- console-kit-daemon[2396]: GLib-GObject-WARNING: IA__g_object_get_valist:
value location for `gchararray' passed as NULL
+ console-kit-daemon: GLib-GObject-WARNING: IA__g_object_get_valist: value
location for 'gchararray' passed as NULL
** Description changed:
Binary pac
** Description changed:
Binary package hint: consolekit
Computer makes about 5 very fast beeps at shutdown/reboot (just before
leaving the desktop).
The problem is similar to this:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/374397
Contents of syslog just before shut
I have a similar bug on i386:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/377521
--
console-kit-daemon: glibgobject warning value location for gachararray passed
as null
https://bugs.launchpad.net/bugs/374397
You received this bug notification because you are a member of Ubuntu
Bug
Sorry, didn't visited launchpad. If my answer is of any use after this
time: I have the same version as you.
I guess this minor gnome update fixes this beeping.
ftp.gnome.org/pub/GNOME/desktop/2.26/2.26.3/NEWS mentions: "- Make
gnome-session exit properly on reboot/shutdown". And as Steven wrote -
Public bug reported:
When "Search for:" field in "Replace..." dialog contains more than 3 symbols
every press on "Find", "Replace" or "Replace all" buttons initiates write by
dconf-service.
Steps to reproduce:
a) I needed to change gedit's "max-recents" setting.
b) since there's no option for
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975510
Title:
Gedit initiates write by dconf-service when using "Replace..." dialog
To manage notifications about this bug go to:
https://bugs.launchpad
Yes of course gedit stores recent searches.
But what bugs me:
1) we enter some text into search field
2) we hit "find" or "replace" button
3) text we entered gets added to recent searches in dconf database
4) we see this:
kernel: [11053.994218] dconf-service(1656): dirtied inode 4194707 (user) on
to draco:
iotop doesn't show all io, though it detects it. For example: there's audible
write sound from HDD, iotop (running with -a) doesn't show any change for any
of processes but "TOTAL WRITE" field on it's top line quickly flickers with
something like 340K/s (you may need to lower update i
Same situation here.
Desktop. Xubuntu 11.10, 64bit, kernel 3.0.0-16-generic. Filesystem ext4.
jbd2 writes to disk every ~5sec when there is activity (like web
browsing), or every ~20-30sec when idle. Writes mostly in / partition,
but occasionally in /home.
--
You received this bug notification
Hello all.
Wanted to inform that there's fresh thread in Archlinux forums and associated
bug on bugzilla.kernel.org with some debugging instructions:
https://bbs.archlinux.org/viewtopic.php?id=139087 - Intense disk IO (jbd2 and
flush) blocks user interface
https://bugzilla.kernel.org/show_bug.cg
Hello.
I made some posts in https://bugzilla.kernel.org/show_bug.cgi?id=42895
and once again it was decided that jbd2 is not to blame. Read
explanation given by Jan Kara and Theodore Ts'o at the end.
Overall people from kernel.org have seen my "15 mins of idling"
block_dump (see attachment in pos
1. block_dump (see post 73). I should mention again that you may skip creating
tempfs dir altogether.
2. find (see post 73).
3. ftrace
FTRACE
Note: ftrace should be enabled on most more or less recent systems by default.
Overall usage:
ATTENTION: overall rule - after you have traced whatever you
16 matches
Mail list logo
