[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Tags added: rls-bb-incoming -- 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 meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
Rachel, I can't find any existing reports of this problem in Launchpad or upstream. So please report the bug to the Gnome developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new issue ID. -- 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/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
But before you report the problem upstream, please try uninstalling your extensions: b'org.gnome.shell' b'enabled-extensions' b"['hide_activit...@shay.shayel.org', 'custom-hot- corn...@janrunx.gmail.com', 'autohide-batt...@sitnik.ru', 'user-theme @gnome-shell-extensions.gcampax.github.com', 'suspend-button@laserb', 'dash-to-d...@micxgx.gmail.com', 'customcor...@eccheng.gitlab.com', 'remove-dropdown-arr...@mpdeimos.com']" and then verify the problem still happens. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Summary changed: - gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] + [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] -- 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 meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817620] Re: High cpu usage on alt-tab-ing
I think this bug is very clear already. It really requires someone (most likely future me) to do some profiling on the primary test case: > just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). Also, there's a secondary issue you mention: > Also, just whizzing the mouse around on the screen (not moving anything) would keep the cpu at 40-50%. Please remove that from the description because it's a different bug (https://gitlab.gnome.org/GNOME/mutter/issues/283). -- 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/1817620 Title: High cpu usage on alt-tab-ing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Done. I think this bug should now be discussed upstream where a fix would occur and there are people who know the code: https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 ** Summary changed: - gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU) + gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] -- 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: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817978] [NEW] lubuntu 19.04 no onscreen keybboard found (x86 tablet - fcitx)
Public bug reported: I'll write shortly (on a device with real keyboard) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: fcitx 1:4.2.9.6-5 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: LXQt Date: Thu Feb 28 01:44:40 2019 LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190227) PackageArchitecture: all SourcePackage: fcitx UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "fcitx_not_seen_main_window.png" https://bugs.launchpad.net/bugs/1817978/+attachment/5242175/+files/fcitx_not_seen_main_window.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1817978 Title: lubuntu 19.04 no onscreen keybboard found (x86 tablet - fcitx) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1817978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738164] Re: [snap] U2F doesn't work with yubikey
** Changed in: gnome-software (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774904] Re: No defualt sound. Test speakers not working.
Hi, in my case, I think it was simply a missing package dependency. Installing the libcanberra-pulse package fixed it for me. gnome-control should probably add libcanberra-pulse to a proper dependency rather than just recommends since it's likely common that people would want to test speakers and the test silently failing (e.g. control-centre doesn't even warn its missing the libs it needs) makes a user (me for example) get lost (i.e. inspecting ALSA, etc) when the silent test failure misleads. Also noted at the end of: https://bugs.launchpad.net/ubuntu/+source /gnome-media/+bug/736349 -- 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/1774904 Title: No defualt sound. Test speakers not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802520] Re: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it
I just upgraded to 18.10 and have the same problem. For me, the output when opening a single gnome-terminal is the following. # watch_fast: "/com/canonical/unity-gtk-module/" (establishing: 0, active: 0) # unwatch_fast: "/com/canonical/unity-gtk-module/" (active: 0, establishing: 1) # watch_established: "/com/canonical/unity-gtk-module/" (establishing: 0) # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) -- 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/1802520 Title: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1802520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802520] Re: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1802520 Title: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1802520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738164] Re: [snap] U2F doesn't work with yubikey
** Changed in: gnome-software (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774904] Re: No defualt sound. Test speakers not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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://bugs.launchpad.net/bugs/1774904 Title: No defualt sound. Test speakers not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1643190] Re: Often I am required to unplug and replug the power cable for the indicator to register that my machine is fully charged
** Changed in: gnome-shell 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/1643190 Title: Often I am required to unplug and replug the power cable for the indicator to register that my machine is fully charged To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1643190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795421] Re: [cosmic] sidebar requires scrolling
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- 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/1795421 Title: [cosmic] sidebar requires scrolling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817647] Re: locking ubuntu doesn't work properly
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen ** 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 evince in Ubuntu. https://bugs.launchpad.net/bugs/1817647 Title: locking ubuntu doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1817647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.
This is still an issue for me on Ubuntu 18.04. Can mount iPhone 5 via Nautilus but it doesn't show on Rhythmbox or Banshee. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1641417 Title: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1641417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Hello Agustin, or anyone else affected, Accepted gnome-control-center into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.28.2-0ubuntu0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU)
I think we need to completely remove Android Emulation from the title and description. I never use that, nor have I ever, and I see this crash constantly. It's EXTREMELY frustrating. What do you guys need from us in order to help us track this issue? I want to do what I can to help get this fixed. -- 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: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787], often when running Android emulator (QEMU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
@daniel, could you give some specifics on your issue you are having. Can't your organisation manually modif the apt configuration or environement variable? do you rely on the GNOME tool to apply manually the configuration on each machine, or how does it work? -- 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/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size
Ok, I found the issue and proposed a fix upstrfeam https://gitlab.gnome.org/GNOME/gedit/merge_requests/27 ** Changed in: gedit (Ubuntu) Status: New => In Progress ** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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/1817459 Title: gedit assert failure: corrupted size vs. prev_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
I installed a fresh copy of 18.04 from an iso too and the issue is still persisting, the proxy issue is preventing us to deploy an important machine for our organization will there be a fix for this issue soon? -- 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/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
NB: If you launch an app from a terminal, eg: gnome-calculator, it *does* then get the input focus; just not when launched from gnome- shell. That's why I didn't think it was a mutter 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/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817924] [NEW] apps launched from gnome shell do not get input focus
Public bug reported: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed -- 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/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236]
The patch was merged to master. I've performed piglit-test and run check totem-app functionality - all looks good. I close the card. -- 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/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Changed in: mesa Status: Confirmed => Fix Released -- 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/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236]
The mentioned patch has landed in master and 19.0 (presumably it is or will be in 18.3 shortly), is this okay to close? -- 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/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
OK, so /var/cache/app-info/ exists before and after software-updater runs. But it does not exist in between while it prepáres the upgrade. ** Summary changed: - Crash on Upgrade to 18.10 from 18.04 Network Not Available + Crash on Upgrade preparation from 18.04 to 18.10 in APT::Update::Post-Invoke-Success -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade preparation from 18.04 to 18.10 in APT::Update::Post- Invoke-Success To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
I forgot to mention: of course, network connectivity is given. And the system is up-to-date. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade preparation from 18.04 to 18.10 in APT::Update::Post- Invoke-Success To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1794213/+attachment/5242040/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1794213/+attachment/5242039/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-12 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Package: appstream 0.12.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-02-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf _MarkForUpload: True ** Tags added: apport-collected bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817620] Re: High cpu usage on alt-tab-ing
Thanks for the reply. I'll run Apport as soon as I can access the machine again. Regarding the actual issue, I don't think it is as cut and dry as this being just about rendering alone, as that would imply that the rendering performance was consistently bad. As I wrote, the performance seems fine on a fresh boot and also after restarting gnome-session (once the bug has appeared), which would not be the case if this was down to just rendering. Some kind of memory issue (leak, fragmentation, ...) seems to play a part in order to explain the time component. Also, there is no window preview (which I assume is a small boxed window preview when Alt-Tab-ing) when I have disabled the Coverflow plugin, yet the stuttering performance was very much present. When it comes to testing out the issue with 19.04, you'll have to bear with me, as this issue takes some time to materialize :-) I have not been able to reproduce it in a short time. Are there any debugging tools I can employ to gain some insight/stats/vitals if/when I encounter this issue? -- 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/1817620 Title: High cpu usage on alt-tab-ing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
I can confirm, experiencing the same. So from what I understand is that apt executes if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi which fails. It checks whether the two files /var/cache/app-info and /usr/bin/appstreamcli both exist and if so it attempts to run appstreamcli. appstreamcli handles AppStream metadata and the AppStream index. /var/cache/app-info does not exist on my system. Not sure if it is supposed to be there all the time or just during the uggrade process. Leaving my VM in the current condition so I can gather more information if needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794213] Re: Crash on Upgrade to 18.10 from 18.04 Network Not Available
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: appstream (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade to 18.10 from 18.04 Network Not Available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817900] Re: FFe 3.31.90
Uploaded to proposed ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Fix Committed -- 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/1817900 Title: FFe 3.31.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
Let's tag that one as blocking the update, it's making easy to lock your session without obvious way out ** Tags added: block-proposed -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817900] Re: FFe 3.31.90
These are some minor features. I'm going to self-approve this FFe, since we don't have a choice other than to upload this. I'll block this update in proposed until Shell itself is ready to move out, too. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High ** Tags added: block-proposed -- 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/1817900 Title: FFe 3.31.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817900] [NEW] FFe 3.31.90
Public bug reported: === Version 3.31.90 === - Translation updates - Remove libXtst as a dependency Keyboard: - Enable ibus for OSK purposes on X11 Power: - Add x-gnome-privacy-scope hints to power notifications - Define brightness to be -1 if builtin display is disabled Smartcard: - Wait until smartcards are inspected before locking screen - handle a smartcard getting removed very shortly after login == Version 3.31.2 == - Translation updates Color: - Add DBus API to preview Night Light for a few seconds Media-keys: - Default to interactive shutdown action for power button if the action is not supported. Power: - Avoid setting GError twice - Speed up tests by splitting into chunks Print-notification: - Ignore Server* messages from CUPS not meant to us Rfkill: - Use GUdev to monitor rfkill device pressence == Version 3.31.0 == - Translation updates - Build improvements - Add desktop-entry hints to notifications Power: - Guard against events from the wrong device type - Hide suspend-then-hibernate behind a meson option Media-keys: - Increase GSD_REENABLE_POWER_BUTTON_DELAY to 3 seconds - Add mapping for Ctrl + media-key for some media-keys Rfkill: - Fix GIOChannel encoding Color: - Fix check for timerfd - Correct temperature interpolation corner cases ** Affects: gnome-settings-daemon (Ubuntu) Importance: High Status: Confirmed ** Tags: block-proposed -- 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/1817900 Title: FFe 3.31.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725955] Re: "Printer added" notification
It still occurs in 18.04. -- 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/1725955 Title: "Printer added" notification To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I am very interested on the status of this bug, since I am considering which version of Ubuntu to install. I have just 3 questions about it: * If I understand correctly, the bug does not occur in Ubuntu 18.10. The user can switch seamlessly between using the Intel or the Nvidia discrete graphics card. Is this correct? * What is the status in Ubuntu 18.04? Is the bug solved? * In Ubuntu 18.04, is it possible to run the laptop disabling the Nvidia graphics card completely (with the card not consuming any power)? How can this be achieved? -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size
Ok, I managed to trigger it, you need to pick documents for the "recent document" popdown, creating new ones or using ctrl+O to open files doesn't do it (the function from the valgrind log hinted that) -- 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/1817459 Title: gedit assert failure: corrupted size vs. prev_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size
Could you give details on what you do exactly? Is adding tabs enough? Or do you need to open existing documents? Do you save same or do editing without saving in a way that should trigger the 'do you want to save before exiting' dialog? -- 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/1817459 Title: gedit assert failure: corrupted size vs. prev_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794139] Re: At random times, no warning when closing a file after it's been deleted
Upstream reopened it ** Changed in: gedit (Ubuntu) Importance: Undecided => Low ** Changed in: gedit (Ubuntu) Status: New => Triaged -- 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/1794139 Title: At random times, no warning when closing a file after it's been deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1794139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1816634 Title: GNOME Shell consistently ignores mouse clicks in a particular app window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816634/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size
Thanks, that has the details of the error ==2494== 1 errors in context 1 of 1208: ==2494== Invalid free() / delete / delete[] / realloc() ==2494==at 0x483897B: free (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==2494==by 0x4891CEF: gedit_open_document_selector_dispose (gedit-open-document-selector.c:753) ==2494==by 0x4A91F82: g_object_unref (gobject.c:3308) ==2494==by 0x4A91F82: g_object_unref (gobject.c:3238) ==2494==by 0x4FF8395: gtk_container_destroy (gtkcontainer.c:1700) ==2494==by 0x4A8CD90: g_closure_invoke (gclosure.c:810) ==2494==by 0x4AA0895: signal_emit_unlocked_R (gsignal.c:3751) ==2494==by 0x4AA944D: g_signal_emit_valist (gsignal.c:3391) ==2494==by 0x4AA9B0E: g_signal_emit (gsignal.c:3447) ==2494==by 0x520CE6B: gtk_widget_dispose (gtkwidget.c:12098) ==2494==by 0x4A91F82: g_object_unref (gobject.c:3308) ==2494==by 0x4A91F82: g_object_unref (gobject.c:3238) ==2494==by 0x50D2061: gtk_menu_button_dispose (gtkmenubutton.c:1058) ** Changed in: gedit (Ubuntu) Status: Incomplete => New ** Changed in: gedit (Ubuntu) Importance: Medium => High -- 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/1817459 Title: gedit assert failure: corrupted size vs. prev_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
