Looks like this issue does not exist when we use Ubuntu with Wayland in
18.04. I am using it now. Will update the details if there is any
change.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]
** Changed in: hundredpapercuts
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.
[Expired for shotwell (Ubuntu) because there has been no activity for 60
days.]
** Changed in: shotwell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.lau
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-contro
[Expired for hexchat (Ubuntu) because there has been no activity for 60
days.]
** Changed in: hexchat (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.la
Remember this bug is only about "entries with stack traces ending in
osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)".
If you have any other problem then please open a new bug for it by
running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a mem
^^^
That is bug 1772677. Not this one.
--
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/1812593
Title:
gnome-shell[3159]: JS ERROR: Exception in callback for signal:
activate:
** Changed in: gnome-control-center
Status: New => Fix Released
--
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/1818751
Title:
can not switch between single disp
** Summary changed:
- Totem player hangs when seeking video
+ Totem player hangs when seeking video due to [gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]
** No longer affects: totem (Ubuntu)
** Project changed: totem => libva
--
You received this bug notific
Yes I will be backporting the same fix to bionic. At least I will try
to. I don't know what conflicts and incompatibilities might be in mutter
3.28.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchp
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
[bionic][regression] gnome-shell crashes with SIGSEGV in
met
This bug was fixed in the package pygobject - 3.32.0-1
---
pygobject (3.32.0-1) experimental; urgency=medium
* New upstream release
-- Jeremy Bicha Sun, 10 Mar 2019 12:59:34 -0400
pygobject (3.31.4-1) experimental; urgency=medium
* New upstream release
* Bump minimum glib
Public bug reported:
Typo'd as openvtswitch
** Affects: gnome-software (Ubuntu)
Importance: Low
Assignee: Robert Ancell (robert-ancell)
Status: Fix Committed
** Affects: gnome-software (Ubuntu Xenial)
Importance: Low
Assignee: Robert Ancell (robert-ancell)
S
It says the sender of this error is gnome-session-b? who's that? where's
the code that generates this error? I'm on 18.10, upgraded from 18.04
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
calling StartServiceByName for org.gnome.ScreenSaver:
GDBus.Error:org.freedesktop.DBus.
I was affected but I haven't seen it since 17.10, I seem to remember it
was actually fixed a long time ago, but this bug report must have been
forgotten.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member o
*since 18.04
--
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/1705689
Title:
When adding an app to favourites, two icons are created.
To manage notifications about this bug go t
Ok, thanks. It still feels like rather odd behavior.
--
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/1819497
Title:
gnome-control-center autonomously uninstalling
To m
Thank you for your bug report. It's not a bug though, gnome-control-
center depends on network-manager since it's using it as a service and
going to fail to work if that one is missing.
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-cente
@Łukasz
Will you not be following/patching bionic with this fix? (@Daniel)
--
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/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap
** Also affects: systemd
Importance: Undecided
Status: New
--
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/1819471
Title:
gsd-power is not using lid-close-su
Public bug reported:
Over the last couple of weeks gnome-control-center has autonomously uninstalled
(or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the
second time when I uninstalled NetworkManager (and installed WICD instead). In
both cases, trying to run gnome-con
These are the commands I used to cause the bug:
1st time:
sudo apt purge wpasupplicant
2nd time:
sudo apt install wicd-gtk
sudo apt remove network-manager-gnome network-manager
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-co
I had the same issue, followed David's instructions, but I still get a
rapidly expanding syslog file when I lock the screen. I am running
Ubuntu 18.04.02 with gnome shell 3.28.3, dual monitor and intel
graphics.
Something I can see is that when locked the screens are first turned to
black, then th
I am looking for if the patch was included before the release of mesa
"19.0.0-rc7"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1815236
Title:
totem assert failure: totem: src/inte
They could pass to [1]mesa_19.0.0~rc7
[1]
https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog
https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.
** Bug watch added: freedesktop.org Bugzilla #109535
https://bugs.freedeskt
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
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/1819471
Title:
gsd-power is not using lid-close-susp
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desk
** Changed in: intel-vaapi-driver (Ubuntu)
Status: Incomplete => Triaged
** Changed in: intel-vaapi-driver (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.
Thanks
** Changed in: libfprint (Ubuntu)
Status: New => Triaged
** Also affects: libfprint via
https://gitlab.freedesktop.org/libfprint/libfprint/issues/151
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop B
*** This bug is a duplicate of bug 1812527 ***
https://bugs.launchpad.net/bugs/1812527
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Thank you for your bug report, the key is ubuntu specific and buggy, but
the feature request is also discussion upstream on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #111
https://gitlab.gnome.org/GNOME
Fixed in gobject-introspection (1.60.0-1).
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Released
--
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/1816415
Title:
** Description changed:
- I'm using 18.04 on Lenovo T480. Suspending on lid close is not possible with
external monitor attached.
+ I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with
external monitor attached.
Even if everything is set properly:
$ gsettings get org.
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.4
---
mutter (3.30.2-1~ubuntu18.10.4) cosmic; urgency=medium
* Add support for high frame rate displays (LP: #1763892):
- Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch
- Add lp1763892-a-renderer-n
I think we can assume that at least the mutter cosmic SRU does not
introduce regressions and does fix the bug for certain testers. In case
there's a follow-up fix needed, please file a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
Public bug reported:
I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with
external monitor attached.
Even if everything is set properly:
$ gsettings get org.gnome.settings-daemon.plugins.power
lid-close-suspend-with-external-monitor
true
$ dconf read
/org/gnome/settings-
** Tags added: sts
--
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/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
To manage notifications about this bug go to:
https://bu
** Changed in: totem
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1818862
Title:
Totem player hangs when seeking video
To manage notifications about
Kay-Heng, what's the status of the linux image landing on bionic?
Can you help in verify this once we've all there?
--
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/174503
Tested in gnome-shell 3.28.3+git20190124-0ubuntu18.04.1,
No error is spawned here.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1805444
Title:
Daniel, while the fix¹ didn't landed yet it will land on 3.32.1².
[1] TBH this isn't really a fix for the problem itself but at least in ubuntu
where we
compile without `G_DISABLE_CHECKS` will mute the crash, making things for
us at least
good enough to close this.
[2] https://gitlab.g
Yep, sure. (Ideally as a sync.)
It'd be nicer for me in future if you could paste the NEWS entries and
other things, so that I can read it all and reply directly from my email
client. :-)
** Changed in: pygobject (Ubuntu)
Status: New => Confirmed
** Changed in: pygobject (Ubuntu)
Impor
** Tags added: fixed-3.32.0
--
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/1819126
Title:
gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-
content.c:155:st_imag
Hi,
I believe my problem is related to this bug report. I am running Ubuntu 18.04.2
with GNOME 3.28.2, intel graphics and dual screen. The /var/log/syslog file
keeps on expanding out of control. I believe this is happening when the screen
is locked. If the screen is locked for a long time, it is
I have the same bug. I used to work around this by installing an
alternative sound device selector shell extension but this one broke
down when Gnome shell upgraded to 3.31.91. So now there is no way for me
to switch to HDMI output any more.
The select box shows the correct devices but selecting a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https:/
Both raring and quantal now EOL so request is no longer valid
** Changed in: evolution (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1
What error exactly did you see after that update?
--
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/1021375
Title:
Nautilus says the USB stick is read only when it is not
To manage
** Changed in: yelp (Ubuntu)
Importance: Undecided => Low
--
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/1732991
Title:
I can't use mouse buttons to navigate Ubuntu Desktop Guide
That's fixed in the current version
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Fix Released
--
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/18
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Reporter resolved issue by restoring a backup.
Report no longer valid so closing.
** Changed in: evolution (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Thank you for your bug report, that's an upstream decision of removing
support for .desktop launchers, see
https://gitlab.gnome.org/GNOME/nautilus/issues/184
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #184
https://gitlab.gnome.org/GNOME/nautilus/issues/184
** Changed in: nautil
** Changed in: libfprint (Ubuntu)
Status: New => Triaged
** Bug watch added: gitlab.freedesktop.org/libfprint/fprintd/issues #16
https://gitlab.freedesktop.org/libfprint/fprintd/issues/16
** Also affects: libfprint via
https://gitlab.freedesktop.org/libfprint/fprintd/issues/16
Imp
sorry, commented on the wrong bug
** No longer affects: libfprint
** Changed in: libfprint (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/18
Thanks, it's https://gitlab.freedesktop.org/libfprint/fprintd/issues/16
** Bug watch added: gitlab.freedesktop.org/libfprint/fprintd/issues #16
https://gitlab.freedesktop.org/libfprint/fprintd/issues/16
** Changed in: libfprint (Ubuntu)
Importance: Undecided => High
** Changed in: libfprin
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
--
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/1712122
Title:
Desktop keyboard shortcuts autorepeat
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shel
Upstream bug closed "RESOLVED FIXED" on 2014-07-01
Fixed in evolution 3.13.x, so in all currently supported versions of Ubuntu
** Changed in: evolution (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
** Also affects: totem via
https://github.com/intel/intel-vaapi-driver/issues/448
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1818862
Upstream bug closed "RESOLVED FIXED" on 2017-06-28
so fixed in recent versions of Ubuntu.
** Changed in: evolution (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
h
Bug did not expire due bugwatch
No reply to comment #6 so closing
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launc
Bug did not expire due to bug watch
No reply to comment #5 so closing
** Changed in: gedit (Ubuntu)
Status: Incomplete => Invalid
--
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/
Thanks. Upstream bug: https://github.com/intel/intel-vaapi-
driver/issues/448
** Bug watch added: github.com/intel/intel-vaapi-driver/issues #448
https://github.com/intel/intel-vaapi-driver/issues/448
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Hmm, not sure what I did wrong last time, but you're right: Uninstalling
i965-va-driver does resolve the issue. I'll report the crash at the
intel-vaapi-driver repo as suggested.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in
I am closing this bug since it is old and tracker does not seem to crash
any longer while indexing the file that caused it to crash.
** Changed in: tracker-miners (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
** 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/1761709
Title:
gnome-terminal-server crashed with signal 5
To manage notif
70 matches
Mail list logo
