In fact you have to move the content of the file .gtk-bookmarks (in your
home dir) into the file .config/gtk-3.0/bookmarks
--
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/1165136
I have exactly the same issue on Ubuntu 12.10 with both gedit and
latexila (based on gedit).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1089966
Title:
Gedit scrolling jumps to
Public bug reported:
Ubuntu Precise
Version: 1:3.3.90-0ubuntu4
I want to remove the annoying shortcut ctrl-Q for all gnome applications
through the gnome-control-center and its keyboard panel.
I created a new personal shortcut but when I click on 'deactivated' to choose
my shortcut and I press
** Bug watch added: GNOME Bug Tracker #671448
https://bugzilla.gnome.org/show_bug.cgi?id=671448
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=671448
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Still here on Maverick, for instance with https://www.galaxie
.enseignementsup-
recherche.gouv.fr/ensup/ListesPostesPublies/Emplois_publies_TrieParCorps.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Please, do not post comments that just say it happens to me too. Instead, use
the button this bug affect n persons at the top of the page.
The goal of this button is to avoid flooding in comments and to make a
difference between affected people and comments bringing information to solve
the
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
Gdk-WARNING **: XID collision, trouble ahead
https://bugs.launchpad.net/bugs/401823
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
Sam, your question was not concerned by my post (of course ;)).
Do not open an other report for firefox 3.6 since the problem seems to be the
same than firefox 3.5.
I add the ubuntu firefox package to the list of the affected packages; since
package firefox on Lucid is mapped to firefox-3.6:
Please, do not post comments that just say it happens to me too. Instead, use
the button this bug affect n persons at the top of the page.
The goal of this button is to avoid flooding in comments and to make a
difference between affected people and comments bringing information to solve
the
Here is the full backtrace.
** Attachment added: complete backtrace.
http://launchpadlibrarian.net/43232190/gdb-gnome-system-monitor.txt
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete = New
--
gnome-system-monitor crashes with signal SIGABRT
Can you explain what you do to get the crash please ? Can you reproduce
it ?
** Changed in: empathy (Ubuntu)
Status: New = Incomplete
--
empathy crashed with SIGSEGV in tp_proxy_get_object_path()
https://bugs.launchpad.net/bugs/554741
You received this bug notification because you are a
Public bug reported:
Binary package hint: gnome-system-monitor
lucid, 64bits
gnome-system-monitor 2.28.0-1ubuntu2
Production of the crash:
go in preferences, click on the file system tab, click on the resources
tab, change the value of the frequency using the spinner (I set the value to
** Attachment added: the crash backtrace
http://launchpadlibrarian.net/42975167/gdb-gsm.txt
--
[lucid] gnome-system-monitor crashes with signal SIGABRT
https://bugs.launchpad.net/bugs/554596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
More information:
This is the message I get when I try to lock the screen in command line:
$ gnome-screensaver-command --activate
** Message: Screensaver is not running!
$ gnome-screensaver-command --lock
** Message: Screensaver is not running!
If I start the screensaver using this command:
The issue is the same than the old fixed bug 84858
--
gnome-screensaver no longer locks the screen
https://bugs.launchpad.net/bugs/408873
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs
ok ok... Shame on me... After some investigations to understand why the
screensaver was not running, I figured out that in
system-preference-starting program, the check box screensaver was
not selected.
Now it works great.
@John Lenton: can you check that in order to see if this bug is not a bug
Same problem than #458703 ?
The lastest release of eclipse in karmic fixed that.
--
Buttons in Eclipse not working correctly with GTK+ 2.18.1-1
https://bugs.launchpad.net/bugs/442078
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I have exactly the same problem.
--
nautilus shortcuts doesn't work at first press
https://bugs.launchpad.net/bugs/390662
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
sorry, I forgot to said that I am on jaunty. As far as I remember, I had the
same problem on hardy on the computers.
I will do some tests to see if Compiz has something to do with that.
--
nautilus shortcuts doesn't work at first press
https://bugs.launchpad.net/bugs/390662
You received this
A use case that always produce the problem for me:
In a folder I have a test.pdf file. I open a terminal in this folder and I
launch pdfcrop using the pdf document. I close the terminal. I delete test.pdf
in order to rename the new pdf that pdfcrop created (named test-crop.pdf). I
select
On jaunty the example is not displayed but there is no crash nor cpu
extra use.
--
opening a specific svg uses 100% ram
https://bugs.launchpad.net/bugs/172341
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
21 matches
Mail list logo
