Public bug reported:
If you have ~/Pictures/Screenshots open in Nautilus and you take new
screenshots, some of them will get tiny thumbnails instead of regular
size thumbnails.
See attached picture of the end result: some images have full size
thumbnails, some have tiny ones.
ProblemType: Bug
Di
Looking through upstream bug tracker I wonder if this might be caused by
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487#note_1553836?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bu
I have the same problem but with Intel video. Chromium 124.0.6367.60
shows up camouflaged as my desktop wallpaper after the last snap update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launch
Public bug reported:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At fi
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769945/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.l
apport information
** Attachment added: "HookError_chromium_browser.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769946/+files/HookError_chromium_browser.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-brows
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769950/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769948/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769947/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
ht
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769951/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
ht
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769952/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bu
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769949/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
ht
apport information
** Attachment added: "Snap.Info.cups.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769954/+files/Snap.Info.cups.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bu
apport information
** Attachment added: "Snap.Info.core20.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769953/+files/Snap.Info.core20.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https:
apport information
** Attachment added: "Snap.Info.gnome-42-2204.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769955/+files/Snap.Info.gnome-42-2204.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
dmesg has a bunch of repeated
`snap revert chromium` reverted to 123.0.6312.122, which works fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2063304
Title:
chromium 12
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769956/+files/Snap.Info.gtk-common-themes.txt
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
(sorry, copy/paste fail)
> dmesg has a bunch of repeated
bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20243):
apparmor="DENIED" operation="open" class="file"
profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=7070
comm="FSBroker7944" requested_mask="r
The syscall=330, the mknod denial, the /etc/vulkan/ denials are also
produced by the working chromium snap.
The /etc/igfx_user_feature.txt denial only shows up with the broken
chromium snap.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049
(Confirming that I have ozone-platform-hint set to Auto instead of
Default in chrome://flags.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chr
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3451
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
I'm also seeing memory leaks in transmission-gtk after upgrading to
22.04 LTS. In 48 hours it eats up all the RAM and Swap and gets killed
by systemd-oomd.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://b
The memory leak makes transmission unusable, so this bug should qualify
for a SRU. All we need is for someone to prepare a debdiff and request
sponsorship for the upload, as described in
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1973084 ***
https://bugs.launchpad.net/bugs/1973084
** This bug has been marked a duplicate of bug 1973084
transmission-daemon high RAM usage
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to trans
This appears to have been fixed in transmission 4.0 packages in 23.10
(mantic) and Debian sid.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1775434
Title:
Wrong ExecStop in sys
I backported Andrey Kudinov's suggested change (replacing Ubuntu's
openssl3-compat.patch with gentoo's version) and built a transmission
package in a PPA for jammy (Andrey's PPA only has packages for kinetic
and lunar).
I've been testing the patched transmission-gtk for the last 24 hours and
the m
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-
calculator/-/issues/359
Upstream says the actual bug is in libsoup:
https://gitlab.gnome.org/GNOME/libsoup/-/issues/361.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/-/issues #359
https://gitlab.gnome.org/GNOME/gnome-calculator
Debian reverted the change to isolate these low quality fonts from the
rest of the system in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=883973, and now this bug is back in Ubuntu 23.10.
** Bug watch added: Debian Bug tracker #883973
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8839
Public bug reported:
There's a default keybinding of XF86Tools to launch gnome-control-
center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no
longer works in Ubuntu 22.10. Instead I see this error in my journal:
spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find
This was fixed upstream in version 42.beta:
https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/commit/371a1260630035724e20972ae5bda7098e2928a7
Ubuntu explicitly reverts that in debian/patches/ubuntu/Revert-media-
keys-fix-gnome-settings-desktop-file.patch with the rationale
> Ubuntu isn't ge
I'm now using Xephyr to confine my ChromeDriver-based Selenium tests
Xephyr :2 -screen 1300x720
export DISPLAY=:2
unset WAYLAND_DISPLAY
This works fine for me on Ubuntu 22.10 in a Wayland session (and it also
worked on 22.04 LTS).
As a bonus, the Chromium window doesn't steal focus a
I've already upgraded to vivid so won't be able to do the verification.
** Changed in: xserver-xorg-video-intel (Ubuntu Utopic)
Assignee: Marius Gedminas (mgedmin) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is
Chris Wilson said this on IRC:
"The issue is that after the hotplug interrupt is sent by the hardware,
the monitor is not yet ready to respond to the DDC probes and generates
a NAK instead - this leads us to conclude that there is nothing on the
other end of the connector"
so it looks like a genu
Tried talking about this on IRC (#intel-gfx on FreeNode). It was
suggested to me to capture the kernel log after setting drm.debug to
0x5. That produced quite a lot of log output (70 thousand lines in
about a minute), and after some trimming I got something that could
perhaps be useful: https://g
gdb in Ubuntu links against libpython3.4.
The Python scripts in /usr/share/glib-2.0/gdb haven't been fully ported
to Python 3: the custom iterators should define a '__next__' method
alias pointing to 'next'.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed
Somewhat-related upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=720635
** Bug watch added: GNOME Bug Tracker #720635
https://bugzilla.gnome.org/show_bug.cgi?id=720635
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 i
Upstream bug with a patch:
https://bugzilla.gnome.org/show_bug.cgi?id=749092
** Bug watch added: GNOME Bug Tracker #749092
https://bugzilla.gnome.org/show_bug.cgi?id=749092
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ub
Public bug reported:
Apport sometimes gets confused when analyzing a core dump:
SegvAnalysis: Failure: invalid literal for int() with base 16: '='
I'm attaching the crash file (sans base64-encoded core dump) that
contains this and some other wonderful examples, like
Registers: $6 = 0x0
I booted an Ubuntu 12.04 LTS desktop live session with testdrive, apt-
get installed xchat-gnome version
1:0.30.0~git20110821.e2a400-0.2ubuntu4.2 and attempted to connect
slack.com's IRC gateway.
The connection was successful.
** Tags removed: removal-candidate verification-needed
** Tags added:
I built a patched 2:2.99.914-1~exp1ubuntu4.2mg1 (debdiff applied fine,
except for the debian/changelog bits) and uploaded it to my ppa
(ppa:mgedmin/ppa). I'm currently running it: shadows are fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
I have vague memories of filing this bug in the past, reproducing the
issue, attaching a log file, and seeing libsane getting all the blame
(since it's libsane returning error codes from sane_read).
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Unfortunately simple-scan doesn't do log rotation, so I don't have a
copy of ~/.cache/simple-scan/simple-scan.log with the failures.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/14
Public bug reported:
1. Try to scan an 18-page document: launch simple-scan
2. Press the scan button, get a page
3. Repeat for pages 2 to 7
4. Press the scan button again, get an error
5. Futilely retry a few times, try to unplug and re-plug the USB cable, nothing
helps
6. Launch xsane, try to ac
Ah, the bug I filed last time was #1261440 and it was a different
situation (scanning failed in the middle of a page).
It's the same office scanner, though (HP Color LaserJet 2840).
The fact that simple-scan failed to scan the page several times in a row
and then succeeded after I restarted simpl
If you use GNOME Shell, you'll find the Preferences in the application
menu (Super+F10 or click on the application name in GNOME Shell's top
panel).
If you don't use GNOME Shell, I think it's supposed to have a regular
menu (which will probably also appear in the top panel in a Unity
session), but
This does not appear to have been fixed. I just got an apport dialog
about an assertion failure in signon-ui, pointing towards this bug
report. I have signon-ui 0.11.0ubuntu1, installed since Nov 02
according to my dpkg.log, and given that my last reboot was on Dec 19,
I'm sure this was the versi
Public bug reported:
I can make windows 50% translucent in gnome-shell if I run
xprop -f _NET_WM_WINDOW_OPACITY 32c -set _NET_WM_WINDOW_OPACITY
0x7fff
and click on a window, but when I try the same with
transset 0.5
nothing appears to change (and xprop doesn't show a
_NET_WM_WINDOW_
Here are xtrace log files capturing the X requests made by transset
(which failed) and xprop (which succeeded) on the same window.
** Attachment added: "xtrace of transset that had no effect"
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1301472/+attachment/4060918/+files/transset-fa
** Attachment added: "xtrace of xprop that had an effect (on the same window)"
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1301472/+attachment/4060919/+files/xprop-success.xtrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
The problem seems to be with the window ID: instead of picking up the
gnome-terminal window (id 0x0166) I clicked on it picked up some
strange unnamed 1366x741+0-0 window at +0+27, probably belonging to
gnome-shell.
--
You received this bug notification because you are a member of Desktop
Pac
Looks like transset is not doing the "does the window have WM_STATE?
recurse through its children if not" logic employed by xprop/xwininfo.
Compare Get_Window_Under_Cursor from transset/dsimple.c and
Select_Window from xprop/dsimple.c).
--
You received this bug notification because you are a memb
Forwarded upstream to https://bugs.freedesktop.org/show_bug.cgi?id=76958
** Bug watch added: freedesktop.org Bugzilla #76958
https://bugs.freedesktop.org/show_bug.cgi?id=76958
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-apps i
This was fixed in unity-settings-daemon 14.04.0+14.04.20140402-0ubuntu1.
It remains unfixed in gnome-settings-daemon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Public bug reported:
Freshly upgraded to 14.04. Can't launch System Preferences: /usr/bin
/gnome-control-center.real segfaults on startup.
Here's a backtrace with debug symbols:
mg@platonas: ~ $ gdb /usr/bin/gnome-control-center.real
GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
Copyright (C)
Trying to step through this with gdb.
In main(), control-center.c:254 the following statement
shell = gnome_control_center_new ();
assigns NULL to shell, after emitting a few warnings:
(gnome-control-center.real:653): GLib-GObject-WARNING **: cannot
derive 'GnomeControlCenter' from non-
** Also affects: software-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1302896
Title:
Unreadable text in Ubuntu s
*** This bug is a duplicate of bug 1302896 ***
https://bugs.launchpad.net/bugs/1302896
** This bug has been marked a duplicate of bug 1302896
Unreadable text in Ubuntu software center
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug has been marked a duplicate of bug 1309419
gnome-control-center segfaults on startup on 14.04
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
*** This bug is a duplicate of bug 1309419 ***
https://bugs.launchpad.net/bugs/1309419
** This bug is no longer a duplicate of bug 1278209
gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
** This bug has been marked a duplicate of bug 1309419
gnome-control-ce
I can reproduce this by creating a new user account (sudo adduser guest)
and logging in.
I cannot reproduce this by booting Ubuntu GNOME 14.04 LiveCD.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https:
Ok, turns out I hadn't actually purged all the PPA packages correctly,
and so I somehow ended up with gnome-control-center 1:3.6.3-0ubuntu56
but libgnome-control-center1 1:3.10.1-0ubuntu1~saucy3 .
After I downgraded the former gnome3-team/gnome3 PPA packages to their
versions in trusty, this probl
It's possible that gnome-terminal 3.14 might get the translucent background
feature back:
http://blogs.gnome.org/uraeus/2014/04/16/preparing-the-ground-for-the-fedora-workstation/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-ter
This is fixed in trusty.
(Chromium in Trusty uses Aura, which doesn't have this problem.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1242663
Title:
Omnibox text jumps up
mutter 3.10.4 from trusty (no PPA) builds with the two patches applied
(here's a debdiff). I tested with debuild wile waiting for 'pbuilder-
dist create trusty', now I'm waiting for 'pbuilder-dist build trusty
mutter_3.10.4-0ubuntu2mg1.dsc'... Ok, this builds too.
I could upload the fixed mutter
Apologies, I accidentally commented on the wrong bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1317921
Title:
Titlebar corruption after window maximization
Status in “
Trusty has gnome-settings-daemon 3.8.6. Support for XF86AudioMicMute was added
in gnome-settings-daemon 3.9.2:
https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af1
I believe gnome-settings-daemon (and unity-settings-daemon) need to
backport that patch fo
Public bug reported:
Steps to reproduce
1. Launch xbmc (I use version 2:12.3~git20131213.0944-frodo-0precise from
http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/)
2. Press \ a few times to toggle fullscreen mode
What happens: X segfaults and I'm thrown back to the login screen.
(xbmc also segfa
Public bug reported:
Today I installed a mainline kernel for testing an unrelated bug and
rebooted. On login apport popped up a non-localized error dialog.
About a minute or two later apport popped up a second error dialog, this
time it was translated to my desktop language (Lithuanian).
These
I didn't have a DisplayPort cable before. I used an analog VGA cable
and hotplug detection worked reliably.
I could boot a 12.04 LTS LiveCD and test it, if it's important.
I'd like to help debug this. It would help if I knew how hotplug
detection is supposed to work, and what tools there are fo
Just saw this bug with gvfs 1.18.2-0ubuntu1. Same as original reporter:
crash on eject.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
gvfsd-mtp assert failure: *** Error
Ubuntu 12.04 also had those lines in those config files.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/312296
Title:
NeatReceipts Mobile Scanner NR-030108 Unsupported Out-of-th
I found this bug by looking at the DuplicateOf field in the Apport
dialog before I hit the 'Report' button. I can't say how reliable is
apport's backtrace matching, but I remember noticing something about
"invalid free()" in that report.
I then tried and managed to reproduce a crash on eject, and
I should mention that when I say "eject", I meant hitting the ⏏ icon in
Nautilus. I'm not yanking USB cables prematurely.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
g
Ubuntu 13.10 already has this line in /etc/sane.d/gt68xx.conf:
##
# Autodetect NeatReceipts Mobile Scanner
usb 0x07b3 0x0462
and /lib/udev/rules.d/40-libsane.rules has
ATTRS{idVendor}=="07b3", ATTRS{idPr
Public bug reported:
1. Plug in USB scanner (actually multi-function HP Color LaserJet 2840)
2. Start simple-scan
3. Try to scan
It errors out saying there's no scanner plugged in.
I can launch xscanimage and scan fine. So I try simple-scan again.
This time it starts scanning and then stops wit
Here's simple-scan.log from the 2nd attempt, where it failed with a read
error after 10% of the scan.
** Attachment added: "simple-scan.log"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1261440/+attachment/3930782/+files/simple-scan.log
--
You received this bug notification bec
Public bug reported:
Steps to reproduce:
1. Type some text in the Chromium address bar
Expected behavior: text does not jump up and down
Actual behavior: text jumps up and down (see attached screencast).
Apologies for the large size of the screencast. I tried to unplug my
external monitor to r
If I install the Adwaita theme[1] to make Chromium fit in with the rest
of my GNOME desktop, this problem comes back.
[1] https://chrome.google.com/webstore/detail/adwaita-
gnome-3/oojbknijfmdmidgcgchmojbildmbdamm?hl=en
--
You received this bug notification because you are a member of Desktop
Pa
This is very similar to
https://code.google.com/p/chromium/issues/detail?id=27103, except that
bug was closed in 2009. Also, I didn't see this with Chromium 28 in
raring.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
If I go to chrome://settings/ and click 'Use Gtk+ theme', this problem
goes away.
If I go to chrome://settings/ and click 'Use classic theme', this
problem comes back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in U
Submitted upstream as
https://code.google.com/p/chromium/issues/detail?id=309605
** Bug watch added: code.google.com/p/chromium/issues #309605
http://code.google.com/p/chromium/issues/detail?id=309605
** Also affects: chromium-browser via
http://code.google.com/p/chromium/issues/detail?id=3
** Bug watch added: GNOME Bug Tracker #525574
https://bugzilla.gnome.org/show_bug.cgi?id=525574
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=525574
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
That's bug 209447.
*glares at Launchpad*
*grumbles about lack of a Preview button*
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading respons
Looks like a duplicate of 209447.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1067301
Title:
ssh-add: Error reading response length from authentication socket.
Status in GNO
I built a patched gnome-terminal in my PPA:
https://launchpad.net/~mgedmin/+archive/ppa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1040885
Title:
gnome-terminal auto-restor
Since this bug has security implications (gnome-shell crash on resume
unlocks the session), I think it's worth pursuing a SRU for
accountsservice.
Does anyone want to help me with that? I've never asked for a SRU
before.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
S
A simpler workaround: pressing Fn-Home/Fn-End (screen brightness control
keys) after plugging in the DisplayPort cable also triggers detection.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bu
*** This bug is a security vulnerability ***
Public security bug reported:
slack.com is a chat service with optional IRC integration. Since today
I can no longer connect to their IRC gateway using XChat-GNOME. The
error is:
> * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL
> ro
1 - 100 of 268 matches
Mail list logo
