[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Hi again, Epson Perfection 4490 Photo, new Ubuntu Mate 19.04 install, iscan-bundle-1.0.0.x64.deb.tar.gz driver, make sure to add the line 'epkowa'to the /etc/sane.d/dll.conf file first; xsane gave a 'Access to resource has been denied' message as a regular user, same with 'sudo xsane' from a terminal, what I did is: 1) from a terminal enter 'sudo passwd root' and create a password for the root user, when done 2) enter 'su root' and provide the newly created password, when root 3) run 'xsane' despite the warnings AND scan a page (a previous attempt without scanning didn't work), after that, believe it or not, the scanner works, I do not really understand why and how, but this is it, though YMMV. Regards, Luca -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827989] [NEW] Screenshot spanning two/multiple monitors has gap
Public bug reported: Taking an area screenshot (Shift+Print Screen) of an application that spans two monitors results in the screenshot containing a black band where one screen ends and the other begins. This does not happen for Alt+Print Screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 7 00:30:03 2019 InstallationDate: Installed on 2018-12-31 (127 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot of Display settings spanning two screens has gap.png" https://bugs.launchpad.net/bugs/1827989/+attachment/5262042/+files/Screenshot%20of%20Display%20settings%20spanning%20two%20screens%20has%20gap.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1827989 Title: Screenshot spanning two/multiple monitors has gap Status in gnome-screenshot package in Ubuntu: New Bug description: Taking an area screenshot (Shift+Print Screen) of an application that spans two monitors results in the screenshot containing a black band where one screen ends and the other begins. This does not happen for Alt+Print Screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 7 00:30:03 2019 InstallationDate: Installed on 2018-12-31 (127 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1827989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Hi all, Brother MFC-1910W, new Ubuntu Mate 19.04 install, Brother drivers from https://support.brother.com/g/b/downloadend.aspx?c=as_ot=en=mfc1910w_eu_as=128=dlf006893_000=4=625=true at first the scanner was not detected, my previous workaround involving libsane-extras is not an option anymore, since the package has been pulled out. What I did is: 1) created the file /etc/udev/hwdb.d/brother4.hwdb with the lines usb:v04F9p035D* libsane_matched=yes 2) created the file /etc/sane.d/dll.d/brother4 with the line brother4 the scanner works with no further tinkering, creating symlinks and the like. HTH Luca -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Hi Michael, are You installing as root or sudo? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727] Re: All plugins disabled due to expired cert
Fixed in 66.0.4+build3-0ubuntu1. Backports to stable releases are coming. ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium
The patch works for me on Ubuntu 19.04 and I posted into AskUbuntu.com the install procedure I took: https://askubuntu.com/q/1141108/1698 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825497 Title: flash player does not work in chromium Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Invalid Bug description: after you allow it to run it doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 73.0.3683.103-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU= modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Fri Apr 19 04:29:19 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2017-04-20 (729 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 1.18 Load-Processes-Running-Percent: 0.4% Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 02/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4202 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827983] [NEW] plugin freezes my system periodically, randomly.
Public bug reported: Firefox freezes randomly while at tankionline.com using flash plugin which sometimes crashes. I often end up going to a VT and killing the plugin, no report is usually generated but CPU utilization goes back down as does the load. CPU usage goes up past 100% - file attached. That website always tickles the bug eventually. You just have to actively play the game (battle) long enough - lately it's been happening almost immediately upon entering a battle map. I usually have a very large number of windows & tabs open - 50+, I don't know if that's relevant. I often have pandora playing - I don't know if that's relevant. Also, it would be nice if I could attach more than one file to this report; htop reports multiple children for each child using a tremendous amount of memory - way more than I have. I don't know if it's a bug in htop or what. top does not show the grandchildren. The processes often show as disk-bound in top; is it possible there is some disk driver issue? dmesg shows this: [1619488.695470] Cameras IPC[24599]: segfault at 0 ip 55579c3e538b sp 7f4f34ff28c0 error 6 in firefox[55579c3df000+34000] I have no cam, though I did plug an android in recently. I've never noticed the above message before, though admittedly I don't often look at dmesg. Since no timestamp is included it's hard to say when the above was generated or what caused it. Description:Ubuntu 16.04.6 LTS Release:16.04 Firefox 66.0.3 (64-bit) # apt-cache policy firefox firefox: Installed: 66.0.3+build1-0ubuntu0.16.04.1 Candidate: 66.0.3+build1-0ubuntu0.16.04.1 Version table: *** 66.0.3+build1-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 66.0.3+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: apb 15542 F pulseaudio /dev/snd/pcmC0D0p: apb 15542 F...m pulseaudio /dev/snd/controlC0: apb 15542 F pulseaudio BuildID: 20190410113011 Channel: Unavailable CurrentDesktop: Unity Date: Mon May 6 21:13:04 2019 ExecutablePath: /usr/lib/firefox/plugin-container Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-20 (228 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev enp4s5 proto static metric 100 169.254.0.0/16 dev enp4s5 scope link metric 1000 192.168.0.0/24 dev enp4s5 proto kernel scope link src 192.168.0.3 metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-1c6ff3ca-51b4-47e8-b009-e5feb0190429 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410113011 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-1c6ff3ca-51b4-47e8-b009-e5feb0190429 bp-cbd10a93-2bd7-46a7-b905-6df710190425 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: 970M Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd06/17/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970MPro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "150%CPU.png" https://bugs.launchpad.net/bugs/1827983/+attachment/5262017/+files/150%25CPU.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827983 Title: plugin freezes my system periodically, randomly. Status in firefox package in Ubuntu: New Bug description: Firefox
[Desktop-packages] [Bug 1637605] Re: Wacom driver crash on wake
[Expired for xf86-input-wacom (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xf86-input-wacom (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1637605 Title: Wacom driver crash on wake Status in xf86-input-wacom package in Ubuntu: Expired Bug description: Issue: Wacom drivers crash on Wacom pen enabled laptops/tablets. Crash Occurs: When the PC is woken from sleep mode. The screen will become inert to the pen. How to reproduce: Select "suspend" then press power button to wake. Work around: Log out and log back in or shutdown and reboot. Notes below: Tested on multiple machines from 7",10",12", and 14.1". Bug does not seem to effect 7" and 10" displays. Occurs at random. Very common to reproduce. bug has one chance on reboot to fail on wake. If driver does not crash it will continue to work but, could crash after rebooting. Bug has been around I believe in all versions but, noticed it in 12.04 - 14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1637605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818923] Re: Evince does not responds sometimes when I opens my .pdf document
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1818923 Title: Evince does not responds sometimes when I opens my .pdf document Status in evince package in Ubuntu: Expired Bug description: I have been already written about this bug! Please, fix it! I will be very thank! #ubuntu19.04 #evince #crashed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: evince 3.31.91-1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 00:53:17 2019 InstallationDate: Installed on 2019-03-04 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1818923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Think it has something to do with the browser used for hotpot If anyone can find what confi controls in network manager for what browser to use (suspect chromium because it exhibits same behavior and is default install, but Firefox works) can find way to change configuration to use working browser Maybe have time to look after finals > On May 6, 2019, at 10:44 PM, Antonio Aguillon wrote: > > Hi... I have this problem in ubuntu 19.04 right now. Any clue? Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1748839 > > Title: > Problem to connect to WPA2/PEAP WIFI - gnome-shell > > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > This problem is also happened on my desktop. > > After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC > could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no > CA certificate/true username and password. > > > I tried to solve the problem following URL link; however, it could not help > me also. > > https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c > > > > My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, > OS: Ubuntu 18.04.1 (64-bit). > > root@joe-UBTPC:/root # lspci > > 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core > processor DRAM Controller (rev 09) > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen > Core processor Graphics Controller (rev 09) > 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series > Chipset Family MEI Controller #1 (rev 04) > 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset > Family USB Enhanced Host Controller #2 (rev 05) > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family > High Definition Audio Controller (rev 05) > 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 1 (rev b5) > 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 2 (rev b5) > 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 3 (rev b5) > 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 4 (rev b5) > 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 5 (rev b5) > 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family > PCI Express Root Port 6 (rev b5) > 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset > Family USB Enhanced Host Controller #1 (rev 05) > 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC > Controller (rev 05) > 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset > Family SATA AHCI Controller (rev 05) > 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus > Controller (rev 05) > 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter > 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel
[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
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: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in gnome-shell package in Ubuntu: Incomplete Bug description: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Hi... I have this problem in ubuntu 19.04 right now. Any clue? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system
** Summary changed: - [HDA-Intel - HDA Intel PCH, recording] No sound at all - since installation of system + [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827958 Title: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system Status in alsa-driver package in Ubuntu: New Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827957] Re: After unplugging HDMI, internal sound's balance is not center [Acer Swift 5 SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem
** Summary changed: - After unplugging HDMI, internal sound's balance is not center [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem + After unplugging HDMI, internal sound's balance is not center [Acer Swift 5 SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827957 Title: After unplugging HDMI, internal sound's balance is not center [Acer Swift 5 SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: After unplugging HDMI which was selected to transmit sound (successfully) the internal sound is almost all (one from the most extreme position) on the left. Before that the balance was certainly in the center. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:48:24 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Grey Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Thanks for all that. I think we're still missing a system log. Please wait until the problem happens, note the time and date and then run: journalctl -b0 > curjournal.txt and send us the file 'curjournal.txt'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package:
[Desktop-packages] [Bug 1827843] Re: Ubuntu 18.04: App Menu Drawer doesn't show up fully always!
Please try uninstalling (or just renaming the directory of) the extensions mentioned in comment #6. Then reboot and retest We find a large number of bugs are caused by extensions so we need to know if this bug still happens without any extensions installed. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827843 Title: Ubuntu 18.04: App Menu Drawer doesn't show up fully always! Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi I am using Ubuntu 18.04. The App Menu Drawer doesn't show up always fully with all the icons. Sometimes one page shows up while the rest of the pages are empty. Not sure what caused this Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 6 14:07:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-02-10 (85 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=11c430c4-0277-4837-abc2-5daafb4e3cd5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0PNFDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/27/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827912] Re: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound
It sounds like this might be noise on the motherboard itself. Especially if you are hearing crackling when no sound is playing. I don't think there's much we can do about this in software, although the kernel guys sometimes have some tricks they can do to make sound chips less noisy... I personally recommend using a USB audio DAC or "USB sound card" to avoid such problems with motherboard noise. It is a very common hardware problem. You will also get higher quality sound from a USB DAC. I am also moving this bug to the kernel, just in case there's anything that can be done to reduce the problem there. ** Summary changed: - [All Series, Realtek ALC1150] Crackling sound + [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827912 Title: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound Status in linux package in Ubuntu: New Bug description: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration Status in xorg-server package in Ubuntu: New Bug description: I'm running Xubuntu. I finally reported this problem to the Xfce group and received this response: "As arandr/xrandr does not detect correctly your 2nd screen, this seems that it is not related directly to Xfce, but a bug in Xubuntu stack. Can you please open a bug on Xubuntu project if the issue is still present for you?" Thus this bug report. I've been running Xubuntu for years with two monitors, each running an independent xfce4 desktop -- i.e., configured without Xinerama. This has worked fine for every upgrade through 18.04. When upgrading to 18.10, something significant changed and the the second monitor (display :0.1) was disabled. After much reading and work, I have only been able to restore some extremely hobbled functionality. I am unable to get a second xfce4-desktop, panel or window manager running on the second screen. I have assembled detailed screenshots and command output at the following link: http://smallthoughts.com/xfce/xfce.html I'm using an NVIDIA Quadro K-4000 graphics card and no hardware changes were made between 18.04 and 18.10. The nvidia-settings tool reports both monitors active (as configured in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr tools each show only one display (although xrandr can be forced to report on the second display. See full documentation at the above link.) What changed in the latest release, and what needs to be done to get the second monitor running a second desktop once again? I have been struggling with this for many months now and it has severely impacted the use of my system. As a new release of Ubuntu in coming, I would appreciate it if this could be prioritized and addressed as quickly as possible. I will provide additional information upon request. P.S.: There is really no documentation available on running multiple desktops on separate screens when Xinerama is not used to tie the screens together into a single desktop. This is a common configuration and I would like to request that as part of the solution to this problem, the setup steps be documented and this multi-desktop configuration be made a standard part of the development and testing process for each Ubuntu release. 13-> lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1822181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/mag
I no longer have a desktop running disco with which to test this :/ You can't test it on a laptop... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826797 Title: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Impact ] gnome-shell crashes if booted with the monitor off. This leaves me with just a black screen and flashing cursor when I turn the monitor on. [ Test Case ] Boot ubuntu with the monitor off, turn on the monitor. GNOME-Shell should run properly with no errors [ Regression potential ] Mouse cursor isn't scaled properly when using the a11y magnifier Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland events: Connection reset by peer Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: Script threw an exception Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9 Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9 _initializeUI@resource:///org/gnome/shell/ui/main.js:170:17 start@resource:///org/gnome/shell/ui/main.js:127:5 @:1:31 Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: Script threw an exception ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Mon Apr 29 09:33:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (145 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232928] Re: crda defaults file not honoured on wireless association
1. Click the "Start" button, type "cmd", and press "Enter" while holding the "Ctrl" and "Shift" buttons. This runs the Command Prompt as an Administrator. 2. Click "Continue" in the confirmation window. If you are not currently logged in as an administrator, enter the administrator password. 3. Type "assoc .EXT=" in the Command Prompt window, replacing "EXT" with the actual file extension. Press "Enter" to remove the file association. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1232928 Title: crda defaults file not honoured on wireless association Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: I have edited the /etc/defaults/crda file to configure my system regulatory domain to AU. When network-manager attaches to the wireless network, this value is not sourced. The regulatory domain switches back to US. This repeats back and forth, from AU to World to US. System detail is: root@mythtv:/etc/sysctl.d# cat /etc/os-release NAME="Ubuntu" VERSION="13.04, Raring Ringtail" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 13.04" VERSION_ID="13.04" ... Here is the output from dmesg when this occurs. [ 15.579701] cfg80211: Calling CRDA for country: AU [ 15.583170] cfg80211: Regulatory domain changed to country: AU [ 15.583173] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 15.583174] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 15.583175] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 15.583176] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 15.583177] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) ... [ 22.265820] wlan0: authenticate with 94:44:52:a7:ed:d3 [ 22.313771] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3) [ 22.315735] wlan0: authenticated [ 22.319045] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3) [ 22.320563] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 status=0 aid=4) [ 22.323544] wlan0: associated [ 22.323571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 22.323611] cfg80211: Calling CRDA for country: US [ 22.325924] cfg80211: Regulatory domain changed to country: US [ 22.325927] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 22.325928] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2700 mBm) [ 22.325930] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) [ 22.325931] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325932] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325933] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325934] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) ... [ 216.856143] wlan0: deauthenticating from 94:44:52:a7:ed:d3 by local choice (reason=3) [ 216.884265] cfg80211: Calling CRDA to update world regulatory domain [ 216.890344] cfg80211: World regulatory domain updated: [ 216.890350] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 216.890355] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890359] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 216.890362] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 216.890365] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890368] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890390] cfg80211: Calling CRDA for country: AU [ 216.895900] cfg80211: Regulatory domain changed to country: AU [ 216.895904] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 216.895907] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 216.895910] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 216.895913] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 216.895915] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) [ 217.982078] wlan0: authenticate with 94:44:52:a7:ed:d3 [ 218.005788] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3) [ 218.006865] wlan0: authenticated [ 218.010870] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3) [ 218.012486] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 status=0 aid=4) [ 218.015591] wlan0: associated [ 218.015626] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 218.015680] cfg80211: Calling CRDA for country: US [ 218.022206] cfg80211: Regulatory
[Desktop-packages] [Bug 1232928] Re: crda defaults file not honoured on wireless association
Type "assoc .EXT=" in the Command Prompt window, replacing "EXT" with the actual file extension. Press "Enter" to remove the file association. see: https:https://tgw.onl/hostgator/ , https://tgw.onl/dreamhost/ & https://tgw.onl/bluehost/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1232928 Title: crda defaults file not honoured on wireless association Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: I have edited the /etc/defaults/crda file to configure my system regulatory domain to AU. When network-manager attaches to the wireless network, this value is not sourced. The regulatory domain switches back to US. This repeats back and forth, from AU to World to US. System detail is: root@mythtv:/etc/sysctl.d# cat /etc/os-release NAME="Ubuntu" VERSION="13.04, Raring Ringtail" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 13.04" VERSION_ID="13.04" ... Here is the output from dmesg when this occurs. [ 15.579701] cfg80211: Calling CRDA for country: AU [ 15.583170] cfg80211: Regulatory domain changed to country: AU [ 15.583173] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 15.583174] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 15.583175] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 15.583176] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 15.583177] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) ... [ 22.265820] wlan0: authenticate with 94:44:52:a7:ed:d3 [ 22.313771] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3) [ 22.315735] wlan0: authenticated [ 22.319045] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3) [ 22.320563] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 status=0 aid=4) [ 22.323544] wlan0: associated [ 22.323571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 22.323611] cfg80211: Calling CRDA for country: US [ 22.325924] cfg80211: Regulatory domain changed to country: US [ 22.325927] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 22.325928] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2700 mBm) [ 22.325930] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) [ 22.325931] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325932] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325933] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 22.325934] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) ... [ 216.856143] wlan0: deauthenticating from 94:44:52:a7:ed:d3 by local choice (reason=3) [ 216.884265] cfg80211: Calling CRDA to update world regulatory domain [ 216.890344] cfg80211: World regulatory domain updated: [ 216.890350] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 216.890355] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890359] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 216.890362] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 216.890365] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890368] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 216.890390] cfg80211: Calling CRDA for country: AU [ 216.895900] cfg80211: Regulatory domain changed to country: AU [ 216.895904] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 216.895907] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 216.895910] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 216.895913] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2300 mBm) [ 216.895915] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) [ 217.982078] wlan0: authenticate with 94:44:52:a7:ed:d3 [ 218.005788] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3) [ 218.006865] wlan0: authenticated [ 218.010870] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3) [ 218.012486] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 status=0 aid=4) [ 218.015591] wlan0: associated [ 218.015626] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 218.015680] cfg80211: Calling CRDA for country: US [ 218.022206] cfg80211: Regulatory domain changed to country: US [ 218.022210] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 218.022213] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
[Desktop-packages] [Bug 1799293] Re: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.
** No longer affects: gnome-shell-extension-dashtodock (Ubuntu) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Bionic) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Cosmic) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Disco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1799293 Title: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works. Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: Fix Released Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: 1) Ubuntu 18.10 (new install) 2) gdm3 3.30.1-1ubuntu5 Preconditions The session's user has auto-login enabled (i.e. the system starts and the user is not prompted for a password but directly presented with the desktop) 3) What should happen: Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top right corner menu) and the lock screen is engaged (that is, lock screen clock shade drops down and screen fades to dark). Pressing ENTER brings back the lock screen and the password is prompted. 4) What happens: First Win + L lets the system in a half locked state in which the contents of the desktop are seen although no interaction is possible. A second Win + L correctly invokes the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)
** Changed in: guile-2.2 (Ubuntu) Assignee: Andrea Azzarone (azzar1) => (unassigned) ** Changed in: guile-2.2 (Ubuntu Disco) Assignee: Andrea Azzarone (azzar1) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to guile-2.2 in Ubuntu. https://bugs.launchpad.net/bugs/1823459 Title: guile-2.2 ftbfs in disco (arm64 only) Status in guile-2.2 package in Ubuntu: In Progress Status in guile-2.2 source package in Disco: In Progress Bug description: https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco- arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz Totals for this test run: passes: 41515 failures: 1 unexpected passes: 0 expected failures: 10 unresolved test cases: 577 untested test cases:1 unsupported test cases: 1 errors: 0 warning: call to primitive-fork while multiple threads are running; further behavior unspecified. See "Processes" in the manual, for more information. warning: call to primitive-fork while multiple threads are running; further behavior unspecified. See "Processes" in the manual, for more information. ;;; SSAX warning: Skipping PI: xml ;;; SSAX warning: Skipping PI: PI ;;; SSAX warning: Skipping PI: PI1 ;;; SSAX warning: ( Warning: DOCTYPE DECL T system1 found and skipped) ;;; SSAX warning: ( Warning: Internal DTD subset is not currently handled ) ;;; SSAX warning: ( Warning: DOCTYPE DECL T system1 found and skipped) ;;; SSAX warning: Skipping PI: pi ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core binding `filter' FAIL: check-guile == 1 of 1 test failed Please report to bug-gu...@gnu.org == make[4]: *** [Makefile:1956: check-TESTS] Error 1 make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[3]: *** [Makefile:2241: check-am] Error 2 make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[2]: *** [Makefile:1856: check-recursive] Error 1 make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[1]: *** [Makefile:2243: check] Error 2 make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1' dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1823459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826933] Re: gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_mana
I was pretty sure to have marked this as a duplicate of another bug and SRU'ed that description, but I can't find it anymore :o Anyways, i've updated the description accordingly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826933 Title: gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_manager_rebuild_logical_monitors_derived Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: [ Impact ] Gnome shell crashes in meta_monitor_mode_get_resolution This seems to happen when starting gnome-shell with no display on (headless). [ Test case ] - Start gnome-shell in a desktop (i.e. one with no embedded display) setup with all the monitors off - Gnome shell should start properly, without crashing - Anyway monitor results in https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12 to check if errors goes down [ Regression potential ] Scale isn't properly computed for monitors with higher DPI --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826933] Re: gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_mana
This bug was fixed in the package mutter - 3.32.1-2ubuntu1
---
mutter (3.32.1-2ubuntu1) eoan; urgency=medium
* Merge with debian
- Update to 3.32.1 upstream version (LP: #1826936)
- Fix applications aren't focused in Wayland session (LP: #1826176)
- Fix crash on hotplugging a dock with a monitor (LP: #1826182)
Remaining changes:
+ debian/control:
- Update VCS flags to point to launchpad
- Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr
* d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Fixed crash on calculation of global scale (LP: #1826933)
mutter (3.32.1-2) experimental; urgency=medium
* Cherry-pick patches from upstream gnome-3-32 branch:
- compositor-Destroy-window-actors-list-on-destruction.patch,
compositor-Disconnect-from-stage-signals-on-destruction.patch: Fix crash
when exiting. (LP: #1813716)
- 0-initialize a struct we'll be memcmp()ing.
* Reorder patch series so upstream patches come first (no conflicts, no
refreshing required).
mutter (3.32.1-1) experimental; urgency=medium
* New upstream release
* debian/patches: disable mousekeys with Numlock ON to match the
documentation (cherry picked from the 3.32 branch)
mutter (3.32.0+git20190410-2) experimental; urgency=medium
[ Gunnar Hjalmarsson ]
* Add gnome-control-center-data to Build-Depends. This package provides
gnome-keybindings.{its,loc}. These are needed if the translation template
is regenerated at build-time to translate the key bindings defined in
data/50-*.xml. (LP: #1823722)
-- Marco Trevisan (Treviño) Wed, 01 May 2019
11:08:08 +0100
** Changed in: gnome-shell (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: mutter (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: gnome-shell (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: mutter (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: mutter (Ubuntu Disco)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu Eoan)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu Eoan)
Importance: Undecided => Medium
** Description changed:
+ [ Impact ]
+
+ Gnome shell crashes in meta_monitor_mode_get_resolution
+
+ This seems to happen when starting gnome-shell with no display on
+ (headless).
+
+ [ Test case ]
+
+ - Start gnome-shell in a desktop (i.e. one with no embedded display) setup
+ with all the monitors off
+ - Gnome shell should start properly, without crashing
+
+ - Anyway monitor results in
+ https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12
+ to check if errors goes down
+
+ [ Regression potential ]
+
+ Scale isn't properly computed for monitors with higher DPI
+
+
+ ---
+
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.32.0+git20190410-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1826933
Title:
gnome-shell crashes in meta_monitor_mode_get_resolution ->
calculate_scale -> meta_monitor_calculate_mode_scale
derive_calculated_global_scale ->
meta_monitor_manager_rebuild_logical_monitors_derived
Status in gnome-shell package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in gnome-shell source package in Disco:
Fix Committed
Status in mutter source package in Disco:
Fix Committed
Status in gnome-shell source package in Eoan:
Fix Released
Status in mutter source package in Eoan:
Fix Released
Bug description:
[ Impact ]
Gnome shell crashes in meta_monitor_mode_get_resolution
This seems to happen when starting gnome-shell with no display on
(headless).
[ Test case ]
- Start gnome-shell in a desktop (i.e. one with no embedded display) setup
with all the monitors off
- Gnome shell should start properly, without crashing
- Anyway monitor results in
https://errors.ubuntu.com/problem/f66514c0f5ecdc8dceb19c76baf20adf29746f12
to check if errors goes
[Desktop-packages] [Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1265 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1265 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1265 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_na
** Changed in: gnome-shell (Ubuntu Eoan) Status: In Progress => Fix Released ** Changed in: gnome-shell (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813716 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in mutter source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: [ Impact ] GNOME Shell crashes on restart or when ending the session [ Test Case ] Under X11, try to reload the shell multiple times using - Alt+F2: write 'r', press 'enter'. - Or quit it writing in the run dialog 'debugexit'. Repeat multiple times, no crash caused by x11 calls should happen. [ Regression potential ] Nothing known, window actors might not be painted on reload. --- Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576 Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1813716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827959]
*** This bug is a duplicate of bug 1827727 *** https://bugs.launchpad.net/bugs/1827727 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 1827727, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1827727 All plugins disabled due to expired cert -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827959 Title: All extensions disabled due to expiration of intermediate signing cert Status in firefox package in Ubuntu: Confirmed Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to the expiration of a signing certificate, a collection of addon (some related to privacy) are disabled. There are a variety of workarounds, but these all reduce browser users safety (including the approach proposed by Mozilla). Mozilla has released a version that repairs the cert chain 66.0.4 (see https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons- in-firefox/), but this has not been packaged for any ubuntu version except Eoan Ermine. Please release an update for other supported ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827959] Re: All extensions disabled due to expiration of intermediate signing cert
*** This bug is a duplicate of bug 1827727 *** https://bugs.launchpad.net/bugs/1827727 Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827959 Title: All extensions disabled due to expiration of intermediate signing cert Status in firefox package in Ubuntu: Confirmed Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to the expiration of a signing certificate, a collection of addon (some related to privacy) are disabled. There are a variety of workarounds, but these all reduce browser users safety (including the approach proposed by Mozilla). Mozilla has released a version that repairs the cert chain 66.0.4 (see https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons- in-firefox/), but this has not been packaged for any ubuntu version except Eoan Ermine. Please release an update for other supported ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827858] Re: Extensions and add ons are disabled and can not be installed
*** This bug is a duplicate of bug 1827727 *** https://bugs.launchpad.net/bugs/1827727 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827858 Title: Extensions and add ons are disabled and can not be installed Status in firefox package in Ubuntu: Confirmed Bug description: It is a known(https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/#summary) issue, upstream released a new version. IMHO this should be marked as very important and pushed immediately. Firefox release has been pushed — version 66.0.4 on Desktop and Android, and version 60.6.2 for ESR. This release repairs the certificate chain to re-enable web extensions, themes, search engines, and language packs that had been disabled (Bug 1549061). There are remaining issues that we are actively working to resolve, but we wanted to get this fix out before Monday to lessen the impact of disabled add-ons before the start of the week To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827958] [NEW] [HDA-Intel - HDA Intel PCH, recording] No sound at all - since installation of system
Public bug reported: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827958 Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all - since installation of system Status in alsa-driver package in Ubuntu: New Bug description: The inbuilt microphone has never worked on the version of ubuntu on this computer. The hardware works completely fine on other operating systems (Windows). Distribution: Ubuntu 18.04.2 LTS alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:54:58 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 0 3 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1273 F pulseaudio lune 1908 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827957] [NEW] After unplugging HDMI, internal sound's balance is not center [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem
Public bug reported: After unplugging HDMI which was selected to transmit sound (successfully) the internal sound is almost all (one from the most extreme position) on the left. Before that the balance was certainly in the center. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:48:24 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Grey Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827957 Title: After unplugging HDMI, internal sound's balance is not center [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: After unplugging HDMI which was selected to transmit sound (successfully) the internal sound is almost all (one from the most extreme position) on the left. Before that the balance was certainly in the center. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:48:24 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Grey Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
** Description changed: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). - Expected behaviour: Gnome Shell shows the time for the cities you - configured when you click on the date at the top centre. + Expected behaviour (how it worked in cosmic & before): Gnome Shell shows + the time for the cities you configured when you click on the date at the + top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in gnome-shell package in Ubuntu: New Bug description: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
This seems to happen both when you have world clocks configured before upgrading from cosmic to disco, as well as when configuring them after upgrading. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in gnome-shell package in Ubuntu: New Bug description: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour: Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727] Re: All plugins disabled due to expired cert
** Bug watch added: webcompat.com/issues #30522 https://webcompat.com/issues/30522 ** Bug watch added: webcompat.com/issues #30529 https://webcompat.com/issues/30529 ** Bug watch added: webcompat.com/issues #30530 https://webcompat.com/issues/30530 ** Bug watch added: webcompat.com/issues #30534 https://webcompat.com/issues/30534 ** Bug watch added: webcompat.com/issues #30536 https://webcompat.com/issues/30536 ** Bug watch added: webcompat.com/issues #30539 https://webcompat.com/issues/30539 ** Bug watch added: webcompat.com/issues #30556 https://webcompat.com/issues/30556 ** Bug watch added: webcompat.com/issues #30561 https://webcompat.com/issues/30561 ** Bug watch added: webcompat.com/issues #30562 https://webcompat.com/issues/30562 ** Bug watch added: webcompat.com/issues #30563 https://webcompat.com/issues/30563 ** Bug watch added: webcompat.com/issues #30564 https://webcompat.com/issues/30564 ** Bug watch added: webcompat.com/issues #30565 https://webcompat.com/issues/30565 ** Bug watch added: webcompat.com/issues #30566 https://webcompat.com/issues/30566 ** Bug watch added: webcompat.com/issues #30571 https://webcompat.com/issues/30571 ** Bug watch added: webcompat.com/issues #30572 https://webcompat.com/issues/30572 ** Bug watch added: webcompat.com/issues #30576 https://webcompat.com/issues/30576 ** Bug watch added: webcompat.com/issues #30578 https://webcompat.com/issues/30578 ** Bug watch added: webcompat.com/issues #30584 https://webcompat.com/issues/30584 ** Bug watch added: webcompat.com/issues #30588 https://webcompat.com/issues/30588 ** Bug watch added: webcompat.com/issues #30600 https://webcompat.com/issues/30600 ** Bug watch added: webcompat.com/issues #30603 https://webcompat.com/issues/30603 ** Bug watch added: webcompat.com/issues #30637 https://webcompat.com/issues/30637 ** Bug watch added: webcompat.com/issues #30638 https://webcompat.com/issues/30638 ** Bug watch added: webcompat.com/issues #30643 https://webcompat.com/issues/30643 ** Bug watch added: webcompat.com/issues #30645 https://webcompat.com/issues/30645 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827953] [NEW] when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
Public bug reported: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour: Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco regression-release ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in gnome-shell package in Ubuntu: New Bug description: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour: Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549198 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549352 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549248 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549218 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549203 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
Please document here the root cause of this issue and what is being done to ensure that it does not happen again, or if that has already been documented elsewhere, please post a link to that documentation here. I've reviewed all the comments on this bug as well as the other information sources to which it links, and I don't see an explanation of the root cause or of steps being taken to prevent recurrence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
See Also: → https://webcompat.com/issues/30576, https://webcompat.com/issues/30578, https://webcompat.com/issues/30584, https://webcompat.com/issues/30588, https://webcompat.com/issues/30600, https://webcompat.com/issues/30603, https://webcompat.com/issues/30637, https://webcompat.com/issues/30638, https://webcompat.com/issues/30643, https://webcompat.com/issues/30645 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
124 failures in 4131 pushes (0.03 failures/push) were associated with this bug in the last 7 days. This is the #16 most frequent failure this week. ** This failure happened more than 75 times this week! Resolving this bug is a very high priority. ** ** Try to resolve this bug as soon as possible. If unresolved for 1 week, the affected test(s) may be disabled. ** Repository breakdown: * mozilla-central: 124 Platform breakdown: * linux64-qr: 16 * linux64: 36 * android-em-4-3-armv7-api16: 12 * linux32: 12 * osx-10-10: 1 * windows7-32: 2 * linux64-ccov: 5 * windows10-64: 2 * windows10-aarch64: 3 * osx-10-10-shippable: 1 * windows10-64-ccov: 8 * windows7-32-shippable: 1 * linux32-shippable: 8 * linux64-shippable-qr: 8 * linux64-shippable: 8 * windows10-64-shippable: 1 For more details, see: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1548973=2019-04-29=2019-05-05=all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549118 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549180 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549137 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
See https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons- in-firefox/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549110 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549120 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
See Also: → https://webcompat.com/issues/30556, https://webcompat.com/issues/30561, https://webcompat.com/issues/30562, https://webcompat.com/issues/30563, https://webcompat.com/issues/30564, https://webcompat.com/issues/30565, https://webcompat.com/issues/30566, https://webcompat.com/issues/30571, https://webcompat.com/issues/30572 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
(When) can http://ftp.mozilla.org/pub/firefox/candidates/ be opened again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
Please see https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox for current solutions and workarounds. Status updates are posted here: https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
See Also: → https://webcompat.com/issues/30522, https://webcompat.com/issues/30529, https://webcompat.com/issues/30530, https://webcompat.com/issues/30534, https://webcompat.com/issues/30536, https://webcompat.com/issues/30539 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549124 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549105 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549090 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549143 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549173 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549138 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549094 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
124 failures in 56 pushes (2.214 failures/push) were associated with this bug yesterday. Repository breakdown: * mozilla-central: 124 Platform breakdown: * linux64-qr: 16 * linux64: 36 * android-em-4-3-armv7-api16: 12 * linux32: 12 * osx-10-10: 1 * windows7-32: 2 * linux64-ccov: 5 * windows10-64: 2 * windows10-aarch64: 3 * osx-10-10-shippable: 1 * windows10-64-ccov: 8 * windows7-32-shippable: 1 * linux32-shippable: 8 * linux64-shippable-qr: 8 * linux64-shippable: 8 * windows10-64-shippable: 1 For more details, see: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1548973=2019-05-04=2019-05-04=all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549088 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599995] Re: Ability to refresh/rescan individual subdirectories without rescanning the whole file system
Any update on this? It's been 3 years. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/155 Title: Ability to refresh/rescan individual subdirectories without rescanning the whole file system Status in baobab package in Ubuntu: Confirmed Bug description: It would be really helpful it was possible to right click on a folder and rescan just that folder as opposed to clicking the refresh button in the top right hand corner which refreshes the entire file system. The use case for this is when trying to free up some space, you use the tool to identify where the best space savings can be made and then do some clearing up in the folder, then you want to refresh that part of the tree to see how it now fits into the overall picture. I hope that's clear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
** Changed in: totem Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in Totem: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: New Status in totem package in Ubuntu: Triaged Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1827194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827948] [NEW] Use libreoffice-style-breeze as the default icon theme
Public bug reported: The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. So do the breeze icons for libreoffice. All in all does the breeze icon set for libre office fit very good to the look of the Yaru icons. https://i.imgur.com/tgioycv.png https://i.imgur.com/WwKvjMh.png Thus I would suggest to use it as the default icon set in Ubuntu to guarantee a consistent look and feel across the desktop ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1827948 Title: Use libreoffice-style-breeze as the default icon theme Status in libreoffice package in Ubuntu: New Bug description: The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. So do the breeze icons for libreoffice. All in all does the breeze icon set for libre office fit very good to the look of the Yaru icons. https://i.imgur.com/tgioycv.png https://i.imgur.com/WwKvjMh.png Thus I would suggest to use it as the default icon set in Ubuntu to guarantee a consistent look and feel across the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826874] Re: In Ubuntu's Thunderbird, Empty Deleted warns, Empty "Inbox"!
These questions should be asked on the upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1547664 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1826874 Title: In Ubuntu's Thunderbird, Empty Deleted warns, Empty "Inbox"! Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Triaged Bug description: Issue: In Ubuntu desktop 18.10 and 19.04 (and perhaps years earlier?), when a Thunderbird user clicks on File>Empty Deleted, it warns that Empty "Inbox" will be done, instead! Ouch! (It does empty the correct folder anyway, but this should and does scare many users.) After a protracted dialog with the Mozilla Thunderbird support team, I've learned that Mozilla's own vanilla Thunderbird shows Empty "Trash", as it should. They say that the version of Thunderbird that comes bundled with Ubuntu is to blame - so please fix it. Note 1: Specifically, this wrong routine threatens to empty the active folder; commonly, that folder is "Inbox". Note 2: There's no prompt at all, if the "Trash" dialog box is suppressed. But default is (and should be) to have it enabled. Note 3: You can view the details of my Mozilla trouble-shooting (including my/Ubuntu's erroneous Thunderbird screen-print and Mozilla's correct one), here: https://support.mozilla.org/en-US/questions/1254659#answer-1216735 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1826874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
If someone else has those issues with a USB-C Dock (Thunderbolt 3) I got rid of the issue by using the latest mainline Kernel: 5.1.0-050100-generic #201905052130 SMP Mon May 6 01:32:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux and the following Kernel config settings (/etc/default/grub): GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash intel_idle.max_cstate=4 i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 i915.enable_dp_mst=0" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage
[Desktop-packages] [Bug 1775999] Re: Cannot set vino preferences in Lubuntu 18.04
Low because - i doesn't impact the default Ubuntu Desktop - it's easy to workaround by installing another vnc server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1775999 Title: Cannot set vino preferences in Lubuntu 18.04 Status in vino package in Ubuntu: Confirmed Bug description: Apparently the functionality of vino-preferences was merged into gnome-control-center for 18.04. But since Lubuntu does not include gnome-control-center, there is no way to set up vino., ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: LXDE Date: Sat Jun 9 08:40:31 2018 InstallationDate: Installed on 2018-03-09 (91 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1) SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
I forgot to reply to the question about Gnome Shell extensions. No, I have not installed any. The only ones I have are ones that were installed as part of 19.04: dpkg -l | grep -i gnome-shell ii gnome-shell3.32.0+git20190410-1ubuntu1 amd64graphical shell for the GNOME desktop ii gnome-shell-common 3.32.0+git20190410-1ubuntu1 all common files for the GNOME graphical shell ii gnome-shell-extension-appindicator 28-1 all AppIndicator/KStatusNotifierItem support for GNOME Shell ii gnome-shell-extension-desktop-icons19.01.1-1 all desktop icon support for GNOME Shell ii gnome-shell-extension-ubuntu-dock 64ubuntu7 all Ubuntu Dock for GNOME Shell ii yaru-theme-gnome-shell 19.04.2 all Yaru GNOME Shell desktop theme from the Ubuntu Community -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1826394] Re: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
I have recently performed a rebuild due to filesystem change and this problem has not been an issue since. Will reopen if I can reproduce. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: Invalid Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
how do i open an sru for cosmic?, it looks like you took care of disco and eon already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: In Progress Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: In Progress Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)
I would like to note that this is still/again a problem in 2019 on Ubuntu 19.04. (I didn't notice it on 18.10, but maybe I just missed it.) I agree with pretty much everything that gdi2k wrote above, particularly that the following seemingly simple change would remove a significant annoyance for anyone who occasionally uses the mouse without at all detracting from keyboard-only functionality: "Reverting focus to the Name field if a folder is double-clicked using the mouse (familiar Windows behaviour, which does not impact keyboard- using advanced users in any way)." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775999] Re: Cannot set vino preferences in Lubuntu 18.04
Why "low", it's very annoying. Gone seems support for low end.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1775999 Title: Cannot set vino preferences in Lubuntu 18.04 Status in vino package in Ubuntu: Confirmed Bug description: Apparently the functionality of vino-preferences was merged into gnome-control-center for 18.04. But since Lubuntu does not include gnome-control-center, there is no way to set up vino., ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: LXDE Date: Sat Jun 9 08:40:31 2018 InstallationDate: Installed on 2018-03-09 (91 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1) SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Some additional information: It looks like NetworkManager is part of the problem / solution. --> Linked to networkmanager <-- If wifi is disabled (nmcli radio wifi off) the suspend works as expected. Unfortunately, when scripting this into a systemctl script hooking to suspend.target, networkmanager is killed before the script is executed, thus networkmanager cannot respond anymore to the command. Example of this systemctl script included here: [Unit] Description=Network suspend service Before=sleep.target StopWhenUnneeded=yes [Service] User=root Type=oneshot RemainAfterExit=yes ExecStart=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli radio wifi off' ExecStart=/usr/bin/sleep 5 [Install] WantedBy=sleep.target ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827791] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261927/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1654480]
I believe this is due to Firefox playing ~70ms samples of audio at original speed, and skipping between them. In my experience with a similar effect in mplayer (https://mplayerhq.hu/), blending samples of about 15ms produces quality comparable to Webkit (Chrome, Opera). To test this yourself in Firefox and mplayer: video: https://www.youtube.com/watch?v=K0Tsa3smr1w ["DASH Audio" stream URL](https://r1---sn-n4v7sn7y.googlevideo.com/videoplayback?id=o-AKrDYrKDiSnXJpeZyZF5pIoHpfZrgIKmRSc2E2753l3m=250=youtube=yes=31%2C29=sn-n4v7sn7y%2Csn-n4v7knlk=au%2Crdu=m=18=4vTNXNDJB4WQkwag0KugCg=2038750=audio%2Fwebm=yes=15794557=2131.221=1507964730717576=1557001371=1=yes=WEB=205.154.192.198=0=1557023042=ip%2Cipbits%2Cexpire%2Cid%2Citag%2Csource%2Crequiressl%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cei%2Cinitcwndbps%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt=4BB77D089E75903DF0EB3B66A4C36139C0BA2B61.92C7BDB33502808BADBCD64236905EBB1B8CBEDF=yt8=yes) for same video (retrieved with youtube-dl -j K0Tsa3smr1w) `mplayer -speed 2 -af scaletempo=stride=70 # present Firefox quality` `mplayer -speed 2 -af scaletempo=stride=15:overlap=1 # better quality` Note that using `]` to speed up greater than 3x, the words are still intelligible in the latter method. BTW: "overlap=1" causes the samples to be blended together across their entire duration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1654480 Title: HTML5 sound choppy when played at 4x Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: I use a bookmarklet to set the playback rate on the HTML5 player element to 4x (tested with YouTube). Chrome handles the audio flawlessly, but Firefox becomes choppy after 2x. Here's the bookmarklet. The following line may get mangled or removed... "javascript:%7Bvar%20v%3Ddocument.getElementsByTagName(%22video%22)%5B0%5D%3Bv.playbackRate%3D4%3B%7Dvoid(0)%3B" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 50.1.0+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 BuildID: 20161209095719 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Jan 5 20:28:52 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-12-21 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev enp9s0 proto static metric 100 169.254.0.0/16 dev enp9s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev enp9s0 proto kernel scope link src 192.168.0.108 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Profiles: Profile0 (Default) - LastVersion=50.1.0/20161209095719 (In use) RelatedPackageVersions: gnome-shell 3.18.5-0ubuntu0.2 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: X99A GODLIKE GAMING (MS-7883) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/11/2016:svnMSI:pnMS-7883:pvr1.0:rvnMSI:rnX99AGODLIKEGAMING(MS-7883):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7883 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1654480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827791] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261930/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
apport information ** Description changed: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04-on-dell- xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied:
[Desktop-packages] [Bug 1827791] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261919/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261920/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture:
[Desktop-packages] [Bug 1827791] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261926/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261917/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261916/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
(OK, I ran apport-collect 1827791 but that didn't seem to add much, so I ran apport-collect --package=xorg 1827791 and that added all of the output that was originally added). Hopefully the new files are cleaner (no ath10k crashes, no Bluetooth mouse). The CPU temperature warnings occur during boot (or CPU-intensive tasks). The hangs have occurred since then, with no new messages being added to dmesg, so I do not think that's related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
[Desktop-packages] [Bug 1827791] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261921/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261922/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture:
[Desktop-packages] [Bug 1827791] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261918/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261928/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261925/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261929/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1796661]
(In reply to Troels Liebe Bentsen from comment #4) > There is also a bit of discussion on changing the behaviour of fscrypt to use > EXDEV instead: > > https://github.com/google/fscrypt/issues/124 > > But why is Firefox using the /tmp folder in the first place, would it not be > better to do a tmp file in the same folder to start with and then maybe fall > back to /tmp if that fails? This would probably be better, yes. Both for privacy (if you're downloading to an encrypted folder, there is probably a good reason) and for performance (renaming across file systems is slow). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1796661 Title: Firefox can't download files to an fscrypt protected, unlocked folder Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: My Downloads folder is encrypted by fscrypt. I can save and read files in there. However, for Firefox - all downloads fail and it says only "download failed" and offers a button to retry which fails again. After a failed attempt, a file is created with a proper file name but no content (0 bytes). When I changed the download dir to a different non-fscrypted folder, everything works properly and files do get properly saved. I switched to Chromium and Chromium has no problems downloading files into any dirs, regardless encrypted or not. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 62.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pkolaczk 3692 F pulseaudio /dev/snd/pcmC0D0c: pkolaczk 3692 F...m pulseaudio /dev/snd/pcmC0D0p: pkolaczk 3692 F...m pulseaudio BuildID: 20181002091723 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 12:10:57 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-04-12 (543 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.0.1 dev enxd481d7358c11 proto dhcp metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev enxd481d7358c11 proto kernel scope link src 192.168.0.2 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=62.0.3/20181002091723 RelatedPackageVersions: adobe-flashplugin 1:20180911.1-0ubuntu0.18.04.1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1796661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827791] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261923/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261924/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
apport information ** Tags added: apport-collected ** Description changed: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04-on-dell- xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + GsettingsChanges: + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' + b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + InstallationDate: Installed on 2019-04-28 (8 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gnome-shell 3.32.0+git20190410-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt"
[Desktop-packages] [Bug 1827791] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261913/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture:
[Desktop-packages] [Bug 1827791] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827791/+attachment/5261914/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
Re: [Desktop-packages] [Bug 1827407] Re: Touchpad scrolling becomes glitchy or unresponsive
Moi, Viimeisimmän kernelin myötä on ruvennut käymään niin, että kahden sormen toiminnot eivät enää toimi ollenkaan, kun kone käy lepotilassa. - Timo ‐‐‐ Original Message ‐‐‐ On Friday, May 3, 2019 9:27 AM, Timo Aaltonen wrote: > if the boot menu doesn't show up, hit esc when the bios info screen > disappears > > --- > > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1827407 > > Title: > Touchpad scrolling becomes glitchy or unresponsive > > Status in xinput package in Ubuntu: > New > > Bug description: > When I start Ubuntu, the touchpad scrolling (using two fingers) works > great, but after some time (usually hours) the scrolling becomes very > glitchy. The scrolling starts to feel very unresponsive and I have to > do the scrolling motion two to three times to scroll the normal amount > on a page or document. It feels like only small parts of the actual > finger motion converts to scrolling and the rest is cut off. Sometimes > (rarely) the scrolling just dies completely. Booting fixes this issue, > but often the issue is back very quickly after boot. Unfortunately I > have no steps on how to replicate this issue. > > This is a new-ish problem that started happening after an update at > some point a few months ago and did not appear in the first 18.04 > release versions. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xinput 1.6.2-1build1 > ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 > Uname: Linux 4.15.0-48-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu May 2 21:11:18 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: > virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed > virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed > GraphicsCard: > Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA > controller]) > Subsystem: Lenovo HD Graphics 5500 [17aa:5036] > InstallationDate: Installed on 2019-01-02 (119 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) > MachineType: LENOVO 20BWS1S000 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic > root=UUID=cb376add-fb0b-4005-bf43-86651dcf840d ro quiet splash vt.handoff=1 > SourcePackage: xinput > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/14/2018 > dmi.bios.vendor: LENOVO > dmi.bios.version: JBET71WW (1.35 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20BWS1S000 > dmi.board.vendor: LENOVO > dmi.board.version: SDK0K11826 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrJBET71WW(1.35):bd09/14/2018:svnLENOVO:pn20BWS1S000:pvrThinkPadT450s:rvnLENOVO:rn20BWS1S000:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad T450s > dmi.product.name: 20BWS1S000 > dmi.product.version: ThinkPad T450s > dmi.sys.vendor: LENOVO > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1827407/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1827407 Title: Touchpad scrolling becomes glitchy or unresponsive Status in xinput package in Ubuntu: New Bug description: When I start Ubuntu, the touchpad scrolling (using two fingers) works great, but after some time (usually hours) the scrolling becomes very glitchy. The scrolling starts to feel very unresponsive and I have to do the scrolling motion two to three times to scroll the normal amount on a page or document. It feels like only small parts of the actual finger motion converts to scrolling and the rest is cut off. Sometimes (rarely) the scrolling just dies completely. Booting fixes this issue, but often the issue is back very quickly after boot. Unfortunately I have no steps on how to replicate this issue. This is a new-ish problem that started happening after an update at some point a few months ago and did
[Desktop-packages] [Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Hi Daniel, Thanks for taking the time to look at this issue. Regarding the Bluetooth mouse, I only bought that recently, and this issue was occurring before then (just using the touchpad). To double-check though, I just switched off the Bluetooth mouse and rebooted and still get the temporary freezes. The disconnecting you see I think is the mouse going into power-save mode after a period of inactivity (it needs a click of a button to wake-up and reconnect). The Wi-Fi crashes are interesting, I hadn't noticed that in the logs, but I did have an issue where the Wi-Fi stopped working until I disabled and re-enabled it. I will file a separate bug for that, as I don't think they are related (since rebooting, I have seen some hangs, but dmesg at the moment does not have a "firmware crashed" line, and Wi-Fi is still working). I can regenerate the logs from the current session, which should have no Wi-Fi crashes and no Bluetooth connections, if that helps clean out some red herrings from the logs. What command do I run to recollect the same logs and attach them to this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
