** Also affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
--
Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
https://bugs.launchpad.net/bugs/328575
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Bug watch added: Debian Bug tracker #531734
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531734
** Changed in: debian
Importance: Undecided => Unknown
** Changed in: debian
Status: New => Unknown
** Changed in: debian
Remote watch: None => Debian Bug tracker #531734
--
Can
Here's a patch that cherry-picks an upstream commit to fix this problem
for Jaunty.
** Attachment added: "gnome-terminal_2.26.0-0ubuntu2.1.debdiff"
http://launchpadlibrarian.net/30671489/gnome-terminal_2.26.0-0ubuntu2.1.debdiff
--
Cannot start gnome-terminal (or x-terminal-emulator) because
** Summary changed:
- Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
+ [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator)
because of gconf error
** Description changed:
+ Binary package hint: gnome-terminal
+
+ IMPACT: gnome-terminal will fai
** Changed in: debian
Status: Unknown => Fix Released
--
[gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator)
because of gconf error
https://bugs.launchpad.net/bugs/328575
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a b
gnome-settings-daemon listens for drm udev events to trigger automatic
layout updates. As it turns out, upower's current definition for "is
this machine docked" is "does this machine have more than one output
connected", and it...also listens for udev events - specifically from
drm, not dock device
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.la
I've seen a similar bug on Jaunty (in my case, printing multiple copies
of a document with duplexing enabled would do various incorrect things),
but I've been unable to reproduce it or this bug on Karmic.
Alex - are you still having this issue on Karmic?
--
Printing duplex in reverse order does
** Changed in: gnome-settings-daemon
Importance: Undecided => Unknown
** Changed in: gnome-settings-daemon
Status: New => Unknown
** Changed in: gnome-settings-daemon
Remote watch: None => GNOME Bug Tracker #670116
--
You received this bug notification because you are a member of Ubu
It looks like GDM still hard-codes the ~/.xsession-errors path (see
GDM_SESSION_DEFAULT_PATH in daemon/gdm-session-worker.c).
There is, of course, a slightly different problem. As of gdm 2.80, it
seems that GDM no longer displays a popup if your login session lasts
less than 10 seconds. "Now we ha
Public bug reported:
The overrides in pygobject for Gdk use the Gdk.atom_intern function,
which was not correctly exported in GDK 2.0, which causes the import to
fail:
evan@caron:~$ python
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/875399
Title:
Can not explicitly import Gdk-2.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Verified from oneiric-proposed - I can explicitly import both Gdk-2.0
and Gdk-3.0
evan@caron:~$ python
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi
>>> gi.require_version('Gdk', '2.0')
>>>
** Also affects: vinagre (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oneiric-backports
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vinagre in Ubuntu.
https://bugs.launchpad.net
By default, GNOME runs with 4 virtual workspaces. For your first bug, I
suspect that the windows you are "losing" are actually on a different
virtual workspace. Try pressing Ctrl-Alt-Right arrow and see if your
windows are there. Your window manager is responsible for reconfiguring
windows when the
I'm unsubscribing ubuntu-sponsors from this bug. Merge-proposals
requesting a review from ubuntu-sponsors or ubuntu-branches (the
default) automatically show up in our queue for sponsorship.
Additionally subscribing ubuntu-sponsors creates an extra entry, so it
should only be used when attaching a
*** This bug is a duplicate of bug 853973 ***
https://bugs.launchpad.net/bugs/853973
** This bug has been marked a duplicate of bug 853973
package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package
*** This bug is a duplicate of bug 853973 ***
https://bugs.launchpad.net/bugs/853973
** This bug has been marked a duplicate of bug 853973
package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package
*** This bug is a duplicate of bug 853973 ***
https://bugs.launchpad.net/bugs/853973
** This bug has been marked a duplicate of bug 853973
package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package
*** This bug is a duplicate of bug 853973 ***
https://bugs.launchpad.net/bugs/853973
** This bug has been marked a duplicate of bug 853973
package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package
*** This bug is a duplicate of bug 853973 ***
https://bugs.launchpad.net/bugs/853973
** This bug has been marked a duplicate of bug 853973
package libgucharmap7 1:3.0.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libgucharmap_2_90.so.7.0.0', which is also in package
Closing the dapper-backports task due to Ubuntu 6.06 (Dapper Drake) no
longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 6.06 (Dapper Drake) are no longer being accepted.
This bug was fixed with 3.2.1-1
** Changed in: libgweather (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/629646
Title:
Locatio
Debdiff for Lucid SRU attached. (Will be updating the bug description
shortly)
** Patch added: "libgweather_2.30.0-0ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/629646/+attachment/2610674/+files/libgweather_2.30.0-0ubuntu1.1.debdiff
--
You received this bug n
Debdiff for Maverick SRU attached.
** Patch added: "libgweather_2.30.3-0ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/629646/+attachment/2610675/+files/libgweather_2.30.3-0ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubun
Debdiff for Natty SRU
** Patch added: "libgweather_2.30.3-1ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/629646/+attachment/2610676/+files/libgweather_2.30.3-1ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
Debdiff for Oneiric SRU
** Patch added: "libgweather_3.2.0-0ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/629646/+attachment/2610677/+files/libgweather_3.2.0-0ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
** Description changed:
+ [Impact]
+ libgweather is unable to parse the HTML data previously returned from the
Australian Bureau of Meteorology
+
+ [Development Fix]
+ Fix committed upstream as a80552f51c641754ef8410eebea6debc23a25561,
73829e640d2ebd7f926563145ca81702c17d0abb. Picked up in 3.2.
** Description changed:
[Impact]
libgweather is unable to parse the HTML data previously returned from the
Australian Bureau of Meteorology
[Development Fix]
Fix committed upstream as a80552f51c641754ef8410eebea6debc23a25561,
73829e640d2ebd7f926563145ca81702c17d0abb. Picked up in 3.2.
Thanks for tracking this down, guys.
I'm going to close the lxappearance task as "Invalid" since the issue
seems to have been tracked down to GTK.
(In particular, this should cause it to show up as a GTK patch on the
sponsorship queue, which hopefully means the right people will see it)
** Chang
** Changed in: libgnome (Ubuntu)
Importance: Undecided => Medium
--
gnome-open uses firefox while it's not the preferred browser
https://bugs.launchpad.net/bugs/670128
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgnome in ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Medium
** Changed in: xdg-utils (Ubuntu)
Importance: Undecided => Medium
--
gnome-open uses firefox while it's not the preferred browser
https://bugs.launchpad.net/bugs/670128
You received this bug notification because y
** Changed in: evince (Ubuntu)
Status: Triaged => Incomplete
** Changed in: gtk+2.0 (Ubuntu)
Status: Triaged => Incomplete
--
Printing duplex in reverse order does not work from many applications
https://bugs.launchpad.net/bugs/370591
You received this bug notification because you
Oliver, I'm a bit confused. As I understand it, the bug described here
was the result of switching gconf to use gdbus, and that change was only
introduced in Maverick. If I am understanding this correctly, then you
could not be experiencing this particular bug on Lucid, even if you're
experiencing
So based on some digging, I don't think the issue here is actually the
one described, at least not immediately.
Booting with "single" in /proc/cmdline causes the system to emit the
runlevel S event (read "switch to runlevel S" if you don't feel like
thinking Upstart-y). When the user exits out of
Of course, once something does actually trigger the gdm job to run (with
the exception of doing "start gdm" directly), that will still trigger
command-line inhibition code originally described in this bug, so we
would still need to do something about that.
--
You received this bug notification be
36 matches
Mail list logo
