Public bug reported:
Binary package hint: gnome-utils
I'm using Ubuntu Intrebid Ibex (8.10) with latest updates, checked a few mins
ago.
gnome-utils package which contains gnome-screenshot is version 2.24.1-0ubuntu1.
I tried to take a screenshot with the right click menu active by pressing the
This bug has been fixed upstream (in version 2.24.1)
** Changed in: gnome-utils (Ubuntu)
Status: Triaged => Fix Released
--
gnome-screenshot fired in terminal grabs window border anyway
https://bugs.launchpad.net/bugs/110827
You received this bug notification because you are a member of U
Confirmed in Intrepid with gnome-utils version 2.24.1-0ubuntu1
Does not work from the console, not with -b switch either. I did not try with
metacity, only with compiz.
When used from console, prints out another bug regarding the new Intrepid theme:
[EMAIL PROTECTED]:~$ gnome-screenshot -b -w
/u
Confirmed by multiple users (including me) even with the current
version.
** Changed in: gnome-utils (Ubuntu)
Status: Triaged => Confirmed
--
"Include the window border" doesn't work by default (with compiz)
https://bugs.launchpad.net/bugs/74008
You received this bug notification because
I had this when using Nokia N8 + Ubuntu 12.04 i386.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/642508
Title:
rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category(
Public bug reported:
I wrote the search term into search box and I pressed enter. After that
the application crashed immediately.
I use Ubuntu 11.04, version 3.0.0-0ubuntu2.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: yelp 3.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/804005
Title:
the app crashes when you press Enter when you write something into
search box
To manage notifications about this bug go
But why is the -o force not enabled by default?
If the case's that it's potentially dangerous to mount a dirty volume,
the package should ASK the user what to do, ignore the case that can
lead to data loss and mount it, or "Do not mount".
The possibility of data loss in dirty unmount situations i
Maybe someone could post a new bug or blueprint of this one?
Preferably one, that has rights to make this change as a "High" or "Medium"
priority, as this is pretty important for users who come from Windows!
A sample case:
Person A installs Ubuntu on his laptop, and has Windows XP/Vista on his
d
