Public bug reported:
Do: File > Create > Screenshot > Select a region to grab > Snap > drag box
Results in error:
Execution error for 'Screenshot':
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19:
Operation was cancelled
ProblemType: Bug
DistroRelease: Ubuntu 20
Example PDF (at least, it seems to reproduce the same error message):
https://sec.report/lux/doc/102081415.pdf
I opened an upstream issue:
https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Bug watch added: gitlab.freedesktop.org/poppler/poppler/-/issues #1140
https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140
** Also affects: evince via
https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140
Importance: Unknown
Status: Unknown
--
You received this
Public bug reported:
Steps to reproduce:
- Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- Log in, click desktop menu item "Power off / logout -> suspend"
- Laptop will suspend
- Press key on USB keyboard to resume
- Resume fails - external
** Bug watch added: Debian Bug tracker #689097
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689097
** Also affects: gtk+2.0 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689097
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Public bug reported:
https://play.google.com/store/apps/details?id=it.medieval.blueftp
get "bluetooth file transfer" from Google Play
run it
click on Bluetooth icon
click on ubuntu-0
pairing - phone loops asking user to enter pin number but unity never shows a
request for pairing
ProblemType: B
*** This bug is a duplicate of bug 932177 ***
https://bugs.launchpad.net/bugs/932177
** This bug has been marked a duplicate of bug 932177
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
--
You received t
*** This bug is a duplicate of bug 932177 ***
https://bugs.launchpad.net/bugs/932177
** This bug is no longer a duplicate of bug 569667
Error communicating with gnome-keyring-daemon
** This bug has been marked a duplicate of bug 932177
XFCE (and other non-GNOME) desktops do not initialis
*** This bug is a duplicate of bug 932177 ***
https://bugs.launchpad.net/bugs/932177
** This bug has been marked a duplicate of bug 932177
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
--
You received t
This is actually a security bug for users of Chrome / Chromium. Chrome will
store passwords in cleartext if gnome-keyring isn't functional. This is
mentioned in the upstream Chrome disk encryption bug
https://code.google.com/p/chromium/issues/detail?id=25404
$ cp ~/.config/chromium/Default/Logi
http://ptspts.blogspot.co.uk/2010/06/how-to-enable-bitmap-fonts-on-
ubuntu.html Using the fixedsc font and conf file from that page worked
for me. Note "The Fixed (6x13) had to be renamed to FixedSC, because the
original 6x13 font has the tag semicondensed, which makes it impossible
to select in t
@Julián the only problem is that gnome-keyring won't actually work (see
comment #27), but if you don't use it, and none of the apps you use rely
on it, then that won't affect you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-k
I also confirm that updating to xkb-data-2.5-1ubuntu1.4 does not fix
this issue.
There are fixes listed for two packages here, should there be an
updated libgtk2.0-0 or some other package in precise-proposed? Or is the
fix in xkb-data alone?
--
You received this bug notification because you ar
** Summary changed:
- WARNING: gnome-keyring:: couldn't connect to PKCS11
+ XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly
/ WARNING: gnome-keyring:: couldn't connect to PKCS11
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Also affects: xfce4-session via
http://bugzilla.xfce.org/show_bug.cgi?id=8014
Importance: Unknown
Status: Unknown
** Also affects: xfce4-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop B
Another comment from Guido regarding modifying the /etc/ autostart
files:
"What happens is that if gnome-keyring components are not initialized
through XDG autostart any more they will be DBus-activated (see
https://live.gnome.org/GnomeKeyring/RunningDaemon). So when they start
adding back the aut
I was interested in the correct solution rather than the workaround of
manually reverting the changes to gnome-keyring's /etc/ config. I asked
Guido Berhoerster, and he said:
"if you are not running gnome-session then gnome-keyring-daemon cannot
be correctly initialized through the XDG autostart m
** Bug watch added: Novell/SUSE Bugzilla #710038
https://bugzilla.novell.com/show_bug.cgi?id=710038
** Also affects: gnome-keyring (openSUSE) via
https://bugzilla.novell.com/show_bug.cgi?id=710038
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
** Bug watch added: GNOME Bug Tracker #660240
https://bugzilla.gnome.org/show_bug.cgi?id=660240
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=660240
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Bug watch added: Red Hat Bugzilla #783568
https://bugzilla.redhat.com/show_bug.cgi?id=783568
** Also affects: gnome-keyring (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=783568
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Bug watch added: Debian Bug tracker #653011
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011
** Also affects: gnome-keyring (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
Unfortunately I don't have that particular crash report anymore.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/964007
Title:
source_gnome-control-center.py Attribute
** Visibility changed to: Public
** Summary changed:
- gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
+ gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
from User Manager
--
You received this bug notification because you are a member of Ubunt
Also source_gnome-control-center.py mixes tabs and spaces!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/964007
Title:
source_gnome-control-center.py AttributeError:
# apport-bug _usr_bin_gnome-control-center.1002.crash
Error connecting to ConsoleKit:
GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup
session information for process '2492'
ERROR: hook /usr/share/apport/package-hooks//source_gnome-control-center.py
crashed:
Traceba
Public bug reported:
ERROR: hook /usr/share/apport/package-hooks//source_gnome-control-center.py
crashed:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 773, in
add_hooks_info
symb['add_info'](self)
File "/usr/share/apport/package-hooks/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/964007
Title:
source_gnome-control-center.py AttributeError: 'NoneType' object has
no attribute 'groups'
To manage no
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/925046
Title:
gnome-control-center sound forgets chosen preferred input device
To manage notifications about this bug go
Public bug reported:
I have two USB audio input devices: sound card and webcam
I always want to use the webcam for audio input
In gnome-control-center I go to "Input" tab and under "Choose a device
for sound input:" I select "Webcam C270 Analogue Mono"
This works but is temporary. When webcam i
Public bug reported:
Using empathy to call via Google Talk to a Google Nexus S phone.
The user appears and I can initiate chat, but "audio call" and "video
call" are grayed out. I can initiate chat in the reverse direction.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: empathy 3.2.0.1-0u
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/925034
Title:
empathy: google talk audio and video call grayed out
To manage notifications about this bug go to:
https://bugs.launchp
--
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/899139
Title:
alt-f2 launcher help does not work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
Public bug reported:
On Gnome desktop. Press alt-f2 to go the program launcher. Click the
help button. Get:
Document Not Found
The URI ‘ghelp:user-guide?gospanel-23#gospanel-23’ does not point to a valid
page.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: yelp 3.2.0-0ubuntu1
ProcVersion
This bug appears to be fixed. Go to Nautilus preferences -> Behavior ->
check "Include a Delete command that bypasses Trash". The action is
bound to shift-delete by default.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/858197
Title:
eog crashed with SIGSEGV in visible_range_changed_cb()
To manage notifications about this bug go to:
https://bugs.launchpad
Public bug reported:
Happens seemingly randomly with multiple eog windows open.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: eog 3.1.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
I have seen a similar / possible the same crash.
(eog:5775): EOG-CRITICAL **: eog_image_get_file: assertion `EOG_IS_IMAGE
(img)' failed
(eog:5775): GLib-GIO-CRITICAL **: g_file_equal: assertion `G_IS_FILE
(file1)' failed
Program received signal SIGSEGV, Segmentation fault.
0x760ad812 in
I can reproduce this crash by doing "gdb eog" in one window, and "for x
in {1..10}; do eog *; sleep 1; done" in another. While the windows are
opening click next/previous in the opened windows.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/852666
Title:
gnome-panel reads free memory in panel_object_loader_stop_loading
To manage notifications a
Public bug reported:
Running valgrind on gnome-panel I noticed:
==4781== Invalid read of size 1
==4781==at 0x4C29FEE: strcmp (mc_replace_strmem.c:538)
==4781==by 0x45C297: panel_object_loader_stop_loading
(panel-object-loader.c:125)
==4781==by 0x45C947: panel_object_loader_idle_handl
valgrind crash with dbgsyms.
(gnome-panel:4699): GLib-GObject-WARNING **: invalid cast from
`PanelToplevel' to `GtkOrientable'
(gnome-panel:4699): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion
`GTK_IS_ORIENTABLE (orientable)' failed
==4699==
==4699== Process terminating with defaul
*** This bug is a duplicate of bug 849600 ***
https://bugs.launchpad.net/bugs/849600
https://bugs.launchpad.net/bugs/849600"Lost something? There’s no
page with this address in Launchpad."
Is there a reason this bug report is a dupe of a private bug?
--
You received this bug notificatio
output from gdb bt full
** Attachment added: "gdb bt full"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/847464/+attachment/2389161/+files/gdbfull
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
Again, with gtk and gnome-panel symbols
(gdb) bt
#0 0x7fffe25928dc in ?? () from /usr/lib/libwnck-3.so.0
#1 0x7594f1aa in g_closure_invoke () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2 0x75961cd7 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x
$ valgrind gnome-panel
...
(gnome-panel:3827): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:2295: signal `size_request'
is invalid for instance `0x1e185900'
==3827==
==3827== Process terminating with default action of signal 8 (SIGFPE)
==3827== Integer divide by
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/847464
Title:
oneiric gnome-panel "Floating point exception" with orientation left
To manage notifications about this bug go to:
Public bug reported:
Set bottom-panel orientation to "left". Gnome panel will no longer
start. Set the orientation to "bottom" and gnome-panel starts ok again.
$ gnome-panel
(gnome-panel:2796): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:2295: signal `size_request
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/846470
Title:
oneiric gnome-panel - The URI ‘ghelp:user-guide?menubar#menubar’ does
not point to a valid page.
To manage notifi
Public bug reported:
right click on "Applications" in gnome-panel
get error:
Document Not Found
The URI ‘ghelp:user-guide?menubar#menubar’ does not point to a valid page.
Search for packages containing this document.
Also, if you do click on "Search for packages containing this document" you g
I think Rodrigo was asking for someone to run those commands on real
hardware. If you run in a VM it is unlikely that a backlight will be
present - afaik VirtualBox/QEMU do not emulate a backlight. It would be
poor isolation if a guest VM going to LCD standby took down the host
LCD.
--
You receiv
I see this in Oneiric too. Very annoying, can be worked around by
disabling nautilus desktop with "gsettings set
org.gnome.desktop.background show-desktop-icons false"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
*** This bug is a duplicate of bug 390816 ***
https://bugs.launchpad.net/bugs/390816
** This bug is no longer a duplicate of bug 609343
gnome-power-preferences needs a "never" option
** This bug has been marked a duplicate of bug 390816
external monitor output is switched off when closin
*** This bug is a duplicate of bug 390816 ***
https://bugs.launchpad.net/bugs/390816
** This bug has been marked a duplicate of bug 390816
external monitor output is switched off when closing the laptop-lid when
gnome-power-manager is set to blank screen on closing
* You can subscribe to
*** This bug is a duplicate of bug 390816 ***
https://bugs.launchpad.net/bugs/390816
** This bug has been marked a duplicate of bug 390816
external monitor output is switched off when closing the laptop-lid when
gnome-power-manager is set to blank screen on closing
* You can subscribe to
The issue does not appear on XDMCP sessions from Lucid->Lucid. It does
appear on sessions from Debian Lenny->Lucid. Maybe there is some
incompatibility between xorg 7.5 and 7.3.
--
gnome-screensaver fails in XDMCP session
https://bugs.launchpad.net/bugs/593318
You received this bug notification b
Public bug reported:
Binary package hint: gnome-screensaver
Run a gnome session over XDMCP remote desktop.
Leave session for 5 minutes.
gnome-screensaver kicks in.
On client there is no evidence that gnome-screensaver is running - the previous
desktop is displayed, and there is no screensaver. T
Using Gnome the display does not dim on boot, and "ctrl-alt-f1 ctrl-
alt-f7" does not dim the screen. Using KDE it does. The KDE battery
monitor screen brightness slider does not work - the brightness always
gets set to the lowest setting. So it looks like this may be a
powerdevil bug (at least, fo
Same here. Thinkpad T42p with ATI Radeon FireGL T2. Display goes dim
after a few minutes. Can be brightened again using the fn-home key
combination.
Same as Memartin: switching to a console with ctrl-alt-f1 then switching
back with ctrl-alt-f7 results in the screen being dimmed.
Using KDE desktop
I had the same problem, incredibly slow playback in totem. I had two
apps loaded which both use xine backends (note I wasn't trying to play
them both at the same time, just had them loaded), totem was using the
xine backend to play video, and amarok was using xine for audio. So I
looked in ~/.xine/
I also get two resume cycles rather than three when acpid is stopped.
With acpid running I got:
$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\),
.*$/keycode \2 = \3, state = \1/p'
keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0
keycode 150 = (keysym 0x1008ff2f, XF86
This also occurs in KDE with kpowersave on Thinkpad T42p in both
Intrepid and Jaunty. It does not occur when selecting Suspend in
Shutdown menu, only when using fn-f4 hotkey.
I thought it might be something to do with ACPI event processing
discussed in bug 267682 ie. the suspend event gets deliver
Same error on Jaunty alpha 3 and jaunty with updates as of 20080130.
Tested with Thinkpad T42p.
--
Hibernate fails on Dell Inspiron 8600 with Intrepid
https://bugs.launchpad.net/bugs/298804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 51537 ***
https://bugs.launchpad.net/bugs/51537
** This bug has been marked a duplicate of bug 51537
Wrong handling of volume buttons on IBM Thinkpad notebooks
--
volume button is to agressive
https://bugs.launchpad.net/bugs/207394
You received this bug
*** This bug is a duplicate of bug 51537 ***
https://bugs.launchpad.net/bugs/51537
** This bug has been marked a duplicate of bug 51537
Wrong handling of volume buttons on IBM Thinkpad notebooks
--
Thinkpad volume control control hardware and software mixer
https://bugs.launchpad.net/bugs
No OSD updates bug may be related to bug #198197 which in turn may be
related to a bunch of ACPI hotkey related bugs.
--
Wrong handling of volume buttons on IBM Thinkpad notebooks
https://bugs.launchpad.net/bugs/51537
You received this bug notification because you are a member of Ubuntu
Desktop B
@sceptic Using KDE? 10 second flicker on KDE:
https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/278471
--
Screen flickers when loading applications
https://bugs.launchpad.net/bugs/245383
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
66 matches
Mail list logo