[Bug 1832988] Re: Intel 8260 Bluetooth not working

2019-06-16 Thread Kai-Heng Feng
Please test this kernel: https://people.canonical.com/~khfeng/lp1832988/ -- 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/1832988 Title: Intel 8260 Bluetooth not working To

[Bug 1825066] Re: gsd-xsettings have tons of error in syslog

2019-06-16 Thread Launchpad Bug Tracker
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1825006] Re: snapp apps not showing in software center

2019-06-16 Thread Launchpad Bug Tracker
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Eric Desrochers
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) -- 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/1832138 Title: Login screen never

[Bug 1806697] Re: Status of interface connections not properly updated in the UI

2019-06-16 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu8 --- gnome-software (3.30.6-2ubuntu8) eoan; urgency=medium * debian/patches/0014-Add-a-basic-permissions-system.patch: - Fix interface connections not showing correct state (LP: #1806697) -- Robert Ancell

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
The attached RfKill.txt seems to suggest that Bluetooth is only turned off in software. So maybe this is just a gnome-shell GUI bug, or gnome- bluetooth. To confirm this, please try turning it on by running this command in a terminal: rfkill unblock 0 ** Also affects: gnome-shell (Ubuntu)

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
If the above command doesn't work then I would next focus on a possible kernel problem in: [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) ** Summary changed: - Bluetooth not working + Intel 8260 Bluetooth

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Daniel van Vugt
Pat, Re comment #19, your crash (hang) reports there seem to show the gnome- shell process behaving normally (in poll) and not stuck at all. That doesn't tell us much but it would support the theory in comment #31. ** Summary changed: - Login screen never appears on vmwgfx but installing kernel

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it

2019-06-16 Thread Daniel van Vugt
Interesting one of the commits mentioned above: 37efe80ce85f drm/vmwgfx: use monotonic event timestamps (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f) is related to what I changed in the latest update to mutter:

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-16 Thread Daniel van Vugt
Indeed there was a kernel update to 18.04 around the same time as the mutter update which I thought was causing this bug. ** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Bionic) ** No longer affects: mutter (Ubuntu Eoan) ** Also affects: linux (Ubuntu Eoan)

[Bug 1832959] Re: Wrong cursor size after screensaver

2019-06-16 Thread Daniel van Vugt
** Tags added: cursor hidpi ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Wrong cursor size after screensaver + [hidpi] Cursor is too small after screensaver ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received

[Bug 1832946] Re: Gnome Shell works the worst after I will launch some apps

2019-06-16 Thread Daniel van Vugt
It sounds like you're trying to describe general frame skipping and performance degradation as more apps are opened. Can you please put the problem into words so we can be sure what the problem is you are reporting? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags

[Bug 1832943] Re: When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background

2019-06-16 Thread Daniel van Vugt
Can you please reword that? I don't understand (and can't see in the video) what the problem is here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in

[Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1800196 *** https://bugs.launchpad.net/bugs/1800196 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1800196, so it is being marked as such. Please

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Tags added: regression-update -- 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/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
It appears this crash is in: /home/gjm/.local/share/gnome- shell/extensions/wsmat...@martin.zurowietz.de which is not part of Ubuntu, so we can't handle it here. Sorry. I suggest you uninstall that extension to avoid the crash. ** Summary changed: - Gnome-shell crashes frequently +

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
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

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-16 Thread Daniel van Vugt
Thanks. Since gnome-shell provides all the graphics (even the lock screen), this bug is now assigned to gnome-shell only. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** No longer affects: gdm3 (Ubuntu) --

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1827450] Re: Some context menu entries are unavailable in list view if folder has many items for nautilus 1:3.26.4-0~ubuntu18.04.4

2019-06-16 Thread widon1104
I find a good way to solve this problem in ubuntu18.04: use dde file manager create by deepin sudo add-apt-repository ppa:leaeasy/dde sudo apt install dde dde-file-manager I think dde-file-manager is better than nautilus. -- You received this bug notification because you are a member of Ubuntu

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Summary changed: - gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows + gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() -- You received this

[Bug 1753884] Re: session logout after suspend

2019-06-16 Thread Daniel van Vugt
Unfortunately we can't backport a fix which we don't know the location of. And I don't see any links to a patch here. Also, we generally don't support/patch gnome-shell on Ubuntu releases older than 18.04. Anyway, this bug is closed and we can't be sure you are experiencing the exact same issue.

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-16 Thread Daniel van Vugt
I'm not sure monitors.xml is any more useful than the xrandr output we already get... unless xrandr output is missing from crash bugs? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-06-16 Thread Gregory Orange
Regarding #17 and the bug (issue) report at Seahorse Gitlab, the latest comment is that Seahorse 3.20.0 which is the latest available on Ubuntu 18.04, is "an ancient version". Can 18.04 receive a newer version such that upstream can be brought into the issue if it persists with that? -- You

[Bug 1833011] [NEW] rotating a 70MB TGA image

2019-06-16 Thread Kunst Uber Alles
Public bug reported: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none

[Bug 1822380] Re: Thunar right-click menu not expanded

2019-06-16 Thread Theo Linkspfeifer
A workaround is not a proper fix. Would it not make more sense to revert the GTK commit which broke the menu behavior? ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is