Public bug reported:
I press super a lot to see progress of other applications or the system time
from activities overview when in a fullscreen application, such as a steam game.
Occasionally the activities overview will not show any applications nor the
desktop, but only the gray background
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1893693
Title:
Unable to scroll gnome app list
To manage notifications about this bug go to:
Public bug reported:
I'm unable to scroll from page 1 to 2 in all apps under the gnome app
list. Changing the dock from left side to bottom or right side solves
the issue. Ubuntu 20.04 fresh install. See here for same issue:
https://askubuntu.com/questions/1241165/should-i-report-show-
Public bug reported:
I can no longer connect to my ISP mail server.
Works in previous version 19.10
"The reported error was “Failed to get capabilities: Error performing
TLS handshake: The Diffie-Hellman prime sent by the server is not
acceptable (not long enough).”."
I've tried finding a
I've come to a pseudo-resolution by disabling Wayland usage in gdm3.
- Edit /etc/gdm3/custom.conf and simply uncomment:
#WaylandEnable=false
- restart everything and Switch Users works fine.
I included this comment as "NOTE 3" in the bug report.
** Description changed:
Ubuntu 18.04
Public bug reported:
Ubuntu 18.04 freezes and must be manually powered down and rebooted when
attempting to "Switch User".
Prerequisites:
- Use Ubuntu 18.04
- You need at least 2 users (e.g. user1 and user2)
Expected behavior:
- While logged in as any user, choose "Switch User" from top power
Public bug reported:
Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
color profile switching. The commit at fault is
104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
when processing update” (which was intended to fix LP bug 1847044).
Upstream issue:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/185
Title:
gnome-session-binary crashed with SIGSEGV in
This is fixed by
https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested
850ef518795dcc20d3b9a4f661f70ff8d0ddacb2).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1843107
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1843107
Title:
Themes and font settings don’t apply to X
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771
https://gitlab.gnome.org/GNOME/mutter/issues/771
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/771
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
By adding some debugging output to mutter and gnome-shell I verified
that mutter emits the x11-display-opened signal before gnome-shell is
able to connect a handler for it, and the handler never runs.
(Possibly things would be different in the experimental autostart-
xwayland mode, but the whole
Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem. Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t
Public bug reported:
After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
tweaks are no longer applied to X11 applications when running in a
Wayland session (I tried Firefox and Emacs). This seems to be because
@snabb (Janne) #7 or @ljh48332 (Luke) just detected this again in latest
release and will present a workaround that solves it even with
continuous Ubuntu/Debian/Gnome updates. Could you give some insight into
why this service is kept and not removed completely? Even the Gnome
threads state it
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
I hope 3.32.1 will get into Disco, but in case this can’t happen and a
more minimal set of patches is required, these are the nine upstream
patches I added to my mutter package to get it to stop crashing on
wakeup:
fe86694dd renderer/native: Make EGLStream page flip errors non-fatal
1eabaf12d
This bug came back again in latest ubuntu, this time a new symptom
occurred. Gnome extensions are also regularly disabled for some reason.
Removing gsd-housekeepin still works.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1820331
Title:
gnome-shell crashed with SIGABRT
To manage notifications
This bug came back in recent updated after using workaround #5 by Janne.
Didn't notice at first, then severe system slowdowns and odd power
behaviour started to occur. 100% Fan on etc. Killing my disk long term
as well. I detected it when the gsd-housekeepin service crashed and
Ubuntu notified
This is a standard for music players. Follow the standard!!!
--
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/185928
Title:
Pressing Space key should toggle play/pause (pause when
This happens on a clean installation of 18.10 here as well, and I'd like
to point out that the window miniature previews are clearly visible and
in some cases even readable from the lock screen by right clicking the
application icons and selecting "All Windows".
--
You received this bug
@Plurto your workaround was successful for my case as well. Thanks.
Weird bug, transparency affecting clicks and interaction through a lock
screen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Hi @Plurto. Where is this setting and is it a default ubuntu setting?
Thanks.
Note: Just using the default installation (had no active extensions
before upgrade besides Ubuntu system defaults). I.e., have not installed
dash to dock.
--
You received this bug notification because you are a member
Same problem after upgrade from 18.04 to 18.10. However, the whole
screen is visible when manually locking the screen (ctrl + alt + L in my
case).
All programs are minimized when locking manually/or resuming from
suspend and the screen goes slightly blurry, but not enough to distort
text for
Btw, for me this happens 100% of all suspend/manual lock cases. Gnome
has crashed once completely as well since upgrade due to this issue. In
18.04 the whole screen was visible sometimes for a very short period of
time after lock, this is worse.
--
You received this bug notification because you
Problem exist in 18.10 as well after upgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1745666
Title:
gsd-housekeeping leaks file descriptors
To manage
Same issue, not as severe regarding disk space. No extensions active.
# NOTE: will only grep first line of stacktracce
journalctl -m | grep osdWindow.js | wc -l
3597
gnome-shell --version
GNOME Shell 3.28.3
Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a64961dc90),
has been
#journalctl -b | grep gsd-housekeepin | wc -l
100067
Going for #5 by Janne since nothing else works (annoying task to keep
performing). It is also the suggestion by Fedora maintainers as systemd
does the same task of cleaning tmp
(https://bugzilla.redhat.com/show_bug.cgi?id=1563445)
Upstream
In 15 hours 6000 new messages occur.
#journalctl -b | grep gsd-housekeepin | wc -l
12000
The permission on /var/tmp
drwxrwxrwt 45 root root 56K okt 1 14:53 tmp/
The permissions on mkinitramfs stuff in /var/tmp
drwxr-xr-x 12 root root 4,0K jan 21 2017 mkinitramfs_NNARsN/
-rw--- 1
As long as you're working on this package would you mind including the
one-line upstream patch for bug 1788483, if you haven't already?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
That was a local build. I also saw it on Launchpad with an unrelated
patch (bug 1788483):
https://launchpadlibrarian.net/391298478/buildlog_ubuntu-
cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz
However, the failure seems to have disappeared with today’s updates of
other packages, or maybe
Nope, the message persists even with fs.inotify.max_user_watches=524288
Total nr messages:
# journalctl -m | grep gsd-housekeepin | wc -l
1947297
Previous nr boot messages (no reboot after workaround was applied, could be
weeks):
#journalctl -b | grep gsd-housekeepin | wc -l
51500
Current nr
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
A full build log is attached. The relevant part is these test failures.
==
clutter 1.26.1: tests/conform/test-suite.log
(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)
** Patch added: "debdiff adding upstream patch, rebased"
I'm fairly sure this is related to changes in fs.inotify.max_user_watches ("Too
many open files"). I recently got a bunch of warnings in misc code editors
about low values. Took me a while to understand the max_user_watches had
reverted back to the default value of about 8000. I.e., some update
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194411/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194409/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
The fan and cpu is very active during this event, thousands of
assertions reported. Syslog case attached.
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194410/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194406/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
All extensions are disabled. All gnome-shell extensions, if enabled, do
severe spamming of the syslog. Most errors are related to "st.bin"
and/or "st.whatever" has been already
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194407/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194405/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1745666 ***
https://bugs.launchpad.net/bugs/1745666
** This bug has been marked a duplicate of bug 1745666
gsd-housekeeping leaks file descriptors
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Public bug reported:
The fan and cpu is very active during this event, thousands of errors
reported. Syslog case attached. The desktop becomes unresponsive during
this event (for instance cant close windows).
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
apt-cache policy
I think this bug i filed might be a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1795111
In my case i could detect that the desktop became unresponsive as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Description changed:
All extensions are disabled. All gnome-shell extensions, if enabled, do
severe spamming of the syslog. Most errors are related to "st.bin"
and/or "st.whatever" has been already deallocated. I.e., at least six
popular extensions experience similar crashes after
Public bug reported:
The fan and cpu is very active during this event, thousands of
assertions reported. Syslog case attached.
lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.3
Public bug reported:
All extensions are disabled. All gnome-shell extensions, if enabled, do
severe spamming of the syslog. Most errors are related to "st.bin"
and/or "st.whatever" has been already deallocated. I.e., at least six
popular extensions experience similar crashes after software
Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720
** Bug watch added: trac.nginx.org/nginx/ #720
http://trac.nginx.org/nginx/ticket/720
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.
** Changed
Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
** Changed in: rasqal (Ubuntu)
Status: New => Incomplete
** Changed in: slang2 (Ubuntu)
Status: New => Incomplete
--
You received this
• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support,
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
** Changed in: nmap (Ubuntu)
• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug:
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing:
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support
** Bug watch added:
Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped. A corresponding Depends was already dropped in
https://bugs.debian.org/757140.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”). The API is completely different and this is expected. See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug
GNOME on Wayland works around the crash.
Based on the apport-retrace results, this is possibly a duplicate of bug
1788483.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1790992
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard
language does not work either most of the time (Super + Space). Those I
use the most. Extremely annoying after some time, especially when using
dual screens (since the Gnome top bar is only on one monitor which is
even more
Sorry, small adjustment. I use wayland as default since 17.10 with gdm
(works well in general for me):
loginctl show-session c1 -p Type
Type=wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This may have been fixed by mutter 3.26.1-2 (bug 1722510). At least I
can no longer reproduce it using the recipe in my duplicate bug 1722709.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in
this crash.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1721681
Title:
gnome-terminal-server crashed with SIGSEGV in
I’m not sure. Since it’s been a week without any sign of an upload to
artful-proposed, I’m changing this back to Confirmed.
I have a patched build of gnome-shell in my PPA if you need it now:
https://launchpad.net/~andersk/+archive/ubuntu/ppa/+packages
It seems to be the TopIcons Plus extension that triggers this so often.
I think that’s roughly consistent with the upstream bug report.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This might be triggered by a shell extension. I haven’t seen any
crashes after turning them all off. I’ll see if I can bisect which one
it is.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This is happening to me very frequently (several times a day) on both
Wayland and Xorg. On Wayland, it brings down the entire session.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714745
Title:
gnome-shell crashed with SIGSEGV in
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
Importance: Unknown
Status: Unknown
** Changed in: systemd
Importance: Unknown => Undecided
** Changed in: systemd
Status: Fix Released => New
** Changed in: systemd
Remote
For anyone ending up here, i lost this feature in 17.04 and need it:
quick fix found at https://askubuntu.com/questions/11/create-new-
document-right-click-option-missing-in-ubuntu-gnome/791946
"
1. See if you have ~/Templates folder. Create one if it is missing using
command:
FYI: got a better experience in gnome when opening a terminal and
running syndaemon -d in gnome. However, that seem to freeze the mouse
slightly too long after I have stopped typing. The unity version works
better (not sure what differs yet).
Related and probably duplicate of:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-
daemon/+bug/1351772
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1576685
Hi, the synaptics (libinput also installed) package work well for me in
16.04 (and previous version to 12.04 at least) up to 17.04 on thinkpads
(x2XX to carbon X1). Currently using carbon x1 5th gen. There is however
some form of instability with settings that affects many users including
me.
Public bug reported:
If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
and I scroll fast in the output of e.g less to cause the "alert sound"
to be played repeatably very fast, pulseaudio crashes.
>From /var/log/syslog:
May 9 15:05:13 ubuntu-laptop indicator-sound[2948]:
Public bug reported:
If you are running ‘journalctl -f’ to try to debug some other problem,
you are constantly interrupted by zillions of these messages from
systemd-resolved:
Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:27 change-mode
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=665073
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gimp (not installed)
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
Public bug reported:
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files
Public bug reported:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping
Public bug reported:
On the MIT network (which runs some ancient version of BIND 9), systemd-
resolved stops resolving anything that isn’t DNSSEC-signed after I
disconnect and reconnect the network. Signed zones continue to resolve.
This happens with either DNSSEC=yes or the default
Public bug reported:
systemd-resolved, or more precisely the hook script /lib/systemd/system
/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add
127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the
other nameservers. That makes no sense because
Public bug reported:
I use a VPN configured with network-manager-openconnect-gnome in which a
split-horizon DNS setup assigns different addresses to some names inside
the remote network than the addresses seen for those names from outside
the remote network. However, systemd-resolved often
Public bug reported:
The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
hosts line of /etc/nsswitch.conf. This makes DNSSEC validation
impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
if libnss_resolve returns a validation failure, glibc will simply
The infinite loop is not in libyaml (yaml_parser_parse), but rather in
its caller in appstream-glib (as_node_yaml_process_layer), which is
ignoring the error code returned by yaml_parser_parse and blindly going
around the loop again. This patch fixes it.
** Patch added:
Public bug reported:
Xenial 16.04
gnome-disk-utility 3.18.3.1
http://pix.toile-libre.org/upload/original/1465929217.png
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop
*** This bug is a duplicate of bug 1579712 ***
https://bugs.launchpad.net/bugs/1579712
** This bug has been marked a duplicate of bug 1579712
Refresh hangs indefinitely, appstreamcli using 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
It seems like if a third party package has been (attempted) installed,
automated updates are disabled.
/ (#17)
However, even after you get the deb package installed, it breaks your
ability to sudo apt-get update. /
---
"Hi, this has been fixed upstream. If you still have issues, please
fully
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 228-5ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu Feb 4
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 228-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu
** Patch added: "vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1528728/+attachment/4539301/+files/vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff
** Tags added: patch
** Bug watch added: Debian Bug tracker #787104
Public bug reported:
Starting gnome-terminal results in a 79×23 window instead of the
standard 80×24, at least in Ubuntu Gnome with the default Adwaita theme
on a high-DPI laptop. This makes it irritating to use some applications
designed for an 80-column terminal.
According to an upstream bug
** Bug watch added: Python Roundup #25493
http://bugs.python.org/issue25493
** Also affects: python via
http://bugs.python.org/issue25493
Importance: Unknown
Status: Unknown
** Bug watch added: GNOME Bug Tracker #757184
https://bugzilla.gnome.org/show_bug.cgi?id=757184
**
This is a combination of two problems. One is that starting update-
manager results in these warnings:
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
+1 on the last comment.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go to:
fixed in 15.04
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1419856
Title:
Long
Every time I press one of these keys, I get the message
(gnome-settings-daemon:7822): GLib-GIO-WARNING **: Dropping signal
AcceleratorActivated of type (ua{sv}) since the type from the expected
interface is (uuu)
This is probably the same thing that happened in LP: #1217196 and LP:
#1376471.
--
1 - 100 of 647 matches
Mail list logo
