[Bug 1905519] [NEW] Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using some
Public bug reported: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905513] Re: Mouse does not respect primary/secondary button settings after being disconnected and reconnected.
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 ** This bug has been marked a duplicate of bug 1899206 Input device settings not applied on hotplug/reconnect/resume in Xorg sessions -- 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/1905513 Title: Mouse does not respect primary/secondary button settings after being disconnected and reconnected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881684] Re: GIMP Python Plugins Won't Run in Ubuntu 20.04
** Changed in: gimp (Debian) Status: Unknown => Fix Released -- 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/1881684 Title: GIMP Python Plugins Won't Run in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1881684/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905513] [NEW] Mouse does not respect primary/secondary button settings after being disconnected and reconnected.
Public bug reported: After installing 20.04, in the gnome control center I selected the right mouse button to be the primary button. When I unplug the mouse and replug it in, the right mouse button is no longer the primary button. When I look at the gnome control center, the setting says that the right mouse button is the primary button. To get the right button as the primary button I need to click on the GUI control to make the left button primary and then on the same control a second time to make the right button primary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108853~20.04~8bcf10e~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 20:43:26 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-10-04 (2244 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-12 (12 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1905513 Title: Mouse does not respect primary/secondary button settings after being disconnected and reconnected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Getting frustrated because a bug that has existed so long and is key to network security (connection with SMB1), and has gone ignored for over 1.5 years, is not bad conduct. SMB1 was disabled because of it's egregious security issues, and having no solution for things like this as a result is unacceptable. Yes, I know this is volunteer work, but this ticket should not be marked Triaged as no work has actually been done on it, and quite frankly, this should be marked with a higher priority. This kind of functional behaviour is only going to promote the re-enabling of SMB1 on systems, which is the complete opposite of what anyone wants. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. There is no fix available at the moment there, unsure why it worked for you in 19.10, you could try again to check if that's still working... Upstream would also be a better place to ask if work is planned on a solution -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905084] Re: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard
The bug happens in both X11 and Wayland. -- 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/1905084 Title: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905084] Re: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard
I set up and save the two configurations separately in gnome-control- center, but they are not applied when switching modes with Super+P (or with the dedicated key) or when switching modes in gnome-control-center, the settings don't persist. The settings are saved in ~/.config/monitors.xml when setting up and saving the configuration in gnome-control-center, but they are not applied when switching with Super+P or when switching modes in gnome- control-center, the settings don't persist. Another way to see the bug is to save a mode configuration in gnome- control-center then switch to the same mode using Super+P by pressing Super+P many times without selecting a different mode, the settings will be lost. See the attached screencast. ** Attachment added: "Monitor-conf.webm" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905084/+attachment/5437640/+files/Monitor-conf.webm -- 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/1905084 Title: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
I second that!! This is pathetic. On November 24, 2020 3:58:16 PM EST, BloodyIron <1828...@bugs.launchpad.net> wrote: >I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? >This >issue was reported over 1.5 YEARS ago and a fix was already made, but >HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT >VERSION. WHEN WILL THIS BE FIXED? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1828107 > >Title: > gvfs can't list shares from smb servers that disabled SMB1 > >Status in gvfs: > Unknown >Status in gvfs package in Ubuntu: > Triaged > >Bug description: > After bug #1778322 is fixed (just needs a gvfs rebuild with newer > samba), samba machines will start to show up again in the "windows > network" tab in nautilus. But if a server has disabled the SMB1 > protocol, nautilus will show an error when that server is clicked on, > instead of showing the shares list. > > Even with SMB1 disabled, it should still be technically possible to > get a share list, since smbclient can do it: > > andreas@nsnx:~$ nmblookup -A 192.168.122.101 > Looking up status of 192.168.122.101 > D-NO-SMB1 <00> - B > D-NO-SMB1 <03> - B > D-NO-SMB1 <20> - B > ..__MSBROWSE__. <01> - B > WORKGROUP <00> - B > WORKGROUP <1d> - B > WORKGROUP <1e> - B > > MAC Address = 00-00-00-00-00-00 > > andreas@nsnx:~$ smbclient -L 192.168.122.101 -N > WARNING: The "syslog" option is deprecated > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > pub_no_smb1 Disk > IPC$IPC IPC Service (d-no-smb1 server (Samba, >Ubuntu)) > Reconnecting with SMB1 for workgroup listing. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Failed to connect with SMB1 -- no workgroup available > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m NT1 > WARNING: The "syslog" option is deprecated > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > >andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U >ubuntu%ubuntu -m SMB2 > WARNING: The "syslog" option is deprecated > Try "help" to get a list of possible commands. > smb: \> dir >. D0 Fri May 3 18:16:38 >2019 >.. D0 Fri May 3 18:15:24 >2019 >hello.txt N 21 Fri May 3 18:16:12 >2019 >hello-from-nsnx.txt A9 Fri May 3 18:16:38 >2019 > > 20509264 blocks of size 1024. 13121800 blocks > available > >To manage notifications about this bug go to: >https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? This issue was reported over 1.5 YEARS ago and a fix was already made, but HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT VERSION. WHEN WILL THIS BE FIXED? -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
An error symbol also appears in the "Shell" in GNOME tweaks, even after reset etc. -- 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/1905186 Title: dock and top bar flashing non-stop at fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf
Thanks Han, that makes sense that the issue is actually in the volume monitor's (lack of) handling for autofs' transitory nature. I'll reassign to that package for further investigation. ** Package changed: autofs (Ubuntu) => gvfs (Ubuntu) -- 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/1855318 Title: autofs tries to find .xdg-volume-info and autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1855318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855318] [NEW] autofs tries to find .xdg-volume-info and autorun.inf
You have been subscribed to a public bug: # automount -f -v Starting automounter version 5.1.5, master map /etc/auto.master using kernel protocol version 5.05 mounted indirect on /home//mnt with timeout 300, freq 75 seconds attempting to mount entry /home//mnt/.xdg-volume-info key ".xdg-volume-info" not found in map source(s). failed to mount /home//mnt/.xdg-volume-info attempting to mount entry /home//mnt/autorun.inf key "autorun.inf" not found in map source(s). failed to mount /home//mnt/autorun.inf /etc/auto.master: +dir:/etc/auto.master.d /etc/auto.master.d: -rw-r--r-- 1 root root 38 Dez 5 19:10 mnt.autofs /etc/auto.master.d/mnt.autofs: /home//mnt file:/etc/auto.mnt /etc/auto.mnt: G -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sg L -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///apps M -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///gs O -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///media P -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///pb T -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///ALLG V -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///SW2 W -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sw X -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///depot Y -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sct-muc Z -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///z Could not find any file "autorun.inf" or ".xdg-volume-info" anywhere on my system. Where do these come from? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: autofs 5.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 5 19:12:38 2019 InstallationDate: Installed on 2019-09-09 (87 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: autofs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- autofs tries to find .xdg-volume-info and autorun.inf https://bugs.launchpad.net/bugs/1855318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904859] Re: [snap] cannot send file from Nautilus
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904859] Re: [snap] cannot send file from Nautilus
Hello Francois, or anyone else affected, Accepted nautilus-sendto into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus- sendto/3.8.6-3ubuntu0.20.04.1 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: nautilus-sendto (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904859] Re: [snap] cannot send file from Nautilus
Hello Francois, or anyone else affected, Accepted nautilus-sendto into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus- sendto/3.8.6-3ubuntu0.20.10.1 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, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: nautilus-sendto (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
How will I check without a dock? -- 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/1905186 Title: dock and top bar flashing non-stop at fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3
** Changed in: flatpak (Ubuntu Groovy) Status: New => In Progress ** Changed in: flatpak (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1904640 Title: [SRU] [groovy] New upstream microrelease flatpak 1.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1904640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3
** Also affects: flatpak (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: flatpak (Ubuntu Groovy) Assignee: (unassigned) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1904640 Title: [SRU] [groovy] New upstream microrelease flatpak 1.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1904640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896393] Re: gedit not responding to keystrokes
Continue to see this problem, both keystroke delay and the mouse wheel response. -- 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/1896393 Title: gedit not responding to keystrokes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899779] Re: Finger Print authentication doesn't work after logout in linux
*** This bug is a duplicate of bug 1875845 *** https://bugs.launchpad.net/bugs/1875845 ** This bug has been marked a duplicate of bug 1875845 keyring cannot be unlocked if used fingerprint to login gnome session -- 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/1899779 Title: Finger Print authentication doesn't work after logout in linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865838] Re: no error displayed on failed fingerprint authentication
** Tags added: fingerprint -- 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/1865838 Title: no error displayed on failed fingerprint authentication To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882884] Re: FP Auth : Multi user Scenario
** Tags added: libfprint ** Tags removed: libfprint ** Tags added: fingerprint -- 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/1882884 Title: FP Auth : Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890958] Re: exfat month modification time increasing by simple consulting with "properties"
*** This bug is a duplicate of bug 1872504 *** https://bugs.launchpad.net/bugs/1872504 ** This bug has been marked a duplicate of bug 1872504 date modified is wrong for files on an exfat formatted drive -- 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/1890958 Title: exfat month modification time increasing by simple consulting with "properties" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1890958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905414] [NEW] Choosing Headset in Select Audio Device doesn't set input device
Public bug reported:
I'm suffering from a series of audio bugs so I'll try my best to
explain.
Out of the box, the output device in GNOME setting is listed as Kaby
Lake something or other. It works in 20.04 but the headset microphone
isn't detected.
In 18.04 the audio didn't work at all, which required me to use this
workaround in /etc/modprobe.d/alsa-base.conf from
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061:
options snd-hda-intel dmic_detect=0
The headset microphone still doesn't seem to be detected, but at least
the output device has a more understandable name ("Headphones - Built-in
Audio").
Yesterday I ran across this workaround in /etc/modprobe.d/alsa-base.conf
from https://askubuntu.com/a/1233446/18665:
options snd-hda-intel model=alc233-eapd
Now I get a popup every time I plug in my headset, which allows me to
choose whether or not I plugged in headphones or a headset. Great!
Unfortunately, even if I explicitly choose Headset, the input device is
not set to the microphone of my headset.
Thankfully the microphone of my headset is detected in the Gnome sound
settings, so my workflow looks like this:
1. Plug in headset
2. When popup shows click Sound Settings
3. Manually set Input Device to Headset Microphone - Built-in Audio
The primary difference between headphones and a headset, so I would
expect that if I click Headset, the Gnome Input Device would be set to
my headset's microphone. I can't see any other reason why the system
would ask me which I'd plugged in. Am I missing something?
In the meantime I'll try yet another workaround such as
https://askubuntu.com/a/1229519/18665
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 24 08:44:36 2020
InstallationDate: Installed on 2020-03-16 (252 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64
(20200203.1)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to focal on 2020-05-25 (182 days ago)
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-04-24T09:20:26.481270
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
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/1905414
Title:
Choosing Headset in Select Audio Device doesn't set input device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1905414/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903759] Re: [SRU] Update mutter to 3.36.7 in Focal
*** This bug is a duplicate of bug 1903230 *** https://bugs.launchpad.net/bugs/1903230 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1903759 Title: [SRU] Update mutter to 3.36.7 in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904709] Re: Nautilus crash on filtering files over samba mount points
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1904709 Title: Nautilus crash on filtering files over samba mount points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905400] Re: nautilus segfault libgio-2.0.so.0.6600.1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905400 Title: nautilus segfault libgio-2.0.so.0.6600.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1905270] Re: On any external monitors, wayland session has a white block on most part of the screen.
On Tue, Nov 24, 2020 at 11:25 AM Daniel van Vugt <1905...@bugs.launchpad.net> wrote: > Please try logging into 'Ubuntu' instead of 'Ubuntu on Wayland' and tell > us if that has the same issue. Please also then run: > > lspci -kv > lspci.txt > xrandr --verbose > xrandr.txt > journalctl -b0 > journal.txt > > and attach the resulting text files here. > > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1905270 > > Title: > On any external monitors, wayland session has a white block on most > part of the screen. > > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > on any external monitors, wayland session has a white block on most > part of the screen. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: mutter 3.38.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 > Uname: Linux 5.8.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50.1 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Mon Nov 23 20:16:15 2020 > InstallationDate: Installed on 2020-09-16 (67 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) > SourcePackage: mutter > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions > ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/bugs/1905270/+attachment/5437518/+files/xrandr.txt ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1905270/+attachment/5437519/+files/lspci.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1905270/+attachment/5437520/+files/journal.txt -- 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/1905270 Title: On any external monitors, wayland session has a white block on most part of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881684] Re: GIMP Python Plugins Won't Run in Ubuntu 20.04
** Bug watch added: Debian Bug tracker #936611 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936611 ** Also affects: gimp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936611 Importance: Unknown Status: Unknown -- 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/1881684 Title: GIMP Python Plugins Won't Run in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1881684/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904474] Re: Black/purple screen after booting Ubuntu
BTW now the screen also gets stuck as black-screen when I close my laptop lid, wait some seconds and open it again. And the functions keys to regulate screen brightness are working no more (I also tried to change brightness with this tool http://ubuntuhandbook.org/index.php/2017/05/install-brightness- controller-utility-in-ubuntu-16-04-higher/ but it had no effect ...) Could this be related to the above described issue? Best Alexander -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1904474 Title: Black/purple screen after booting Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1904474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904474] Re: Black/purple screen after booting Ubuntu
Thanks for the answer, you can find the the requested file appended. Best Alexander ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5437516/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1904474 Title: Black/purple screen after booting Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1904474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817389] Re: GIMP icon sizes small on large and huge setting
This is still happening on GIMP 2.10.18 on Ubuntu 20.04, and renders GIMP pretty unusable on a 4K display -- 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/1817389 Title: GIMP icon sizes small on large and huge setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1817389/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905400] [NEW] nautilus segfault libgio-2.0.so.0.6600.1
Public bug reported: Hi Guys, Some nautilus segfaulting: [ 3337.426167] nautilus[7770]: segfault at 20 ip 7f987a903844 sp 7fffeb101b08 error 4 in libgio-2.0.so.0.6600.1[7f987a852000+119000] [ 5551.902495] nautilus[10777]: segfault at 20 ip 7f7c0c502844 sp 7ffe513a3178 error 4 in libgio-2.0.so.0.6600.1[7f7c0c451000+119000] Packages: libnautilus-extension1a:amd64 1:3.38.1-1ubuntu1 nautilus 1:3.38.1-1ubuntu1 nautilus-data 1:3.38.1-1ubuntu1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-sendto 3.8.6-3 nautilus-share 0.7.3-2ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Nov 24 12:37:57 2020 InstallationDate: Installed on 2018-01-01 (1057 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2019-10-19 (401 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-01-18T18:05:44.880717 usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1905400 Title: nautilus segfault libgio-2.0.so.0.6600.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868332] Re: Scrolling jumps after switching windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1868332 Title: Scrolling jumps after switching windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1868332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904859] Re: [snap] cannot send file from Nautilus
Ok Sébastien, I confirm it works well too in my Focal. Please consider another TB snap send-to bug here: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1898206 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904859] Re: [snap] cannot send file from Nautilus
This bug was fixed in the package nautilus-sendto - 3.8.6-3.1 --- nautilus-sendto (3.8.6-3.1) unstable; urgency=medium * debian/patches/gitlab_thunderbird_cmd.patch: - remove an old workaround for thunderbird, it's not useful anymore and is creating problem with the snap cmd (lp: #1904859) -- Sebastien Bacher Mon, 23 Nov 2020 20:31:53 +0100 ** Changed in: nautilus-sendto (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10
Thanks! ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #190 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/190 ** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/190 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1901286 Title: gnome-disk-image-mounter fails after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1901286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905100] Re: Cover art not shown for file which has a cover art
Great, there is a known issue that if thumbnailing fails for some reason then it will never be retried again. Next time you get the problem feel free to comment with the 'journalctl -b 0' log from the session included ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
And this one too: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1507 ** Changed in: gnome-shell (Ubuntu Groovy) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu Groovy) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Status: Confirmed => 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
OK, I've proposed a fix for the root cause here: https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/merge_requests/191 but it still scares me how easily StBin failed to notice such a mistake so I might also add some error checking in gnome-shell to prevent similar mistakes going unnoticed. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgrou
I'm actually not sure if this bug requires the same or a different fix to bug 1898005. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1898910 Title: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Confirmed => In Progress -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5437407/+files/lspci.txt -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
Interesting talking about devil... It happened right now. Remmina suddenly froze. This time I also lost mouse (no mouse pointer) and after few seconds also music stopped playing on my PC, this indicates this time whole system froze. For #22 for step 2 I am attaching files. ** Attachment added: "freshprevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5437406/+files/freshprevboot.txt -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
