[Bug 587228] Re: Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
I usually have the same problem; after entering 'continue' at gdb's prompt, I can recreate the bug but then not ctrl+c back out to gdb's prompt. I tried it again just now and, although I was unable this time to recreate the 100% CPU bug for some unknown reason, once I added and removed a new keyboard layout twice I got an error from g-s-d and obtained a backtrace (attached). Like I said, I'm not sure if this particular backtrace applies to the bug in question, but it did occur after following the same steps which usually recreate the bug. ** Attachment added: gdb-gnome-settings-daemon.txt http://launchpadlibrarian.net/49562738/gdb-gnome-settings-daemon.txt -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 587228] Re: Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
I've struggled to get a backtrace as gdb hangs when using it against a running gnome-settings-daemon PID (not even responding to Ctrl+C), but when killing all running gnome-settings-daemon processes and then starting gdb with a new gnome-settings-daemon process, I got the following results: GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/gnome-settings-daemon...(no debugging symbols found)...done. (gdb) handle SIG33 pass nostop noprint SignalStop Print Pass to program Description SIG33 NoNo Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/bin/gnome-settings-daemon [Thread debugging using libthread_db enabled] ** At this point, I added a new keyboard layout to the Keyboard Preferences dialogue and the CPU usage went up to 100% until I removed the new layout. I then executed 'killall gnome-settings-daemon' from a terminal. Program exited normally. (gdb) backtrace full No stack. (gdb) info registers The program has no registers now. (gdb) ** At this point, after realising that gdb didn't seem to have picked anything up, I added a new keyboard layout again in the Keyboard Preferences dialogue. The CPU usage went up to 100% and the following two lines were output from gdb: (gnome-settings-daemon:25101): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width 0' failed (gnome-settings-daemon:25101): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** After this I attempted to use Ctrl+C to kill the process inside gdb, but at this point gdb hung and I was unable to continue debugging. I hope the above two lines are of some use. Please inform me of how I might be able to generate a proper stack trace if not. -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 587228] Re: Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
To clarify, the 'Program exited normally' as soon as it had run and re- drawn the window settings correctly. So I'm not sure even if gdb was picking up the action of me adding a new keyboard layout mentioned in my first comment, above. But as I said, every time I try to kill the running gnome-settings- daemon from within gdb, gdb hangs making it impossible to proceed any further in generating a backtrace. -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 587228] Re: Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49309692/Dependencies.txt -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 587228] [NEW] Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
Public bug reported: Binary package hint: gnome-settings-daemon Using Lucid, when adding an additional keyboard layout (various layouts tested), the indicator panel draws the keyboard indicator icon, and gnome-settings-daemon instantly starts using 100% CPU and continues to do so forever. When the second keyboard layout is removed, gnome- settings-daemon's CPU usage drops back to normal. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-settings-daemon 2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-386 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-386 i686 Architecture: i386 Date: Sat May 29 13:32:39 2010 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU https://bugs.launchpad.net/bugs/587228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 311731] Re: gimp save a copy tooltip help confusing
Ok, I accept your comment, but the help text is still confusing and ambiguous in my opinion. -- gimp save a copy tooltip help confusing https://bugs.launchpad.net/bugs/311731 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 311731] [NEW] gimp save a copy tooltip help confusing
Public bug reported: Binary package hint: gimp In gimp 2.6 (and earlier versions) the tooltip help for Save a Copy on the File menu is confusing: Save this image with a different name, but keep its current name. I would suggest that this could be changed to read something like Save this image in the same folder, but with a different name. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- gimp save a copy tooltip help confusing https://bugs.launchpad.net/bugs/311731 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 152123] Re: sound preview doesn't stop when using the mouse wheel
Additionally, another instantiation of this bug occurs when the mouse is hovered over a media file which is already selected, and then deleted whilst the preview is playing. To recreate: select a music or other sound file by clicking once. Hover the mouse over the file until the preview begins to play. Now delete the media file by pressing 'Delete' on the keyboard, without moving the mouse. What should happen: The file is moved to Trash, and the preview should end. What actually happens: The file is moved to Trash, but the preview still continues from the 'phantom' file. -- sound preview doesn't stop when using the mouse wheel https://bugs.launchpad.net/bugs/152123 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 78661] Re: Black themes/High Contrast Inverse theme Bugs
If you look at the comments on http://www.gnome-
look.org/content/show.php/Neutronium+Unity?content=59189 you will notice
the following solution to the above problem, which I can confirm works
for me with Ubuntu 8.04, Firefox 3b5, and the Neutronium Unity dark
theme. It involves editing
~/.mozilla/firefox/profile/chrome/userContent.css :
In order to work porperly with FF3 use this userContent.css instead of
the provided one (I added -moz-appearance: none !important;):
input {
border: 2px inset white;
background-color: white;
color: black;
-moz-appearance: none !important;
}
textarea {
border: 2px inset white;
background-color: white;
color: black;
-moz-appearance: none !important;
}
select {
border: 2px inset white;
background-color: white;
color: black;
-moz-appearance: none !important;
}
input[type=radio],
input[type=checkbox] {
border: 2px inset white ! important;
background-color: white ! important;
color: ThreeDFace ! important;
-moz-appearance: none !important;
}
*|*::-moz-radio {
background-color: white;
-moz-appearance: none !important;
}
button,
input[type=reset],
input[type=button],
input[type=submit] {
border: 2px outset white;
background-color: #ee;
color: black;
-moz-appearance: none !important;
}
body {
background-color: white;
color: black;
display: block;
margin: 8px;
-moz-appearance: none !important;
}
--
Black themes/High Contrast Inverse theme Bugs
https://bugs.launchpad.net/bugs/78661
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
