[Bug 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1704807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for gst-plugins-good1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1704807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1704807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland sessions (including login screen)
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (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/1747568 Title: Mouse clicks ignored in Wayland sessions (including login screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735550] Re: Privacy: One screen not covered on wake after sleep
[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/1735550 Title: Privacy: One screen not covered on wake after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1735550/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland sessions (including login screen)
[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/1747568 Title: Mouse clicks ignored in Wayland sessions (including login screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779888] Re: I'm trying to login freshly to my ubuntu 18.04 but the desktop won't show, just the terminal
[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/1779888 Title: I'm trying to login freshly to my ubuntu 18.04 but the desktop won't show, just the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796434] Re: USB storage device does not finish ejecting
@Steve OK, sorry for the incorrect tag. I was just following the instruction to tag it as 'regression-update' in message #26 of bug report #1762595. -- 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/1796434 Title: USB storage device does not finish ejecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796434] Re: USB storage device does not finish ejecting
To add more information to my previous report, I've recently installed Ubuntu 18.04.1 on two machines, one of which is pretty old, and the other is about a year and a half old. I now have a USB storage device that causes this problem to happen every single time I plug it into my older machine. It's a Verbatim 32GB flash stick. It doesn't cause the problem on my newer machine. The logs attached to my report are from the older machine. lsusb reports the vendor and device IDs of the memory stick as 18a5:0302. The stick containsh an exFAT filesystem, and it has a number of large files on it (a few partition image backups made with Clonezilla). It didn't exhibit the problem when it was blank. -- 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/1796434 Title: USB storage device does not finish ejecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796434] Re: USB storage device does not finish ejecting
That would be a failed verification but not a regression. Removing the tag. ** Tags removed: regression-update -- 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/1796434 Title: USB storage device does not finish ejecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796369] Re: Nautilus not generating image thumbnails
Hello, Please: $ ubuntu-bug nautilus And generate new report Best regards, -- Cristian Aravena Romero (caravena) -- 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/1796369 Title: Nautilus not generating image thumbnails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1796369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794896] Re: nautilus does not show Ghex in "Open With">"Other Application" list
Possibly related to bug #1794899. Note that the problem has disappeared. My feel is that there is some underlying problem. -- 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/1794896 Title: nautilus does not show Ghex in "Open With">"Other Application" list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794896] Re: nautilus does not show Ghex in "Open With">"Other Application" list
** Attachment added: "Select Application_148.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794896/+attachment/5197789/+files/Select%20Application_148.png -- 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/1794896 Title: nautilus does not show Ghex in "Open With">"Other Application" list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796434] [NEW] USB storage device does not finish ejecting
Public bug reported: Regresssion of bug #1762595. I have installed Ubuntu 18.04.1 in the past week, and have encountered this problem repeatedly. I found it reported as fixed in gvfs 1.36.1-0ubuntu1.1, but it clearly isn't, because that's the version of gvfs that I currently have installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 01:18:02 2018 InstallationDate: Installed on 2018-09-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-update -- 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/1796434 Title: USB storage device does not finish ejecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793925] Re: a phantom onscreen keyboard appears that I cannot use
submitted PR https://gitlab.gnome.org/GNOME/caribou/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1793925 Title: a phantom onscreen keyboard appears that I cannot use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1793925/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
I believe infinity (or someone like him) had a similar request the last time we removed gjs/390x. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+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 Folks! Updates on the above. I have not found where BDSword's suggestion for (in comment #31) changing that 200 value in the g_timeout line goes -- it doesn't appear to be a clear text file. Did find using the Metacity option does not have the pink overlay option like the Compiz option does, or at least here. I just started testing with Metacity but so far Compiz and Metacity look the same, so for others if one gives a pink overlay try the other as a workaround. -- 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 1796427] [NEW] /usr/bin/gnome-control-center:11:gtk_stack_set_visible_child_name:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.2-0ubuntu0.18.04.2, the problem page at https://errors.ubuntu.com/problem/dd9c94f5bed99401478671f18f030f86d05b2640 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1796427 Title: /usr/bin/gnome-control- center:11:gtk_stack_set_visible_child_name:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1796427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
I think I would have pushed back on doing no-change rebuilds. I'm not sure there's a precedent for that when doing arch-specific removals. And I was planning to handle fixing packages that need it (in Debian, then syncing/merging) to Build-Depend on gjs or something properly, after we got the transition in. (Given how late we are in the release, it was more time sensitive to get the mozjs version switched over than it might otherwise have been.) It's not *hurting* anything, but I think it could have been done a little bit easier if people had waited instead of rushing around and getting worked up. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
Given that it happened the way it did, though, thanks for handling those things. ;-) -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
Someone (probably didrocks?) will need to look into the ubuntu-make autopkgtest on s390x. It depends on ubuntu-desktop and tries to use gdm. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730410] Re: Window full-screen size when Firefox starts
Almost all applications (Firefox, Nautilus, Google Chrome, PyCharm, Skype, Calendar and other) opens in maximized size if it window size was larger than some value (more than about 80% of display width and height) when application was closed. -- Ubuntu 18.04, NVidia drivers, Gnome Shell ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Also affects: pgadmin3 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Also affects: aisleriot (Ubuntu) Importance: Undecided Status: New ** Also affects: gedit (Ubuntu) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Also affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags added: xorg-session -- 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/1730410 Title: Window full-screen size when Firefox starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1730410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
The provides mixup didn't hurt since I didn't upload to the archive and the Vcs revert was handled quickly. The rebuilds are ok to do though, right? -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796284] Re: package gir1.2-mutter-2:amd64 3.28.3-2~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- 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/1796284 Title: package gir1.2-mutter-2:amd64 3.28.3-2~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1796284/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796284] Re: package gir1.2-mutter-2:amd64 3.28.3-2~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1796284 Title: package gir1.2-mutter-2:amd64 3.28.3-2~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1796284/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796369] [NEW] Nautilus not generating image thumbnails
Public bug reported: Ubuntu 18.04.1 nautilus-1:3.26.4-0 When going to a directory with images those images that were there before I updated to 18.04 still display thumbnails. Any new images placed in to the directory don't display thumbnails. Any images, new or old, that are edited and saved back don't display thumbnails. Edit any existing image which does have a thumbnail and the thumbnail will disappear. The same happens on the Desktop which I believe also uses Nautilus to render. I'll attach a screenshot ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot showing missing thumbnails" https://bugs.launchpad.net/bugs/1796369/+attachment/5197636/+files/Screenshot%20from%202018-10-05%2017-49-29.png ** Package changed: cloud-init (Ubuntu) => nautilus (Ubuntu) -- 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/1796369 Title: Nautilus not generating image thumbnails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1796369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796369] [NEW] Nautilus not generating image thumbnails
You have been subscribed to a public bug: Ubuntu 18.04.1 nautilus-1:3.26.4-0 When going to a directory with images those images that were there before I updated to 18.04 still display thumbnails. Any new images placed in to the directory don't display thumbnails. Any images, new or old, that are edited and saved back don't display thumbnails. Edit any existing image which does have a thumbnail and the thumbnail will disappear. The same happens on the Desktop which I believe also uses Nautilus to render. I'll attach a screenshot ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus not generating image thumbnails https://bugs.launchpad.net/bugs/1796369 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796354] [NEW] Document viewer (Evince) shows document "title" and not document "name" on titlebar
Public bug reported: After upgrading to Ubuntu 18.04 Bionic Evince 3.28.2 shows document "title" and not document "name" on titlebar. This is very annoying since titles are pdf metadata that most commonly do not make sense, while pdf names (i.e. location) are easily modified by user and nexessary to distinguish files. This is actually a rebirth of an old issue that eas fixed in previous versions of Evince ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1796354 Title: Document viewer (Evince) shows document "title" and not document "name" on titlebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1796354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796354] Re: Document viewer (Evince) shows document "title" and not document "name" on titlebar
This was the same issue that was discussed in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/78584 and it was fixed in the following versions of Evince, but now it has reappeard (at least to me) -- 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/1796354 Title: Document viewer (Evince) shows document "title" and not document "name" on titlebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1796354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 78584] Re: Evince title should be adaptable
The issue seems to be reappeared (at least to me) in Bionic, with Evince 3.28.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/78584 Title: Evince title should be adaptable To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/78584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705188] Re: GIMP color picker does not work in Wayland
The upstream bug was migrated to Gitlab. The link to the gitlab bug is https://gitlab.gnome.org/GNOME/gimp/issues/1074 now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1705188 Title: GIMP color picker does not work in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1705188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
I switched from unity to gnome with Ubuntu 18.04, it's quite annoying to have to go to the other monitor just to adjust the audio volume. I think all monitors should have the top bar by default. I agree that login out of the session is not very frequent but adjusting the volume is a very frequent action on the other hand ... -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
Hello Bin, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.3-0ubuntu18.04.2 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! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
OK, I just read a half uninformed rant in #ubuntu-release from last night. It would be good to have those rants in future with some of the parties involved up to that point. We could have avoided that mix up with the provides, for example. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
Some coordination would have been nice. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
infinity wants new uploads of all the packages that have had removed binaries on s390x so that 1) the build log shows correctly as dep-wait or failed and 2) so that the s390x binaries don't accidentally get copied back to the archive. I uploaded some of these to the cosmic unapproved queue already. -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774177] Re: Personal scaling settings not used on the unlock screen
This bug doesn't exist on Wayland. It does seem like GNOME developers don't care about Xorg anymore and these kinds of bugs won't get fixed. -- 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/1774177 Title: Personal scaling settings not used on the unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774177] Re: Personal scaling settings not used on the unlock screen
This happens to me 100% of the time now and is extremely annoying. Issues like this have made the 18.04 GNOME transition a clear step back in desktop polish. -- 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/1774177 Title: Personal scaling settings not used on the unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755536] Re: gnome-control-center is not open ubuntu 18.04
This bug affects me too. Downloaded 18.04.01 today (5/10/2018) Fresh install, no changes at installation (next next next ...) Log in, trying to open settings -> Send Error report trying to run gnome-control-center from terminal -> Core dump trying to remove gnome-control-center (is removed with ubuntu-desktop as well) sudo apt remove gnome-control-center sudo apt autoremove sudo apt install gnome-control-center Still not working. same results as above -- 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/1755536 Title: gnome-control-center is not open ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755536/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796265] Re: Gnome-shell unusable after unlocking screen
Addon: This seems to affect only the X11 version, the Wayland session appears to lock and unlock just fine, so I'm switching to that for now. -- 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/1796265 Title: Gnome-shell unusable after unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796265] [NEW] Gnome-shell unusable after unlocking screen
Public bug reported: After locking the screen, unlocking it again does not return me to a properly working gnome-shell. I can see the desktop background and the top panel (which is responsive). However I cannot access the activities overview, and the Ubuntu dock is missing. One time I noticed that the search field from the activities overview was visible, and it was possible to search for an application. The search did return results, and it was possible to start applications, but they did not show up on the screen. In some cases I could run gnome-shell -r, but this would end the whole session and return me to the login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 12:44:13 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-03 (458 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- 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/1796265 Title: Gnome-shell unusable after unlocking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
I did that: https://gitlab.gnome.org/GNOME/gjs/issues/212 -- 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/1796238 Title: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
I did make this happen with 1.54.0 and 1.54.1 (about to be uploaded). But only when using "debugexit" - normal logout, reboot and fast user switching all worked without crashing. Can you confirm that? I would like to see this forwarded to (gjs initially) upstream, please. -- 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/1796238 Title: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792365] Re: On-screen keyboard works only in the login screen and the activities menu
** Summary changed: - On-screen keyboard doesn't work outside of Ubuntu's text fields + On-screen keyboard works only in the login screen and the activities menu -- 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/1792365 Title: On-screen keyboard works only in the login screen and the activities menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1792365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794721] Re: Remove gjs from s390x
This is done now. I was planning to look into some followup uploads to make sure things don't build uninstallable binaries (BD: gjs or similar) ** Changed in: gjs (Ubuntu) Status: Confirmed => Fix Released -- 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/1794721 Title: Remove gjs from s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796251] [NEW] gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- 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/1796251 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796252] Re: gnome-shell crashed with assertion failure: ../../src/hb-object-private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]...
** Summary changed: - /usr/bin/gnome-shell:gnome-shell: ../../src/hb-object-private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]: \343\202\242\343\202\265\343\203\274\343\202\267\343\203\247\343\203\263 `hb_object_is_valid (obj)' \343\201\253\345\244\261\346\225\227\343\201\227\343\201\276\343\201\227\343\201\237\343\200\202 + gnome-shell crashed with assertion failure: ../../src/hb-object-private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]... -- 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/1796252 Title: gnome-shell crashed with assertion failure: ../../src/hb-object- private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796252] [NEW] gnome-shell crashed with assertion failure: ../../src/hb-object-private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]...
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9afb0dcc7f78b5b850ee48662ccf8311043a89ec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- 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/1796252 Title: gnome-shell crashed with assertion failure: ../../src/hb-object- private.hh:253: Type* hb_object_reference(Type*) [with Type = hb_face_t]... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to
** Summary changed: - /usr/bin/gnome-shell:11:__strlen_avx2:real_save_png:gdk_pixbuf__png_image_save_to_callback:gdk_pixbuf_real_save_to_callback:gdk_pixbuf_save_to_callbackv + gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() -- 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/1796251 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794638] Re: gdm kills itself (on purpose) immediately after switching away from tty1
Just a little confusion over terminology... The gdm3 process should stay running. Please use 'ps' to verify it does. The thing that provides the GUI and that gets killed and restarted is the 'gnome-shell' process owned by the 'gdm' user. Is that what you see? -- 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/1794638 Title: gdm kills itself (on purpose) immediately after switching away from tty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
** Tags added: rls-cc-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/1796238 Title: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794638] Re: gdm crashes immediately after login
Ok, so it looks like this is intended behaviour, ie to save memory? When I first reported the bug, gdm3 didn't reappear when I switched to tty1, but now it reappears after five seconds or so of showing a blank screen. It then dies shortly after I switch back to tty2. It's just a pity it takes so long to reappear. ** Summary changed: - gdm crashes immediately after login + gdm kills itself (on purpose) immediately after switching away from tty1 ** Changed in: gdm3 (Ubuntu) Status: Incomplete => 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/1794638 Title: gdm kills itself (on purpose) immediately after switching away from tty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
** Description changed: - mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) + mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52 which + was still the latest yesterday) Steps to reproduce: 1. Start gnome-shell (master) 2. Super+A to show applications 3. Alt+F2 and type "debugexit" to exit cleanly. Backtrace: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 161 ./js/src/vm/JSContext.h: No such file or directory. [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))] (gdb) bt #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 #1 0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834 #2 0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418 #3 0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x55d07921beb0, args=..., construct=) at ./js/src/vm/Interpreter.cpp:490 #4 0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle) (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=..., thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536 #5 0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., rval=...) at ./debian/build/dist/include/js/RootingAPI.h:1128 #6 0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0 #7 0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0 #8 0x7f3bf7625573 in () at /usr/lib/libgjs.so.0 #9 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f3bf7f788f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0) at clutter-actor.c:5932 #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-widget.c:354 #15 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-bin.c:188 #16 0x7f3bf7f6c448 in g_object_run_dispose () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0) at clutter-actor.c:8615 #18 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0) at clutter-actor.c:19002 #19 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0) at clutter-actor.c:6264 #20 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7f3bf7f78c4a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795a9ba0) at clutter-actor.c:5932 #25 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795a9ba0) at ../src/st/st-widget.c:354 #26 0x7f3bf7f6c448 in g_object_run_dispose () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795a9ba0) at clutter-actor.c:8615 #28 0x7f3bf7025cf5 in st_bin_dispose (gobject=0x55d0795a8260) at ../src/st/st-bin.c:185 #29 0x7f3bf7f6ac13 in g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #30 0x7f3bf7610f5e in ObjectInstance::release_native_object() () at /usr/lib/libgjs.so.0 #31 0x7f3bf7618496 in ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 #32 0x7f3bf76140cc in ObjectInstance::remove_wrapped_gobjects_if(std::function, std::function) () at /usr/lib/libgjs.so.0 #33 0x7f3bf76141a4 in () at /usr/lib/libgjs.so.0 -- 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/1796238 Title: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796238/+subscriptions --
[Bug 1768967] Re: Screen randomly flips 180 degrees
*** This bug is a duplicate of bug 1726160 *** https://bugs.launchpad.net/bugs/1726160 Sounds like it might be a continuation of bug bug 1726160. ** This bug has been marked a duplicate of bug 1726160 On login, display rotates to wrong orientation [HP Pavilion] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1768967 Title: Screen randomly flips 180 degrees To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1768967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Confirmed by duplicate bug 1768967. ** Changed in: systemd (Ubuntu) Status: Won't Fix => Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
Too hard right now. If this affects regular users then the crash should start showing up soon on errors.ubuntu.com. So I will wait and see. ** Changed in: mozjs60 (Ubuntu) Status: New => Incomplete ** Changed in: gjs (Ubuntu) Status: New => Incomplete -- 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/1796238 Title: [regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794638] Re: gdm crashes immediately after login
Do you have evidence of a "crash"? If not then please reword the bug to describe the problem more specifically. I know the new version of gdm3 in cosmic is a bit buggy, related to it trying to kill/restart its own gnome-shell instance on VT switch changes. That's intended as a memory-saving feature, but it is causing a few bugs even still. Maybe the login screen is accidentally on a different tty. I've seen it do that a few times. Try switching to other ones in your search for the login screen. Not just VT1. -- 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/1794638 Title: gdm crashes immediately after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796240] Re: gnome-shell crashed with SIGSEGV in _IO_vfprintf_internal() from __GI___vasprintf_chk() from vasprintf() from g_vasprintf() from g_strdup_vprintf()
** Summary changed: - /usr/bin/gnome-shell:11:_IO_vfprintf_internal:__GI___vasprintf_chk:vasprintf:g_vasprintf:g_strdup_vprintf + gnome-shell crashed with SIGSEGV in _IO_vfprintf_internal() from __GI___vasprintf_chk() from vasprintf() from g_vasprintf() from g_strdup_vprintf() -- 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/1796240 Title: gnome-shell crashed with SIGSEGV in _IO_vfprintf_internal() from __GI___vasprintf_chk() from vasprintf() from g_vasprintf() from g_strdup_vprintf() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796240/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796240] [NEW] gnome-shell crashed with SIGSEGV in _IO_vfprintf_internal() from __GI___vasprintf_chk() from vasprintf() from g_vasprintf() from g_strdup_vprintf()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d450aec7506b529002bdfed41acde7afd6cdc0ab contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic trusty -- 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/1796240 Title: gnome-shell crashed with SIGSEGV in _IO_vfprintf_internal() from __GI___vasprintf_chk() from vasprintf() from g_vasprintf() from g_strdup_vprintf() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796240/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796239] [NEW] /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:gdk_x11_display_error_trap_pop_internal:gdk_x11_display_error_trap_pop:meta_x11_error_trap_pop_with_return
*** This bug is a duplicate of bug 1788483 *** https://bugs.launchpad.net/bugs/1788483 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- 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/1796239 Title: /usr/bin/gnome- shell:6:g_assertion_message:g_assertion_message_expr:gdk_x11_display_error_trap_pop_internal:gdk_x11_display_error_trap_pop:meta_x11_error_trap_pop_with_return To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796239/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796239] Re: /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:gdk_x11_display_error_trap_pop_internal:gdk_x11_display_error_trap_pop:meta_x11_error_trap_pop_with_return
*** This bug is a duplicate of bug 1788483 ***
https://bugs.launchpad.net/bugs/1788483
** This bug has been marked a duplicate of bug 1788483
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()
--
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/1796239
Title:
/usr/bin/gnome-
shell:6:g_assertion_message:g_assertion_message_expr:gdk_x11_display_error_trap_pop_internal:gdk_x11_display_error_trap_pop:meta_x11_error_trap_pop_with_return
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796239/+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()
Tracking in:
https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16
** Description changed:
+ https://errors.ubuntu.com/problem/7760395cb5d46c6f66918a261675bfdee38b7d16
https://gitlab.gnome.org/GNOME/mutter/issues/294
---
Crash happened when I tried to use Wacom stylus on Dell 7285
touchscreen.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.29.90-2ubuntu1
Uname: Linux 4.18.3-041803-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Aug 23 03:55:08 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-04-20 (124 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
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
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
?? ()
Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: Upgraded to cosmic on 2018-04-20 (124 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty
--
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/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 1794638] Re: gdm crashes immediately after login
This is pretty easy to reproduce: the latest daily build (Oct 4) of cosmic does it on first reboot after installation in a VM: as on my system, loginctl shows only a single session present. There are no crash files in /var/crash, and there are no errors logged at ubuntu.com. Is this expected behaviour, then? -- 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/1794638 Title: gdm crashes immediately after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796238] Re: [regression] mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52)
** Description changed: mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) Program terminated with signal SIGSEGV, Segmentation fault. - #0 0x7f3bf4033a4e in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #1 0x7f3bf403eb06 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #2 0x7f3bf403f0d1 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #3 0x7f3bf403f339 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #4 0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #5 0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0 - #6 0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0 - #7 0x7f3bf7625573 in () at /usr/lib/libgjs.so.0 - #8 0x7f3bf7f65b6d in g_closure_invoke () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #9 0x7f3bf7f788f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #10 0x7f3bf7f81882 in g_signal_emit_valist () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #11 0x7f3bf7f81ecf in g_signal_emit () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #12 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0) - at clutter-actor.c:5932 - #13 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0) - at ../src/st/st-widget.c:354 - #14 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0) - at ../src/st/st-bin.c:188 - #15 0x7f3bf7f6c448 in g_object_run_dispose () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #16 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0) - at clutter-actor.c:8615 - #17 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0) - at clutter-actor.c:19002 - #18 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0) - at clutter-actor.c:6264 - #19 0x7f3bf7f65b6d in g_closure_invoke () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #20 0x7f3bf7f78c4a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #21 0x7f3bf7f81882 in g_signal_emit_valist () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #22 0x7f3bf7f81ecf in g_signal_emit () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #23 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795a9ba0) - at clutter-actor.c:5932 - #24 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795a9ba0) - at ../src/st/st-widget.c:354 - #25 0x7f3bf7f6c448 in g_object_run_dispose () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #26 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795a9ba0) - at clutter-actor.c:8615 - #27 0x7f3bf7025cf5 in st_bin_dispose (gobject=0x55d0795a8260) - at ../src/st/st-bin.c:185 - #28 0x7f3bf7f6ac13 in g_object_unref () - at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - #29 0x7f3bf7610f5e in ObjectInstance::release_native_object() () - at /usr/lib/libgjs.so.0 - #30 0x7f3bf7618496 in ObjectInstance::disassociate_js_gobject() () - at /usr/lib/libgjs.so.0 - #31 0x7f3bf76140cc in ObjectInstance::remove_wrapped_gobjects_if(std::function, std::function) () - at /usr/lib/libgjs.so.0 - #32 0x7f3bf76141a4 in () at /usr/lib/libgjs.so.0 - #33 0x7f3bf46596a2 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #34 0x7f3bf46313a4 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #35 0x7f3bf463d73a in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #36 0x7f3bf463e2c3 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #37 0x7f3bf465eb69 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #38 0x7f3bf465fb08 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #39 0x7f3bf465ffd8 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #40 0x7f3bf466015b in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #41 0x7f3bf449eee9 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #42 0x7f3bf44371fb in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - #43 0x7f3bf7628899 in () at /usr/lib/libgjs.so.0 - #44 0x7f3bf7f6ac13 in g_object_unref () + #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., + pc=, script=..., fp=, cx=) + at ./js/src/vm/JSContext.h:161 + 161 ./js/src/vm/JSContext.h: No such file or directory. + [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))] + (gdb) bt + #0 0x7f3bf4033a4e in GetPropertyOperation + (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 + #1 0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&) + (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834 + #2 0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&) + (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418 + #3 0x7f3bf403f0d1 in
[Bug 1796238] [NEW] [regression] mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52)
Public bug reported: mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 161 ./js/src/vm/JSContext.h: No such file or directory. [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))] (gdb) bt #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 #1 0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834 #2 0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418 #3 0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x55d07921beb0, args=..., construct=) at ./js/src/vm/Interpreter.cpp:490 #4 0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle) (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=..., thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536 #5 0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., rval=...) at ./debian/build/dist/include/js/RootingAPI.h:1128 #6 0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0 #7 0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0 #8 0x7f3bf7625573 in () at /usr/lib/libgjs.so.0 #9 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f3bf7f788f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0) at clutter-actor.c:5932 #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-widget.c:354 #15 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-bin.c:188 #16 0x7f3bf7f6c448 in g_object_run_dispose () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0) at clutter-actor.c:8615 #18 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0) at clutter-actor.c:19002 #19 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0) at clutter-actor.c:6264 #20 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7f3bf7f78c4a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795a9ba0) at clutter-actor.c:5932 #25 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795a9ba0) at ../src/st/st-widget.c:354 #26 0x7f3bf7f6c448 in g_object_run_dispose () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795a9ba0) at clutter-actor.c:8615 #28 0x7f3bf7025cf5 in st_bin_dispose (gobject=0x55d0795a8260) at ../src/st/st-bin.c:185 #29 0x7f3bf7f6ac13 in g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #30 0x7f3bf7610f5e in ObjectInstance::release_native_object() () at /usr/lib/libgjs.so.0 #31 0x7f3bf7618496 in ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 #32 0x7f3bf76140cc in ObjectInstance::remove_wrapped_gobjects_if(std::function, std::function) () at /usr/lib/libgjs.so.0 #33 0x7f3bf76141a4 in () at /usr/lib/libgjs.so.0 ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Affects: mozjs60 (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic regression ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) + [regression] mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) ** Description changed: mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52) + Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f3bf4033a4e in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 #1 0x7f3bf403eb06 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 #2 0x7f3bf403f0d1 in () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 #3 0x7f3bf403f339 in
