| 2009-02-12 15:34:39 |
Pete Goodall |
bug |
|
|
added bug |
| 2009-02-19 12:01:11 |
Chris Crisafulli |
None: bugtargetdisplayname |
Ubuntu |
gconf2 (Ubuntu) |
|
| 2009-02-19 12:01:11 |
Chris Crisafulli |
None: bugtargetname |
ubuntu |
gconf2 (Ubuntu) |
|
| 2009-02-19 12:01:11 |
Chris Crisafulli |
None: statusexplanation |
|
|
|
| 2009-02-19 12:01:11 |
Chris Crisafulli |
None: title |
Bug #328575 in Ubuntu: "Cannot start gnome-terminal bcause of gconf error" |
Bug #328575 in gconf2 (Ubuntu): "Cannot start gnome-terminal bcause of gconf error" |
|
| 2009-02-19 12:30:32 |
Pedro Villavicencio |
gconf2: status |
New |
Incomplete |
|
| 2009-02-19 12:30:32 |
Pedro Villavicencio |
gconf2: assignee |
|
desktop-bugs |
|
| 2009-02-19 12:30:32 |
Pedro Villavicencio |
gconf2: importance |
Undecided |
Low |
|
| 2009-02-19 12:30:32 |
Pedro Villavicencio |
gconf2: statusexplanation |
|
is this still an issue? could you attach your ~/.xsession-errors file to the report? do you get the same with another new user created on your system? thanks you. |
|
| 2009-02-19 18:18:45 |
Ubuntuxer |
bug |
|
|
added attachment '.xsession-errors' (.xsession-errors) |
| 2009-03-23 03:00:23 |
Andreas Moog |
gconf2 (Ubuntu): status |
Incomplete |
Triaged |
|
| 2009-03-23 03:00:50 |
Andreas Moog |
bug |
|
|
assigned to gconf |
| 2009-03-23 03:06:30 |
Bug Watch Updater |
gconf: status |
Unknown |
New |
|
| 2009-03-23 14:39:42 |
Andreas Moog |
bug watch added |
|
http://bugzilla.gnome.org/show_bug.cgi?id=555745 |
|
| 2009-03-23 14:39:42 |
Andreas Moog |
gconf: status |
New |
Unknown |
|
| 2009-03-23 14:56:16 |
Bug Watch Updater |
gconf: status |
Unknown |
New |
|
| 2009-04-09 04:59:49 |
Luigi |
removed subscriber Luigi |
|
|
|
| 2009-04-25 22:31:39 |
Maxim Levitsky |
summary |
Cannot start gnome-terminal bcause of gconf error |
Cannot start gnome-terminal because of gconf error |
|
| 2009-04-26 12:12:49 |
Andreas Moog |
bug watch added |
|
https://bugs.freedesktop.org/show_bug.cgi?id=17970 |
|
| 2009-04-26 12:12:49 |
Andreas Moog |
bug task added |
|
dbus |
|
| 2009-04-26 13:03:53 |
Bug Watch Updater |
dbus: status |
Unknown |
In Progress |
|
| 2009-04-26 16:50:48 |
Adam Russ |
removed subscriber Adam Russ |
|
|
|
| 2009-04-26 21:16:43 |
Andreas Moog |
removed subscriber Andreas Moog |
|
|
|
| 2009-04-29 13:18:58 |
Chris Coulson |
tags |
|
regression-release |
|
| 2009-05-08 20:01:57 |
Gabriel Alcivar |
removed subscriber Gabriel Alcivar |
|
|
|
| 2009-05-09 16:17:34 |
Andreas Moog |
removed subscriber Andreas Moog |
|
|
|
| 2009-05-09 16:18:55 |
Andreas Moog |
removed subscriber Andreas Moog |
|
|
|
| 2009-05-10 04:47:50 |
William Ono |
removed subscriber William Ono |
|
|
|
| 2009-05-10 19:14:40 |
gerjantd |
removed subscriber gerjantd |
|
|
|
| 2009-05-12 03:14:28 |
Peter Cordes |
description |
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ gnome-terminal
Failed to contact the GConf daemon; exiting.
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb. |
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ sudo gnome-terminal
Failed to contact the GConf daemon; exiting.
(original report didn't have sudo in this command, but a later comment by the submitter amended this.)
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb.
This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered.
summary of some stuff posted in comments:
gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings.
gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user.
executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar).
Workarounds:
for the gconfd-not-running case:
start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.)
multiple tabs over ssh:
use screen(1)
$ sudo aptitude install screen screen-profiles # if you don't have it already
The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them "windows"). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not.
If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.)
You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab.
root shells:
use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo on the one or two commands that need it. e.g.
$ ls
$ less foo.conf
$ sudo editor foo.conf
(or gksudo editor foo.conf, if your editor of choice is opens it's own window instead of running inside the terminal)
$ ls ..
$ sudo mv foo bar
$ sudo # error permission denied
$ echo 10 | sudo tee /proc/sys/vm/swappiness # sudo tee is a way to accomplish echo 10 > file with the file-open happening as root.
Root is dangerous: a typo could break things much more easily than without sudo. The fewer things running as root, the better. It's not usually necessary to run a terminal emulator as root, just things that use that terminal. Even when you're doing a sysadmin thing, you probably run lots of info-gathering commands that don't need root. Save sudo for the commands that need it.
This bug is partly that gconf requires DBUS, which breaks some remote-GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part.
Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...)
I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies.
|
|
| 2009-05-13 00:39:26 |
Peter Cordes |
description |
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ sudo gnome-terminal
Failed to contact the GConf daemon; exiting.
(original report didn't have sudo in this command, but a later comment by the submitter amended this.)
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb.
This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered.
summary of some stuff posted in comments:
gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings.
gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user.
executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar).
Workarounds:
for the gconfd-not-running case:
start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.)
multiple tabs over ssh:
use screen(1)
$ sudo aptitude install screen screen-profiles # if you don't have it already
The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them "windows"). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not.
If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.)
You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab.
root shells:
use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo on the one or two commands that need it. e.g.
$ ls
$ less foo.conf
$ sudo editor foo.conf
(or gksudo editor foo.conf, if your editor of choice is opens it's own window instead of running inside the terminal)
$ ls ..
$ sudo mv foo bar
$ sudo # error permission denied
$ echo 10 | sudo tee /proc/sys/vm/swappiness # sudo tee is a way to accomplish echo 10 > file with the file-open happening as root.
Root is dangerous: a typo could break things much more easily than without sudo. The fewer things running as root, the better. It's not usually necessary to run a terminal emulator as root, just things that use that terminal. Even when you're doing a sysadmin thing, you probably run lots of info-gathering commands that don't need root. Save sudo for the commands that need it.
This bug is partly that gconf requires DBUS, which breaks some remote-GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part.
Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...)
I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies.
|
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ sudo gnome-terminal
Failed to contact the GConf daemon; exiting.
(original report didn't have sudo in this command, but a later comment by the submitter amended this.)
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb.
This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered.
summary of some stuff posted in comments:
gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings.
gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user.
executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar).
Workarounds to use until the bugs are fixed:
for the gconfd-not-running case:
start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.)
multiple tabs over ssh:
use screen(1)
$ sudo aptitude install screen screen-profiles # if you don't have it already
The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them "windows"). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not.
If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.)
You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab.
root shells:
You can use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo or gksudo on the one or two commands that need it.
This bug is partly that gconf requires DBUS, which breaks some remote-GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part.
Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...)
I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies.
|
|
| 2009-05-14 12:20:39 |
Paolo Benvenuto |
removed subscriber Paolo Benvenuto |
|
|
|
| 2009-06-13 17:07:42 |
franik4ever |
bug task added |
|
debian |
|
| 2009-06-13 22:18:26 |
NilsR |
removed subscriber NilsR |
|
|
|
| 2009-07-17 16:20:26 |
Kevin O'Gorman |
summary |
Cannot start gnome-terminal because of gconf error |
Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error |
|
| 2009-07-17 16:20:26 |
Kevin O'Gorman |
tags |
regression-release |
gconf regression-release terminal |
|
| 2009-07-17 16:43:59 |
Amos Wenger |
removed subscriber Amos Wenger |
|
|
|
| 2009-08-20 18:00:24 |
Quentin Smith |
bug watch added |
|
http://bugzilla.gnome.org/show_bug.cgi?id=564649 |
|
| 2009-08-20 18:00:24 |
Quentin Smith |
bug task added |
|
gnome-terminal |
|
| 2009-08-20 18:46:19 |
Bug Watch Updater |
gnome-terminal: status |
Unknown |
Confirmed |
|
| 2009-08-21 04:23:40 |
Evan Broder |
bug task added |
|
gnome-terminal (Ubuntu) |
|
| 2009-08-21 05:00:43 |
Evan Broder |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531734 |
|
| 2009-08-21 05:00:43 |
Evan Broder |
debian: importance |
Undecided |
Unknown |
|
| 2009-08-21 05:00:43 |
Evan Broder |
debian: status |
New |
Unknown |
|
| 2009-08-21 05:00:43 |
Evan Broder |
debian: remote watch |
|
Debian Bug tracker #531734 |
|
| 2009-08-22 17:20:46 |
Evan Broder |
attachment added |
|
gnome-terminal_2.26.0-0ubuntu2.1.debdiff http://launchpadlibrarian.net/30671489/gnome-terminal_2.26.0-0ubuntu2.1.debdiff |
|
| 2009-08-24 15:29:00 |
Pedro Villavicencio |
gnome-terminal (Ubuntu): importance |
Undecided |
Low |
|
| 2009-08-24 15:29:00 |
Pedro Villavicencio |
gnome-terminal (Ubuntu): status |
New |
Triaged |
|
| 2009-08-24 15:29:00 |
Pedro Villavicencio |
gnome-terminal (Ubuntu): assignee |
|
Ubuntu Desktop Bugs (desktop-bugs) |
|
| 2009-08-27 22:32:46 |
Evan Broder |
summary |
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 |
|
| 2009-08-27 22:32:46 |
Evan Broder |
description |
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ sudo gnome-terminal
Failed to contact the GConf daemon; exiting.
(original report didn't have sudo in this command, but a later comment by the submitter amended this.)
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb.
This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered.
summary of some stuff posted in comments:
gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings.
gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user.
executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar).
Workarounds to use until the bugs are fixed:
for the gconfd-not-running case:
start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.)
multiple tabs over ssh:
use screen(1)
$ sudo aptitude install screen screen-profiles # if you don't have it already
The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them "windows"). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not.
If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.)
You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab.
root shells:
You can use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo or gksudo on the one or two commands that need it.
This bug is partly that gconf requires DBUS, which breaks some remote-GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part.
Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...)
I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies.
|
Binary package hint: gnome-terminal
IMPACT: gnome-terminal will fail to launch under any circumstance where gconfd isn't already running. This can include `sudo gnome-terminal` (since no gconfd is running for root), or starting gnome-terminal under a non-GNOME window manager.
DEVELOPMENT: The Debian maintainer added 02_let_gconf_autostart.patch in 2.26.2-2 to solve this issue (debbugs #531734). That version has been merged into Karmic.
PATCH: Patch available at http://launchpadlibrarian.net/30671489/gnome-terminal_2.26.0-0ubuntu2.1.debdiff, with test builds in https://launchpad.net/~broder/+archive/ubuntu-tests. The upstream gnome-terminal maintainer rejected the patch used for 02_let_gconf_autostart.patch, because it reintroduced gnome-bugs #561663. The attached patch instead cherry-picks the commit the maintainer added to fix this bug upstream.
INSTRUCTIONS: Attempt to run `sudo gnome-terminal`. It will exit with "Failed to contact the GConf daemon; exiting."
REGRESSION: Seems limited - this is a cherry-pick of an upstream change that only changes a handful of lines.
============
Original bug description:
I cannot start gnome-terminal. If I open an xterm and start gnome-terminal from the command line, here is what I get:
$ sudo gnome-terminal
Failed to contact the GConf daemon; exiting.
(original report didn't have sudo in this command, but a later comment by the submitter amended this.)
$ ps ax | grep gconf
3956 pts/0 R+ 0:00 grep gconf
6643 ? S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
6647 ? S 0:06 /usr/lib/libgconf2-4/gconfd-2
This is in Jaunty Alpha 4 with all updates current as of 12 Feb.
This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered.
summary of some stuff posted in comments:
gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings.
gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user.
executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar).
Workarounds to use until the bugs are fixed:
for the gconfd-not-running case:
start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.)
multiple tabs over ssh:
use screen(1)
$ sudo aptitude install screen screen-profiles # if you don't have it already
The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them "windows"). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not.
If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.)
You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab.
root shells:
You can use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo or gksudo on the one or two commands that need it.
This bug is partly that gconf requires DBUS, which breaks some remote-GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part.
Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...)
I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies.
|
|
| 2009-08-31 13:33:58 |
Martin Pitt |
bug task added |
|
gconf2 (Ubuntu Jaunty) |
|
| 2009-08-31 13:33:58 |
Martin Pitt |
bug task added |
|
gnome-terminal (Ubuntu Jaunty) |
|
| 2009-08-31 13:35:11 |
Martin Pitt |
gnome-terminal (Ubuntu): status |
Triaged |
Fix Released |
|
| 2009-08-31 13:41:13 |
Martin Pitt |
gconf2 (Ubuntu): status |
Triaged |
Invalid |
|
| 2009-08-31 13:42:00 |
Martin Pitt |
gconf2 (Ubuntu Jaunty): status |
New |
Invalid |
|
| 2009-08-31 13:51:24 |
Martin Pitt |
gnome-terminal (Ubuntu Jaunty): status |
New |
Fix Committed |
|
| 2009-08-31 13:51:32 |
Martin Pitt |
tags |
gconf regression-release terminal |
gconf regression-release terminal verification-needed |
|
| 2009-08-31 13:53:22 |
Evan Broder |
debian: status |
Unknown |
Fix Released |
|
| 2009-09-01 06:39:09 |
Martin Pitt |
tags |
gconf regression-release terminal verification-needed |
gconf regression-release terminal verification-done |
|
| 2009-09-01 06:56:37 |
BlueSky |
removed subscriber BlueSky |
|
|
|
| 2009-09-02 08:57:25 |
HavocXphere |
removed subscriber HavocXphere |
|
|
|
| 2009-09-09 09:24:54 |
Launchpad Janitor |
gnome-terminal (Ubuntu Jaunty): status |
Fix Committed |
Fix Released |
|
| 2009-09-10 01:11:02 |
Maxim Levitsky |
removed subscriber Maxim Levitsky |
|
|
|
| 2009-12-05 02:45:52 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/jaunty-proposed/gnome-terminal |
|
| 2009-12-21 18:26:14 |
Evan Broder |
removed subscriber Evan Broder |
|
|
|
| 2009-12-21 18:26:17 |
Evan Broder |
removed subscriber Debathena Project |
|
|
|
| 2009-12-21 18:30:05 |
Evan Broder |
bug |
|
|
added subscriber Debathena Project |
| 2010-01-22 13:56:09 |
Ubuntuxer |
removed subscriber Ubuntuxer |
|
|
|
| 2010-02-28 01:14:31 |
BearTM |
removed subscriber BearTM |
|
|
|
| 2010-05-01 20:33:29 |
Antenna |
removed subscriber Antenna |
|
|
|
| 2010-06-14 15:32:55 |
linfidel |
removed subscriber linfidel |
|
|
|
| 2010-09-14 09:35:02 |
Bug Watch Updater |
dbus: importance |
Unknown |
Critical |
|
| 2010-09-14 09:35:12 |
Bug Watch Updater |
bug watch added |
|
http://defect.opensolaris.org/bz/show_bug.cgi?id=2980 |
|
| 2010-09-16 02:21:31 |
Bug Watch Updater |
gconf: importance |
Unknown |
Medium |
|
| 2010-09-16 11:14:11 |
Bug Watch Updater |
gnome-terminal: importance |
Unknown |
Wishlist |
|
| 2011-01-25 12:04:00 |
Bug Watch Updater |
dbus: importance |
Critical |
Unknown |
|
| 2011-01-25 12:13:34 |
mabawsa |
removed subscriber mabawsa |
|
|
|
| 2011-02-03 14:39:59 |
Bug Watch Updater |
dbus: importance |
Unknown |
Critical |
|
| 2011-02-16 06:21:00 |
Anthony Fok |
bug |
|
|
added subscriber Anthony Fok |
| 2012-05-04 10:34:38 |
Bug Watch Updater |
gnome-terminal: status |
Confirmed |
Fix Released |
|
| 2012-05-04 10:44:11 |
Valentin Neacsu |
removed subscriber Valentin Neacsu |
|
|
|
| 2012-05-04 12:01:33 |
Nicolas Breton |
removed subscriber Nicolas Breton |
|
|
|
| 2013-08-13 19:41:05 |
MiaErbus |
bug |
|
|
added subscriber MiaErbus |
| 2014-09-23 14:43:45 |
Bug Watch Updater |
dbus: status |
In Progress |
Fix Released |
|
| 2014-09-23 16:29:32 |
Andrew |
removed subscriber Andrew |
|
|
|
| 2014-09-23 16:53:06 |
David Ring |
bug |
|
|
added subscriber David |
| 2014-09-25 20:09:03 |
Bug Watch Updater |
dbus: status |
Fix Released |
Confirmed |
|
| 2014-09-25 20:09:03 |
Bug Watch Updater |
dbus: importance |
Critical |
Medium |
|
| 2018-08-19 00:39:21 |
Bug Watch Updater |
gconf: status |
New |
Won't Fix |
|
| 2018-08-21 00:13:04 |
Sammy Spets |
removed subscriber Sammy Spets |
|
|
|
| 2018-11-07 20:44:06 |
Bug Watch Updater |
dbus: status |
Confirmed |
Unknown |
|
