** Bug watch added: GNOME Bug Tracker #585160
http://bugzilla.gnome.org/show_bug.cgi?id=585160
** Changed in: fileroller
Importance: Undecided => Unknown
** Changed in: fileroller
Status: New => Unknown
** Changed in: fileroller
Remote watch: None => GNOME Bug Tracker #585160
--
Output of gnome-settings-daemon --no-daemon --debug attached.
** Attachment added: "debug.log"
http://launchpadlibrarian.net/27713499/debug.log
** Attachment removed: "debug.log"
http://launchpadlibrarian.net/27713499/debug.log
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NUL
** Attachment added: "gsd-debug.log"
http://launchpadlibrarian.net/27713572/gsd-debug.log
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/384439
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Removing that file doesn't change a thing here. Attaching a strace of
g-s-d until the messages appear (no crash here, so no bt).
gnome-settings-daemon:
Installed: 2.27.1-0ubuntu1
Candidate: 2.27.1-0ubuntu1
** Attachment added: "strace-gsd.log"
http://launchpadlibrarian.net/27712548/strace-
Finally got a stacktrace (some debugging symbols seem to be missing,
don't know which ones).
** Attachment added: "btfull-gsd.log"
http://launchpadlibrarian.net/27727670/btfull-gsd.log
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/38443
Franciscovega's bug seems unrelated and happens earlier than the error
message in this bug. Also there is no segmentation fault. Xrandr plugin
just causes above mentioned errors.
Looking at the strace output right before the messages...
[pid 4818] 01:06:07.208872 access("/home/test/.config/monit
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/640807/+attachment/1595316/+files/Dependencies.txt
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
Public bug reported:
Binary package hint: gnome-settings-daemon
Starting with version 2.31.91-0ubuntu2, my CRT monitor starts with a
refresh rate of 60 Hz (overriding the 75 Hz set in xorg.conf). Using
nvidia-settings to manually set it back to 75 Hz works, but after
restarting gnome-settings-dae
** Description changed:
Binary package hint: gnome-settings-daemon
- Starting with version 2.31.91-0ubuntu2, my CRT monitor starts with a
+ Starting with version 2.31.91-0ubuntu1, my CRT monitor starts with a
refresh rate of 60 Hz (overriding the 75 Hz set in xorg.conf). Using
nvidia-sett
Ok, so this seems to have been triggered by the change in defaults in
version 2.31.91-0ubuntu3 (turn on ext. monitors).
Setting
'apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup'
to false for the user gdm made this bug go away in the current version.
That key has been introdu
A signature is bound to an account, so why not add its definition to the
account setup process and prepopulate it with "Sent from Ubuntu",
similar like the hostname is prepopulated during the Ubuntu
installation?
--
Evolution adds 'Sent from Ubuntu' signature by default
https://bugs.launchpad.net
I forgot, you also need to disable this option for the user ('sudo -u
gdm' will only deal with the gdm login screen):
gconftool-2 --type bool -s
"/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup"
false
I guess the easiest way to find out if you are affected by this bug is,
Nothing new in the log. I too think that g-s-d isn't the problem but
rather triggering the behavior.
Thing is, without a xorg.conf I only can chose between low/safe
resolutions. With Nvidia's BLOB it's enough to add horizontal and
vertical refresh rates, with Nouveau I also need to provide a model
Feel free to rename the bug title as it doesn't seem to fit anymore. :-)
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
Sure, because "Datei System" would be an orthographic mistake
("Deppenleerzeichen"). ;-)
--
Inconsistent spelling of "Filesystem" (vs. "File system")
https://bugs.launchpad.net/bugs/297793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Changed in: brasero (Ubuntu)
Status: New => Confirmed
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs mailing l
This only seems to happen if the source files are on an NTFS parition
and you copy more than one file (see updated description).
** Description changed:
I just copied a couple of GiB around and noticed that the progress bar
on the Nautilus launcher item wasn't working. It looks like the progr
It also works with FAT32 partitions. I just copied two CD images from a
flash drive onto a second Oneiric system and it showed the same
behavior.
** Description changed:
I just copied a couple of GiB around and noticed that the progress bar
on the Nautilus launcher item wasn't working. It loo
Oh dear, I'm sorry, but it does NOT seem to be dependent on the
filesystem... I now also created an EXT4 partition on the flash drive
and on both Oneiric systems the issue occurs. The only time when the
progress bar seems to work, is when I copy files from the root partition
to the root partition (
Unfortunately it's no fully fixed, as I now cannot see any progress bar
at all (in the bad case, the good case works like before). However that
fixes at least the bad visual experience.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to n
This is not yet fixed. While the graphical glitch is gone (I admit, the
more important part here), there are still some cases where the progress
bar doesn't show any progress at all whereas the Nautilus file copy
dialog works just fine.
** Changed in: nautilus (Ubuntu)
Status: Fix Released
After some more testing: the progress bar seems to fail whenever the
copy process total file size is >= 2147483648 bytes.
** Description changed:
- I just copied a couple of GiB around and noticed that the progress bar
- on the Nautilus launcher item wasn't working. It looks like the progress
-
Public bug reported:
The progress bar seems to fail showing progress whenever the total file
size limit of the copy process is larger or equal than 2147483648 bytes
(= 2 GiB).
TEST CASE:
1. Create a bad dummy file:
dd if=/dev/zero of=dummy.fail bs=1073741824 count=2
2. Create a working dum
Setting status back to fixed on request.
** Changed in: nautilus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/841609
Title:
Progress
I'm still seeing the BT messages but the audio output works reliably (I
didn't remove any BT related packages).
espeak:
Installed: 1.43-0ubuntu1
Candidate: 1.43-0ubuntu1
Version table:
*** 1.43-0ubuntu1 0
500 http://archive.ubuntu.com lucid/main Packages
100 /var/lib/dpkg/st
Err, sorry about #16. :-)
--
Light 1px border around desktop
https://bugs.launchpad.net/bugs/507263
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Yes, it's still an issue on my two testing systems (also confirmed with
a current daily live CD). I don't have any custom gnome-terminal
keybindings and the value of '/apps/gnome-
terminal/keybindings/save_contents' is 'disabled'.
--
Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry !=
Over eight months after "Great progress is being made on this" - any
news on this?
--
nautilus 'replace file' dialog box could give more information
https://bugs.launchpad.net/bugs/136702
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Although I don't see a segmentation fault, I do get mentioned warning
twice every gnome-appearance-properties start.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
https://bugs.launchpad.net/bugs/51836
gdk_display_sync is called four times until the dialog pops up, first
and last call causing the warnings. Attaching backtraces and full
backtraces of all calls.
** Attachment added: "gdb's 'bt' output for all four calls"
http://launchpadlibrarian.net/41228816/gdb_bt_g-c-c.log
--
gdk_display_s
** Attachment added: "gdb's 'bt full' output for all four calls"
http://launchpadlibrarian.net/41228824/gdb_bt_full_g-c-c.log
--
gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
https://bugs.launchpad.net/bugs/518368
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: metacity
If I try to drag a window that overlays a previously maximized window,
the maximized window will be picked instead.
This happens with nvidia-current (not with Nouveau), 'Appearance
Preferences > Visual Effects' set to 'None', and only if the oth
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41900759/Dependencies.txt
--
Drags the wrong window
https://bugs.launchpad.net/bugs/546583
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
Seems this bug is already known (via
https://bugzilla.redhat.com/show_bug.cgi?id=533066):
* https://bugzilla.gnome.org/show_bug.cgi?id=608296 - includes the commit that
might be responsible (tested and fixes this bug)
* https://bugzilla.gnome.org/show_bug.cgi?id=608144 - dupe of above
* https://b
Updated the description: it does happen with Nouveau - I made a mistake
during testing. If this is a Metacity bug it will affect all video
drivers anyways.
** Description changed:
Binary package hint: metacity
If I try to drag a window that overlays a previously maximized window,
the max
Seems fixed for me (no messages while not having any monitor
configuration files in ~/.config). Are you sure it's coming from the
xrandr-plugin (g-s-d --debug might help)?
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/384439
You received th
I'm seeing this too. Starting gnome-settings-daemon with '--no-daemon
--debug' I get:
...
** (gnome-settings-daemon:10629): DEBUG: Loading
/usr/lib/gnome-settings-daemon-2.0/libmedia-keys.so
** (gnome-settings-daemon:10629): DEBUG: Registering GsdMediaKeysPlugin
** (gnome-settings-daemon:10629):
Public bug reported:
Binary package hint: gnome-power-manager
Seeing this warning in ~/.xsession-errors and when manually starting
gnome-power-manager.
ProblemType: Bug
Architecture: i386
Date: Tue Feb 23 11:50:15 2010
DevkitPower: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu
** Attachment added: "g-p-m-verbose.log"
http://launchpadlibrarian.net/39602471/g-p-m-verbose.log
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39602472/Dependencies.txt
** Attachment added: "GConfNonDefault.txt"
http://launchpadlibrarian.net/39602473/GConfNonDef
** Attachment added: "valgrind_g-p-m.log"
http://launchpadlibrarian.net/39602495/valgrind_g-p-m.log
--
GLib-GObject-WARNING **: IA__g_object_new_valist: object class
`GsdOsdNotification' has no property named
`Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c'
https://bugs.launchpad.net/bugs/52
Public bug reported:
Binary package hint: gnome-terminal
I'm getting this message upon starting gnome-terminal (starting
additional terminals doesn't cause it).
ProblemType: Bug
Architecture: i386
Date: Tue Feb 23 14:06:26 2010
DistroRelease: Ubuntu 10.04
Package: gnome-terminal 2.29.6-0ubuntu1
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39609413/Dependencies.txt
--
Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL &&
entry->lock_count > 0' failed
https://bugs.launchpad.net/bugs/526437
You received this bug notification because you are a
** Attachment added: "gdb_bt_gnome-terminal.log"
http://launchpadlibrarian.net/39609428/gdb_bt_gnome-terminal.log
--
Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL &&
entry->lock_count > 0' failed
https://bugs.launchpad.net/bugs/526437
You received this bug notification
** Attachment added: "gdb_btfull_gnome-terminal.log"
http://launchpadlibrarian.net/39609438/gdb_btfull_gnome-terminal.log
--
Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL &&
entry->lock_count > 0' failed
https://bugs.launchpad.net/bugs/526437
You received this bug noti
** Changed in: gnome-menus (Ubuntu)
Status: New => Confirmed
--
"system" pulldown empty
https://bugs.launchpad.net/bugs/491937
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in ubuntu.
--
desktop-bugs mailing list
de
Public bug reported:
Binary package hint: nautilus
When creating or renaming objects on the desktop, a light, 1px wide
border appears around the desktop (panels and maximized windows do
overlap). The border only disappears when killing the process
'nautilus'.
Screenshot: http://img.xrmb2.net/ima
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37865668/Dependencies.txt
** Attachment added: "usr_lib_nautilus.txt"
http://launchpadlibrarian.net/37865669/usr_lib_nautilus.txt
--
Light 1px border around desktop
https://bugs.launchpad.net/bugs/507263
You received th
** Description changed:
Binary package hint: nautilus
When creating or renaming objects on the desktop, a light, 1px wide
border appears around the desktop (panels and maximized windows do
overlap). The border only disappears when killing the process
'nautilus'.
- Screenshot: http:
Sorry, a bad habit.
** Attachment added: "837162.png"
http://launchpadlibrarian.net/37931074/837162.png
** Description changed:
Binary package hint: nautilus
When creating or renaming objects on the desktop, a light, 1px wide
border appears around the desktop (panels and maximized wi
I'm only seeing this, when X starts in low graphics (fail-safe) mode.
ck-list-sessions:
Session1:
unix-user = '1000'
realname = 'test'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ':1'
x11-display-device = '/dev/tty9'
Also prevents auto-mounting: "Unable to mount 2.0 GB Filesystem Not
Authorized"
--
Inactive buttons Shutdown and Restart
https://bugs.launchpad.net/bugs/508379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing li
I too can't reproduce it anymore and ck-list-sessions now shows 'active
= TRUE'.
--
Inactive buttons Shutdown and Restart
https://bugs.launchpad.net/bugs/508379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing l
To reproduce, just reinstall one of the xfonts-packages like xfonts-base
or xfonts-dpi100. All currently open terminals will change their colors.
This will also trigger bug #507263 (
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/507263 ).
--
During updates the terminal changes color
htt
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
non consistant filesystem spelling in GNOME
https://bugs.launchpad.net/bugs/297793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
d
** Bug watch added: GNOME Bug Tracker #585690
http://bugzilla.gnome.org/show_bug.cgi?id=585690
** Also affects: gstreamer via
http://bugzilla.gnome.org/show_bug.cgi?id=585690
Importance: Unknown
Status: Unknown
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' faile
Public bug reported:
~/.xsession-errors is filled with following error message:
Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom !=
None' failed
According to this package's changelog this should already be fixed
(upstream bug 580511: http://bugzilla.gnome.org/show_bug.cgi?id=
With 2.17.2-0ubuntu2 this bug seems really fixed.
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Fix Released
--
gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
https://bugs.launchpad.net/bugs/387912
You received this bug notification because you are a member of Ubuntu
If you decide not to call it "File System"/"Filesystem" you may want to
change it in the filebrowser (or file browser ;)) plugin in Gedit too
(plugins/filebrowser/gedit-file-bookmarks-store.c, end of function
init_special_directories).
--
Inconsistent spelling of "Filesystem" (vs. "File system")
@17
What about another gconf-key? There already are keys like 'gmt_time' and
'format' that don't confuse users by not being present in the preferences
dialog.
--
Drop-down calendar does not close unless you click on it
https://bugs.launchpad.net/bugs/387573
You received this bug notification be
For me it was fusion-icon, which I had in the startup applications list.
Disabling it fixed the problem. Manually starting it brought it back.
--
Process gconfd-2 causes cpu overuse and overheat
https://bugs.launchpad.net/bugs/390733
You received this bug notification because you are a member of
Sorry for spamming but I was too quick with blaming fusion-icon. In my
case it is a problem between metacity and compiz like described in this
bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/389686
--
Process gconfd-2 causes cpu overuse and overheat
https://bugs.launchpad.net/bugs/39
I can confirm this using a Nvidia 6600 GT with Nvidia 185.18.14 drivers.
*) Starting compiz via fusion-icon in the startup applications causes
100% CPU load. Killing either compiz.real or metacity reduces CPU load
back to normal.
*) Starting compiz manually after session start with 'compiz --repl
Ok, this gconfd-2 thing seems to be the result of 'compiz --replace'
starting a loop that triggers this bug:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/150721
Addition to above points:
*) Starting compiz via setting 'Visual Effects' to 'Normal' in
'Appearance Preferences' (and removi
Public bug reported:
Binary package hint: gdm
Opposed to KDM and XDM, GDM doesn't update the file /etc/X11/default-
display-manager (or creates it if missing), so I have to manually change
(or create) it to contain:
/usr/sbin/gdm
Also there is no configuration dialog when installing it along wi
Public bug reported:
Binary package hint: gdm
GDM installs a file /etc/gdm/custom.conf which apparently does not do
what its filename suggests: configure GDM.
Instead GDM seems to use the file /etc/gdm/gdm.conf-custom for
configuration.
gdm 2.26.1-0ubuntu2
** Affects: gdm (Ubuntu)
Importa
Are you sure you didn't delete the gdm.conf-custom file manually?
I cannot confirm this bug:
*) Purged GDM 2.26 (including all GDM related files a file search returned)
*) Installed GDM 2.20.10-0ubuntu5, /etc/gdm contained the (empty)
gdm.conf-custom
*) Used gdmsetup to enable autologin, gdm.con
After reading the documentation
(http://library.gnome.org/admin/gdm/stable/configuration.html.en) it's
in fact custom.conf that should be used to config GDM. I suggest
renaming the bug to something like "gdm 2.26 wrong configuration file
used".
--
gdm 2.26 custom configuration file: wrong filenam
Issue #1: Upgrading from 2.20 to 2.26 leaves you with two configuration
files. Pretty confusing I'd say - especially because you have to
manually configure GDM since there is no graphical tool (yet?) to do it.
Issue #2: Fresh installations just install 'custom.conf', which isn't
used (yet?) by GDM
This is no longer an issue.
** Changed in: gnome-panel (Ubuntu)
Status: Confirmed => Fix Released
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363298
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
This is no longer an issue.
** Changed in: update-notifier (Ubuntu)
Status: New => Fix Released
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363349
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-pan
Public bug reported:
Binary package hint: gdm
When the autologin-user tries to log out he automatically gets logged in
again. So you cannot log out user A and log in with user B (switching
users works, though).
GDM 2.20 always showed the login screen after logging out the autologin-
user.
gdm 2
Downloaded the above linked file (4.2GB). When opening the containing
folder (icon view, preview enabled) and clicking on the file, nautilus
is gone: 100% CPU (actually 50% of my core duo system), ~1GB RAM usage,
unresponsive. I've waited half an hour before killing it.
Attaching gdb output while
** Bug watch added: GNOME Bug Tracker #588446
http://bugzilla.gnome.org/show_bug.cgi?id=588446
** Also affects: nautilus via
http://bugzilla.gnome.org/show_bug.cgi?id=588446
Importance: Unknown
Status: Unknown
--
nautilus becomes non-responsive during video-playback
https://bugs.
Public bug reported:
Binary package hint: gnome-panel
Gnome-panel, nm-applet, and update-notifier put messages prefixed with
"DEBUG" in the .xsession-errors file. As those aren't errors or
warnings, I ask you to remove them for the release. There's already
enough noise in this file.
Example:
**
I see. Should I report this for the other two applications too?
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363298
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@lis
Perfectly clear now. I reported them w/o touching the nominate feature.
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/363349
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/363350
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363298
*** This bug is a duplicate of bug 363349 ***
https://bugs.launchpad.net/bugs/363349
** This bug has been marked a duplicate of bug 363349
Debug messages in .xsession-errors
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363298
You received this bug notification bec
** This bug is no longer a duplicate of bug 363349
Debug messages in .xsession-errors
--
Debug messages in .xsession-errors
https://bugs.launchpad.net/bugs/363298
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mail
Wasn't me. Marking them as invalid and removing the duplicate status of
the other bugs (which again will spam I guess - sorry about that).
** Changed in: network-manager-applet (Ubuntu)
Status: New => Invalid
** Changed in: gnome-panel (Ubuntu)
Status: New => Invalid
--
Debug mess
** Changed in: file-roller (Ubuntu)
Status: Incomplete => New
--
Opening file-roller causes a warning in ~/.xsession-errors
https://bugs.launchpad.net/bugs/328903
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
file-roller:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Still there.
--
Opening file-roller causes a warning in ~/.xsession-errors
https://bugs.launchpad.net/bugs/328903
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
Public bug reported:
Binary package hint: file-roller
Whenever I open file-roller following entries show up in ~/.xsession-
errors
Window manager warning: meta_window_activate called by a pager with a 0
timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACT
Doesn't seem to happen, when I double-click a compressed file but
happens when opening it via "gnome-open file" or "file-roller file".
--
Opening file-roller causes a warning in ~/.xsession-errors
https://bugs.launchpad.net/bugs/328903
You received this bug notification because you are a member o
Sorry for the missing info:
file-roller:
Installed: 2.25.90-0ubuntu1
Candidate: 2.25.90-0ubuntu1
Version table:
*** 2.25.90-0ubuntu1 0
500 http://archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
I think you meant file-roller and not gedit?
A. Opening a com
Public bug reported:
Binary package hint: gnome-control-center
In gnome-keybinding-properties I have three disabled keybindings under "Custom
Shortcuts":
1. "binding" - Disabled starts gconftool-2 --toggle
/desktop/gnome/applications/at/screen_magnifier_enabled
2. "binding" - Disabled starts gc
Here too using vesa (my nvidia GPU is half dead, nv and nvidia won't
work).
--
gdmgreeter crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/331292
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
-
Vesa (with Nvidia G73M).
--
gdmgreeter crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/331324
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists
Fixed. Thanks!
--
gdmgreeter crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/331324
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.co
Reproducible with today's live CD.
1. Open System > Preferences > Keyboard Shortcuts.
2. Under "Custom Shortcuts" there are three disabled shortcuts (just called
"binding").
3. Change the command of one of the three entries, close "Keyboard Shortcuts",
reopen.
4. The initial command will be ther
Seems to be two issues:
1. Every custom shortcut that's disabled will fail to parse as valid
binding in gsd-keybindings-manager.c and therefor throw this warning (to
reproduce add a shortcut, restart GDM, look in ~/.xsession-errors).
2. The command of a custom shortcut can't be changed - it's not
How can I get rid of gnome-system-log in gconf? Uninstalling (and
purging) gnome-utils didn't fix it.
I think you just need to check the existence of default_logfiles[i] in
logview_prefs_fill_defaults (I did it with fopen - maybe overkill?) but
as long as I have the gconf entry present it's not cr
Public bug reported:
Binary package hint: gvfs
The names for the root partition in Nautilus' Places panel and main
panel (Computer view) differ.
Screenshot: http://img.xrmb2.net/images/242451.png
Not sure this is gvfs related, though.
gvfs:
Installed: 1.0.2-0ubuntu1
Candidate: 1.0.2-0ubunt
Public bug reported:
Binary package hint: gnome-panel
In Hardy I was using the compact upstream dialogs for shut down and logout:
http://img297.imageshack.us/img297/1803/bildschirmfotognomepanekk5.png
I enabled them by creating the gconf key upstream_session in
apps/panel/global and setting it t
I finally fixed it. I had not only to remove --purge gnome-panel but
also to delete everything "gnome-panel" related I could find with gnome-
search-tool.
I'll do an hardy install tomorrow and see if I can reproduce this
problem.
--
New logout/shut down dialogs not showing after upgrade from Har
All-clear. I could not reproduce the described situation on the same
laptop via a Hardy => Intrepid upgrade.
** Changed in: gnome-panel (Ubuntu)
Status: New => Invalid
--
New logout/shut down dialogs not showing after upgrade from Hardy
https://bugs.launchpad.net/bugs/282199
You received
** Changed in: gnome-panel (Ubuntu)
Status: New => Confirmed
--
alt f2 not working when panel background color set to "solid color"
https://bugs.launchpad.net/bugs/398826
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
gdm 2.27.4 floods daemon.log
https://bugs.launchpad.net/bugs/403723
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@
The error is caused by the patch 100_load_desired_settings.patch by
adding:
/* return NULL if the file doesn't exist */
if (!g_file_test (filename, G_FILE_TEST_EXISTS))
{
result = NULL;
return result;
}
to the function configurations_read_from_file() in libgnome-desktop
/gnome-rr
Public bug reported:
Binary package hint: gnome-settings-daemon
When the option disable-while-typing is enabled, you currently have to
wait 0.5 seconds after the last key press before the touchpad gets
enabled. In my opinion that's an user preference that should be
configurable at least via gconf
Noted for the next time.
--
Disable touchpad while typing: make time configurable via gconf-key
https://bugs.launchpad.net/bugs/409086
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.ubu
1 - 100 of 232 matches
Mail list logo
