[Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Thanks for reminding me about this bug. It's now on this checklist: https://trello.com/c/pe5mRmx7 -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738487] Re: Shell crashes with JS ERROR: TypeError: monitor is null
Jack: This bug is closed. Please open a new bug. -- 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/1738487 Title: Shell crashes with JS ERROR: TypeError: monitor is null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1738487/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755986] Re: WiFi icon / settings gone from user menu
[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://bugs.launchpad.net/bugs/1755986 Title: WiFi icon / settings gone from user menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767706] Re: Ubuntu 18.04 no guest session available in gdm
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767706 Title: Ubuntu 18.04 no guest session available in gdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
[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://bugs.launchpad.net/bugs/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
** Changed in: gdm3 (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
The attachment "debdiff adding upstream patch" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784892] Re: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
[Expired for tracker (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tracker (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1784892 Title: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1784892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730540] Re: gnome-shell freezes after resume then unlock
Please don't send us crash files. Crash files should instead be reported by running: ubuntu-bug /path/to/your.crash P.S. This bug is already closed. -- 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/1730540 Title: gnome-shell freezes after resume then unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Mario: gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying. Please log a bug for it by running: ubuntu-bug gnome-control-center -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency)
** Tags added: cosmic ** Description changed: - Binary package hint: gnome-terminal - - Hello, - - the transparency in gnome-terminal on LUCID no longer works, I have only - solid color, whatever changes I make in the profil. - - Thanks for your help. - - LGDN. + gnome-terminal transparency no longer works reliably (usually opaque, + but sometimes shows transparency) -- 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/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal
*** This bug is a duplicate of bug 561370 *** https://bugs.launchpad.net/bugs/561370 ** This bug has been marked a duplicate of bug 561370 gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) -- 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/1726262 Title: 17.10 - flickering overlay patterns in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1281169] Re: Dashboard plugin doesn't work
Because this bug has been open for years and the Dashboard plugin doesn't work, I have made it so that it is no longer built in Ubuntu 18.10. ** Bug watch added: GNOME Bug Tracker #727251 https://bugzilla.gnome.org/show_bug.cgi?id=727251 ** Changed in: gedit-plugins Importance: Medium => Unknown ** Changed in: gedit-plugins Status: Invalid => Unknown ** Changed in: gedit-plugins Remote watch: GNOME Bug Tracker #739759 => GNOME Bug Tracker #727251 ** Changed in: gedit-plugins (Ubuntu) Status: Confirmed => Triaged ** Changed in: gedit-plugins (Ubuntu) Importance: Undecided => Medium ** Bug watch added: Debian Bug tracker #881395 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881395 ** Also affects: gedit-plugins (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881395 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1281169 Title: Dashboard plugin doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gedit-plugins/+bug/1281169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
This bug was fixed in the package apparmor - 2.12-4ubuntu8 --- apparmor (2.12-4ubuntu8) cosmic; urgency=medium * lp1788929+1794848.patch: - disallow writes to thumbnailer dir (LP: #1788929) - disallow access to the dirs of private files (LP: #1794848) -- Jamie Strandboge Thu, 27 Sep 2018 17:25:04 + ** Changed in: apparmor (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1788929 Title: Debian/Ubuntu AppArmor policy gaps in evince To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1788929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795210] Re: nautilus crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1785819 *** https://bugs.launchpad.net/bugs/1785819 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1795210 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795254] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libgstreamer-plugins-base1.0-0 no debug symbol package found for libpython2.7-stdlib no debug symbol package found for libkrb5support0 no debug symbol package found for libgssapi-krb5-2 no debug symbol package found for libk5crypto3 no debug symbol package found for libkrb5-3 no debug symbol package found for libogg0 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1795254/+attachment/5194979/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- 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/1795254 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795254] nautilus crashed with SIGSEGV
Stacktrace: No stack. StacktraceSource: StacktraceTop: ThreadStacktrace: ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1795254 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795254] [NEW] nautilus crashed with SIGSEGV
Public bug reported: after turn on system ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 30 20:39:32 2018 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+423+246'" InstallationDate: Installed on 2018-09-29 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795254 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767264] Re: Window manager refresh rate is different from monitor refresh rate
I might be experiencing a similar bug or the same one. 60Hz selected in xrandr, but everything refreshes at 40Hz including glxgears. 40Hz is an available option for the resolution of 1366x768, but 60Hz is selected. Switching to 1360x768 gives a refresh rate of 59.96Hz that actually works and everything syncs to it, so for now I am using this resolution. -- 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/1767264 Title: Window manager refresh rate is different from monitor refresh rate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1767264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792758] Re: Unity Launcher icons replaced by ?
My understanding is that this was a bug in glib2.0 which is now fixed. ** Package changed: unity (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => 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/1792758 Title: Unity Launcher icons replaced by ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1792758/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792758] [NEW] Unity Launcher icons replaced by ?
You have been subscribed to a public bug: For a couple days now, on 18.10 fully updated, upon starting an app from the Unity launcher, the icon is replaced by a question mark. Logging out and back in brings the icons back, but they are replaced by the ? icon as soon as I launch an app. I tried running "unity --reset-icons" which changed my icon theme to what I guess is the new theme, but problem is still present. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released -- Unity Launcher icons replaced by ? https://bugs.launchpad.net/bugs/1792758 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
Off-topic but possibly necessary context: Ubuntu (major) releases are time based. The time of the release is indicated in the release version. As such, Ubuntu 18.10 will be released in year (20)18, month 10. More precise release dates are provided at https://wiki.ubuntu.com/Releases Point releases of LTS versions do not necessarily coincide with other releases. Ubuntu 16.04.2 LTS was released on February 16, 2017 (so between Ubuntu 16.10 (Oct '16) and Ubuntu 17.04 (Apr '17)), which suggests that Ubuntu 18.04.2 may release in February 2019. -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
This bug also appears in Arch linux 4.18.10 running gdm 3.30.1 on X11 (xorg server 1.20.1). -- 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/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795239] Re: XWayland crash, multiple displays
** Description changed: Hello, https://lists.freedesktop.org/archives/wayland- devel/2018-September/039422.html Best regards, -- Cristian Aravena Romero (caravena) + + --- + + https://patchwork.freedesktop.org/patch/247271/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: wayland-protocols 1.16-1 Uname: Linux 4.18.11-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 30 11:42:52 2018 Dependencies: - + InstallationDate: Installed on 2017-10-13 (351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: wayland-protocols UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to wayland-protocols in Ubuntu. https://bugs.launchpad.net/bugs/1795239 Title: XWayland crash, multiple displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1795239/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795239] [NEW] XWayland crash, multiple displays
Public bug reported: Hello, https://lists.freedesktop.org/archives/wayland- devel/2018-September/039422.html Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: wayland-protocols 1.16-1 Uname: Linux 4.18.11-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 30 11:42:52 2018 Dependencies: InstallationDate: Installed on 2017-10-13 (351 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: wayland-protocols UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wayland-protocols (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to wayland-protocols in Ubuntu. https://bugs.launchpad.net/bugs/1795239 Title: XWayland crash, multiple displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1795239/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 743176] Re: Pink layer on taken screenshots (gnome-screenshot)
Hi! No idea if this is a significant discovery or a statement of the obvious but will post anyway. Running Ubuntu 16.04 here; for whatever reason for the past roughly six months I have been been having random lock-ups: display freezes except for the mouse point (usually) and the processes (DejaDup, the Virtual Machine running Windows XP, etc.) also usually continue to work. Recently found a work-around: boot, log-out (via the gear icon at the upper right), log back in but first click on the foot icon and select a different option. Here I have Gnome, Gnome Flashback (Compiz), Gnome Flashback (Metacopy), and Ubuntu (default). I selected the ‘Compiz’ one and my lockups magically went away! According to the post I was following this reduced/eliminated video hardware acceleration. ...The side effect, at least for me, is area screen shots (Shift_PrintScreen) now have the pink overlay. What I’m wondering is in Post #31 BDSword suggest an increase of the 200 value in “g_timeout_add (200, emit_select_callback_in_idle, cb_data)”, something about a delay timeout. I’m wondering if there is a connection between this value and it has effectively been slowed down by my changing from the Ubuntu option to the Compiz option, the latter supposedly turning off video acceleration. Just a WAG, but may help the developers and troubleshooters to find the solution. (Now to try increasing that 200 value – to what??! And from my notes what file?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/743176 Title: Pink layer on taken screenshots (gnome-screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/743176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
Looks like the next point release i.e. 18.04.2 is scheduled to be along with release of 18.10 which is likely to be in Feb-19. Will we have to wait for the fix until then ? What are the chances of backporting the fix to 3.28 branch (as mentioned by Mr.Marco Trevisan) before Feb-19 ? I always prefer to install only LTS stable releases and therefore, will not be installing 18.10. -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756826] Re: hangs when remote search provider performs expensive operation
** Merge proposal unlinked: https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/355858 -- 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/1756826 Title: hangs when remote search provider performs expensive operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795136] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1795028 *** https://bugs.launchpad.net/bugs/1795028 In my brief testing, this appears to be fixed by the same fix for LP: #1795028 so I'm marking it a duplicate of that bug. I've added a Test Case there that resembles this bug's description. The fix needs to be manually approved by the Ubuntu Release Team since the archive is partially frozen in preparation for Ubuntu 18.10's release soon. ** This bug has been marked a duplicate of bug 1795028 Nautilus crashes during search in is_recursive_search (search-engine) -- 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/1795136 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795028] Re: Nautilus crashes during search in is_recursive_search (search-engine)
** Merge proposal unlinked: https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/355858 -- 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/1795028 Title: Nautilus crashes during search in is_recursive_search (search-engine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
** Description changed: Our product is using LibAppIndicator - Please find the dependency tree below for libappindicator, it is using on libglib + Please find the dependency tree below for libappindicator, it is using libglib - libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 - libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 - libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 - libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 - libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 - libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 - libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 - libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 + libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 + libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 + libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 + libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 + libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 + libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 + libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 + libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 -- 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/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795230] [NEW] Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
Public bug reported: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using on libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795223] [NEW] Blank Screen option "Never" changed to "0 Seconds"
Public bug reported: In the Power menu, when selecting the option "Never" for Blank Screen, after you leave the menu and return it is changed to the option "0 Seconds". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 30 12:17:26 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1795223 Title: Blank Screen option "Never" changed to "0 Seconds" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
I've just encountered this today with 18.04, all updates installed both gsd-color and gsd-keyboard and gsd-clipboard all maxing out CPU leading to 60 seconds of non-interactive machine (I know lots of people that would have simply power-cycled, but I wanted to know if it was a separate issue). -- 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/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795210] Re: nautilus crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1785819 *** https://bugs.launchpad.net/bugs/1785819 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1785819, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1795210/+attachment/5194807/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194809/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194813/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194814/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194815/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194816/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1795210/+attachment/5194817/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1785819 nautilus crashed with SIGABRT in g_assertion_message() ** Tags removed: need-amd64-retrace -- 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/1795210 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795136] Re: nautilus crashed with SIGABRT in g_assertion_message()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1795136 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795210] [NEW] nautilus crashed with SIGABRT in g_assertion_message_expr()
Public bug reported: Search in Computer with åäö. Nautilus kept searching. Canceled the search, which worked OK. Edited the search with backspace. Removed ö and removed ä. Nautilus crashed when å was the only character in the search field. I suppose this is related to bug#1795136. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 30 10:19:08 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'268' b'org.gnome.nautilus.window-state' b'geometry' b"'1108x849+1425+107'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-08-09 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180809) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () nautilus_directory_add_file () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795210 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795136] Re: nautilus crashed with SIGABRT in g_assertion_message()
** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795136 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)
One more thing about the bubblewrap. Now that gnome-desktop3 (libgnome-desktop-3-17_3.30.1-1ubuntu1) is build against bubblewrap and depends on it, thumbnailer is working correctly on my system. The new gnome-desktop3 has been changed: "debian/patches/disable-bubblewrap.patch, debian/control*: Drop changes to disable bubblewrap, now that it is approved to go into main." I did test this with the official nautilus-3.26.4-0ubuntu4 and tracker_2.1.4-1 (in proposed). -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
