[Bug 1910912] Re: Settings not applied to USB touchpad and keyboard
This bug has been fixed with mutter (3.36.7+git20201123-0.20.04.1) ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910912 Title: Settings not applied to USB touchpad and keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1910912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910912] [NEW] Settings not applied to USB touchpad and keyboard
Public bug reported: Bug originated after doing a 18.04.5 LTS to 20.04.1 LTS upgrade. The settings from gnome-control-center are not getting applied for external USB devices. For a USB touchpad I've spotted this with the following: org.gnome.desktop.peripherals.touchpad tap-and-drag org.gnome.desktop.peripherals.touchpad tap-to-click For a USB keyboard I've observed this for the input language. I have EN and BG as input languages, but if I plug in an external I can only type in EN (the default language). The fix for both is to go in gnome control center (or gsettings) and do a toggle. I've made a small screencast to demonstrate the issue. https://drive.google.com/file/d/1mP92waNjUmU3rYB6FaHgyow0WzXOItLd/view The system is a Dell XPS 9550 and the Touchpad is a Logitech T650 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 10 17:05:31 2021 InstallationDate: Installed on 2016-04-29 (1716 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-09-29 (102 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-22T11:19:11.812508 ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910912 Title: Settings not applied to USB touchpad and keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1910912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
Hi Colin Ian King, I tested the revert kernels from here https://kernel.ubuntu.com/~cking/lp-1853044/. The results from Powertop can be found here https://postimg.cc/gallery/TTmWSfX. I also included the latest 5.3.0-61 kernel for reference. The test system is an XPS 9550 with HD Graphics 530, Intel Core i7 6700HQ For all kernels I booted up, ran powertop, waited to idle and made screenshots. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
Unfortunately this bug is back with linux-5.3.0-53.47. It got reintroduced somewhere between linux-5.3.0-53.47 and 5.3.0-51.44. System is Dell XPS 9550 with Skylake HD Graphics 530. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
Hi, I've been running without the gpaste extension for a few weeks and gnome-shell no longer crashes. So I guess this bug should be reassigned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
Hi, This crash is still present in the latest gnome-shell version 3.28.4-0ubuntu18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717673] Re: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()
This bug is still present on up to date Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717673 Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1717673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812827] [NEW] gnome-shell crashed with SIGSEGV in meta_window_actor_is_destroyed()
*** This bug is a duplicate of bug 1812527 *** https://bugs.launchpad.net/bugs/1812527 Private bug reported: Behaviour started after upgrading to 1.52.5-0ubuntu18.04.1 Steps to reproduce are: 1. Launch an Android emulator from Android Studio: I used all default settings and Andoid Pie x86 image 2. Change workspace via hotkey 3. Result is gnome-shell crashes and resets Workaround is to run: sudo apt install libgjs0g=1.52.1-1ubuntu1 sudo apt install gjs=1.52.1-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 10:23:29 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1544015290 InstallationDate: Installed on 2016-04-29 (997 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/kstoilov SegvAnalysis: Segfault happened at: 0x7f03ff83dfe0 : mov 0x28(%rdi),%rax PC (0x7f03ff83dfe0) ok source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_actor_is_destroyed () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_actor_is_destroyed() UpgradeStatus: Upgraded to bionic on 2018-08-04 (170 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev sambashare sudo ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash bionic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812827 Title: gnome-shell crashed with SIGSEGV in meta_window_actor_is_destroyed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812780] [NEW] Gnome Shell crashes when Android emulator started
Public bug reported: I am filing this bug with gjs because the behaviour started after upgrading to 1.52.5-0ubuntu18.04.1 Steps to reproduce are: 1. Launch an Android emulator from Android Studio: I used all default settings and Andoid Pie x86 image 2. Change workspace via hotkey 3. Result is gnome-shell crashes and resets Workaround is to run: sudo apt install libgjs0g=1.52.1-1ubuntu1 sudo apt install gjs=1.52.1-1ubuntu1 This is from /var/log/syslog at the time of the gnome-shell crash Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat' Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat' Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,00" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: Object Gio.Settings (0x55703194e880), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: g_object_run_dispose: assertion 'G_IS_OBJECT (object)' failed Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for context 0x55702bd7d340 == Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c135080 i resource:///org/gnome/shell/ui/messageTray.js:173 (0x7f5560090ab0 @ 22) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c1e680 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134fe0 i resource:///org/gnome/shell/ui/messageTray.js:812 (0x7f55600a0098 @ 28) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c1f260 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x55702c134f40 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:100 (0x7f5542c43808 @ 42) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c1fe40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #6 0x55702c134ec8 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:44 (0x7f5542c43340 @ 17) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #7 0x7ffc05c21150 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f5542dd2230 @ 386) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #8 0x55702c134e40 i resource:///org/gnome/shell/ui/messageTray.js:479 (0x7f556009db38 @ 22) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #9 0x7ffc05c21da0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #10 0x55702c134dc0 i resource:///org/gnome/shell/ui/calendar.js:801 (0x7f55600a9ef0 @ 22) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #11 0x7ffc05c22990 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #12 0x7ffc05c22a60 b self-hosted:918 (0x7f5542df12b8 @ 394) Jan 22 06:01:55 kostadin-XPS gnome-shell[16305]: Object Meta.WindowActor (0x55702f200b80), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for context 0x55702bd7d340 == Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c134e48 i resource:///org/gnome/shell/ui/windowManager.js:1787 (0x7f5542b24670 @ 113) Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c21040 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71) Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134dc0 i resource:///org/gnome/shell/ui/tweener.js:112 (0x7f5542dc8e68 @ 37) Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c22ab0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f5542dd2b38 @ 54) Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x7ffc05c22c00 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f5542dd2bc0 @ 1626) Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c22cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f5542dd2c48 @ 100) Jan 22 06:01:55 kostadin-XPS
[Bug 1786094] [NEW] Dell XPS 9550 does not suspend
Public bug reported: After a recent kernel update I have had several suspend failures on a Dell XPS 9550. Instead of suspending as usual the system stays on and is unresponsive with a black screen. Strangely enough this does NOT happen on every suspend, it usually happens after several successful suspend-resume cycle. The issue started with a kernel upgrade to linux-image-4.15.0-29-generic on Ubuntu 16.04.5. I have subsequently upgraded to kernel linux- image-4.15.0-30-generic on Ubuntu 18.04.1 where the issue persists. The workaround for me at the moment is to install and use linux- image-4.15.0-24-generic. Laptop is running the latest Dell BIOS, currently with no Nvidia proprietary drivers. The issue was also present with the nvidia proprietary drivers from the Ubuntu 16.04.5 repositories. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kstoilov 2508 F...m pulseaudio /dev/snd/controlC0: kstoilov 2508 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 8 21:44:40 2018 InstallationDate: Installed on 2016-04-29 (831 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=UUID=539a3d5f-4f1b-4fdc-b884-75fb289fe957 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-04 (4 days ago) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd02/23/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786094 Title: Dell XPS 9550 does not suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I am experiencing the same problem on a Dell XPS 9550 with a GTX 960M. I just upgraded from 16.04 where prime-select was able to power the graphics card down with bbswitch. Strangely enough even nouveau is perfectly capable of powering down the card if it does not have nouveau.run-pm=0 which disables the power management feature. Sadly this is in the grub config generated by prime-select intel. For now i have removed the nvidia proprietary drivers to get back decent battery life. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Can confirm this issue on an Asus T300 Chi and a Dell XPS 9360 on up to date Ubuntu 18.04 installations. I think this is the upstream bug report: https://github.com/micheleg/dash-to-dock/issues/128 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #128 https://github.com/micheleg/dash-to-dock/issues/128 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Here is also a nice video demonstrating the issue: https://www.youtube.com/watch?v=zQCOO-9HZvU It runs Fedora, but the behaviour is exactly the same on Bionic as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
@vanvugt could you try the steps I posted in #46. I can reliably reproduce this on a clean install of Bionic daily in a VM. No extra extensions, just opening window previews with Super multiple times (two windows open). Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
There is a memory leak generating window previews on gnome shell and since pressing the Super key generates windows previews the memory usage grows exponentially. For me Gnome Shell eats about 100-150 MB every day I leave it running. I tested this both on an Intel graphics machine and on a VM, in both Artful and Bionic. Both times clean install. 1. on a clean boot open System Monitor and Terminal side by side (or System Monitor and any other window) 2. press Super wait for the window preview and then press ESC (repeat this several times) 3. Observe the memory usage for Gnome Shell System Monitor grow You can also reproduce this by installing the Alternate Tab extension (https://extensions.gnome.org/extension/15/alternatetab/) which also generates window previews. 1. Alt+Tab between Terminal and System Monitor and watch the Gnome Shell memory usage grow every time. Another user on reddit also came to a similar conclusion: https://www.reddit.com/r/gnome/comments/7teono/possible_fix_to_improve_gnome_lag/ Effectively gnome shell becomes unusable even on 8 GB of RAM after a week of usage. I solve the issue by running ALT+F2 and 'r' every morning. People who are not technical of course will not do this and have a horrible experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
This bug is still present in Ubuntu 17.10 Artful. I have experienced it after waking up from suspend on a Dell XPS 9360 with a clean Ubuntu install. Here is the dump: Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.661562] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.694143] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.726760] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.759262] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.791956] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.824470] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.857075] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.889653] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.922200] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.954870] ath10k_pci :3a:00.0: failed to wake target for read32 at 0x0003a028: -110 Dec 26 17:52:04 sabina-XPS-13 kernel: [30477.569491] ath10k_pci :3a:00.0: failed to read device register, device is gone Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669015] ath10k_pci :3a:00.0: firmware crashed! (uuid 283c1469-65cc-447c-a08d-c723b4f1387a) Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669020] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669021] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669389] ath10k_pci :3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559 Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669634] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 07ee144e Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669635] ath10k_pci :3a:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.172084] ath10k_pci :3a:00.0: failed to read firmware dump area: -16 Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.172087] ath10k_pci :3a:00.0: Copy Engine register dump: Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.302279] ath10k_pci :3a:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.434224] ath10k_pci :3a:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.565730] ath10k_pci :3a:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.695977] ath10k_pci :3a:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.826324] ath10k_pci :3a:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.956700] ath10k_pci :3a:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.086854] ath10k_pci :3a:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217234] ath10k_pci :3a:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217242] ath10k_pci :3a:00.0: failed to reset chip: -5 Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217244] ath10k_pci :3a:00.0: Could not init hif: -5 The workaround is to manually update to the linux-firmware package in bionic (1.170) Dell have written an article about it: http://www.dell.com/support/article/bg/en/bgbsdt1/sln306440/killer-n1535 -wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en I have been running the package and so far so good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627474 Title: ath10k_pci :03:00.0: firmware crashed! (uuid n/a) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1627474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102001] Re: CUPS recommends incorrect driver for Samsung ML-1670
This bug is still present on Ubuntu 16.04 and Samsung ML-1675. The workaround to use the foomatic driver for CLP310 works though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102001 Title: CUPS recommends incorrect driver for Samsung ML-1670 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1102001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631241] Re: Name resolution stops working after resume from suspend
I have also been affected by this bug after upgrading network-manager and related components to 1.2.6-0ubuntu0.16.04.1 from 1.2.2-0ubuntu0.16.04.4 My current workaround is to do: sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-glib4=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm0=1.2.2-0ubuntu0.16.04.4 sudo apt install libnm-util2=1.2.2-0ubuntu0.16.04.4 Followed by: sudo apt-mark hold libnm-glib-vpn1 sudo apt-mark hold libnm-glib4 sudo apt-mark hold libnm0 sudo apt-mark hold network-manager sudo apt-mark hold libnm-util2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609700] Re: username is not saved in openconnect connection dialog
This together with #1575354 make openconnect barely usable on Ubuntu 16.04. You have to be super quick to enter your credentials before it times out. If either of them would be solved it would at least make it tolerable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371274] Re: Unable to use the widevine plugin with Chromium
Is support for widevine meant to be re-enabled with the latest build (53.0.2785.143-0ubuntu0.16.04.1.1254)? If so I'm just reporting that it is still broken. DRM-enabled video playback doesn't work. I can see the widevine module in chrome://components, but it's missing in chrome://plugins. For me personally this feature is still important as http://hbogo.bg/ does not work with Firefox even with the user agent workaround. For whatever reason they insist you need Silverlight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371274 Title: Unable to use the widevine plugin with Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371274] Re: Unable to use the widevine plugin with Chromium
With the latest chromium build 52.0.2743.116-0ubuntu0.16.04.1.1250 in xenial, the plugin files from Chrome no longer work. I see that this was intentional in the changelog. Is there any chance we will see widevine support again or is it gone for good. What is the reason for this change? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371274 Title: Unable to use the widevine plugin with Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611637] Re: ICC profiles are not applied
This bug is fixed for me with the latest xenial kernel 4.4.0-36-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611637 Title: ICC profiles are not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611637] Re: ICC profiles are not applied
I'll test the mainline kernel when I have some spare time and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611637 Title: ICC profiles are not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611637] Re: ICC profiles are not applied
** Description changed: After upgrading the Xenial kernel from 4.4.0-31-generic to 4.4.0-34-generic, custom ICC color profiles are no longer being applied. I am adding them from System Settings -> Color. I am experiencing this bug for monitors, both the laptop screen and an external screen plugged in via HDMI. If I boot into the old 4.4.0-31-generic kernel they work just fine. I am running a Skylake system and I saw that the i915_bpo module is rebased to v4.7-rc6 in the latest kernel so I am guessing it has something to do with this update. + UPDATE: I found a workaround: The ICC profiles are actually applied if + you turn a display off and back on again via System Settings -> + Displays. The switch in System Settings -> Color still makes no + difference what so ever. + + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: kstoilov 4476 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: kstoilov 4476 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 10 09:59:09 2016 InstallationDate: Installed on 2016-04-29 (102 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. - Bus 001 Device 003: ID 0c45:6713 Microdia - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. + Bus 001 Device 003: ID 0c45:6713 Microdia + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=539a3d5f-4f1b-4fdc-b884-75fb289fe957 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-34-generic N/A - linux-backports-modules-4.4.0-34-generic N/A - linux-firmware1.157.2 + linux-restricted-modules-4.4.0-34-generic N/A + linux-backports-modules-4.4.0-34-generic N/A + linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611637 Title: ICC profiles are not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611637] [NEW] ICC profiles are not applied
Public bug reported: After upgrading the Xenial kernel from 4.4.0-31-generic to 4.4.0-34-generic, custom ICC color profiles are no longer being applied. I am adding them from System Settings -> Color. I am experiencing this bug for monitors, both the laptop screen and an external screen plugged in via HDMI. If I boot into the old 4.4.0-31-generic kernel they work just fine. I am running a Skylake system and I saw that the i915_bpo module is rebased to v4.7-rc6 in the latest kernel so I am guessing it has something to do with this update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kstoilov 4476 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 10 09:59:09 2016 InstallationDate: Installed on 2016-04-29 (102 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=539a3d5f-4f1b-4fdc-b884-75fb289fe957 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611637 Title: ICC profiles are not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562093] Re: [Dell Inc. XPS 13 9350] hibernate/resume failure
I can confirm the same behavior on an XPS 9550 with Ubuntu 16.04 and kernel 4.4.0-31-generic. Unloading the brcmfmac driver does indeed allow the system to hibernate successfuly. If it is still loaded the system goes to a black screen and doe not turn off. The 9550 has the BCM43602 chip. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562093 Title: [Dell Inc. XPS 13 9350] hibernate/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598893] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
Experiencing the exact same behavior on an update xenial install with the following compiz version: 0.9.12.2+16.04.20160714-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1598893 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
I can also confirm #136. Screen flickering has been gone on an XPS 9550 with BIOS 1.2.0 since upgrading to 4.4.0-24-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Amazingly, Bluetooth ON/OFF seems to have an effect on this bug. I have been running with Bluetooth constantly ON for the past couple of days and have seen no flicker at all. As soon as I turn off Bluetooth a flicker occurs after a couple of minutes. I also copied the firmware file from the Windows drivers for the Dell Wireless 1830 card as Bluetooth wasn't finding any devices without it. I am not 100% sure, but I think before adding the bluetooth firmware I got flicker with Bluetooth ON as well. You can get the firmware file from this thread - https://bbs.archlinux.org/viewtopic.php?id=204739 I am running an XPS 9550 with an i7-6700HQ. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
@eugenesan I have the XPS 15 9550 with the latest bios, which is 1.2.0 in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
I have the latest kernel 4.4.0-22.39, but the flickering is still present on an XPS 15 9550. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297849] Re: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files
Affected by this bug on up to date Ubuntu 14.04. Workaround in #40 solves the issue. Syslog: Oct 4 16:39:13 kostadin-Ubuntu NetworkManager[1032]: Starting VPN service 'openvpn'... Oct 4 16:39:13 kostadin-Ubuntu NetworkManager[1032]: VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 8637 Oct 4 16:39:13 kostadin-Ubuntu NetworkManager[1032]: VPN service 'openvpn' appeared; activating connections Oct 4 16:39:13 kostadin-Ubuntu NetworkManager[1032]: [1443965953.992100] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. Oct 4 16:39:18 kostadin-Ubuntu NetworkManager[1032]: VPN service 'openvpn' disappeared -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297849 Title: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1297849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
Experiencing this on 14.04 LTS and iPhone 4s with iOS 8.4. Would appreciate a backport to Trusty. I am also happy to help with testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453336] Re: shotwell fails to import iphone photos
I think this bug has already been reported upstream - https://bugzilla.gnome.org/show_bug.cgi?id=742295. ** Bug watch added: GNOME Bug Tracker #742295 https://bugzilla.gnome.org/show_bug.cgi?id=742295 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453336 Title: shotwell fails to import iphone photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1453336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
