[Desktop-packages] [Bug 1843083] Re: tracker-store crashed with SIGSEGV
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1843083 Title: tracker-store crashed with SIGSEGV Status in tracker package in Ubuntu: Confirmed Bug description: I din't know about ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: tracker 2.2.99.0-1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 6 20:15:58 2019 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2016-02-29 (1284 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcCmdline: /usr/lib/tracker/tracker-store ProcEnviron: LANG=ca_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=ca SegvAnalysis: Segfault happened at: 0x55affda50c33:cmpq $0x0,0x8(%rdi) PC (0x55affda50c33) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: () () tracker_data_commit_transaction () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () Title: tracker-store crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-07-30 (37 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1843083/+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 1843083] Re: tracker-store crashed with SIGSEGV
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1843083 Title: tracker-store crashed with SIGSEGV Status in tracker package in Ubuntu: Confirmed Bug description: I din't know about ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: tracker 2.2.99.0-1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 6 20:15:58 2019 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2016-02-29 (1284 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcCmdline: /usr/lib/tracker/tracker-store ProcEnviron: LANG=ca_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=ca SegvAnalysis: Segfault happened at: 0x55affda50c33:cmpq $0x0,0x8(%rdi) PC (0x55affda50c33) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: () () tracker_data_commit_transaction () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () Title: tracker-store crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-07-30 (37 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1843083/+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 1865833] Re: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction()
*** This bug is a duplicate of bug 1843083 *** https://bugs.launchpad.net/bugs/1843083 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843083, so 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1865833/+attachment/5332929/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332931/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332934/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332935/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332936/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332937/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1865833/+attachment/5332938/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1843083 tracker-store crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1865833 Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() Status in tracker package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: tracker 2.3.1-3build1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 3 08:41:10 2020 ExecutablePath: /usr/lib/tracker/tracker-store ExecutableTimestamp: 1581584165 ProcCmdline: /usr/lib/tracker/tracker-store ProcCwd: /home/kabinet-izo ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=ru SegvAnalysis: Segfault happened at: 0x559ed513a243:cmpq $0x0,0x8(%rdi) PC (0x559ed513a243) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: ?? () ?? () tracker_data_commit_transaction () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1865833/+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 416725] Re: Pulseaudio bluetooth module does not recognize a2dp profile
*** This bug is a duplicate of bug 198494 *** https://bugs.launchpad.net/bugs/198494 The thing is its debatable if bluez.class = "0x240404" as I don't think it is as its HSP/HFP and your device is multiprofile and the default is HSP/HFP. ``` 21,18 | 10 | 2Major Service Class CoD Bit 21: Audio (Speaker, Microphone, Headset service, …) CoD Bit 18: Rendering (Printing, Speaker, …) Major Device Class CoD Bits 10: Audio/Video (headset,speaker,stereo, video display, vcr…) Minor Device Class CoD Bits 2: Wearable Headset Device ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/416725 Title: Pulseaudio bluetooth module does not recognize a2dp profile Status in pulseaudio package in Ubuntu: Incomplete Bug description: Binary package hint: pulseaudio-module-bluetooth Hi, I'm trying to use the auto detection of the bluetooth devices, but the module does not recognizes my device as a2dp stereo device. Release: Karmic Koala Alpha4 Package Version: 1:0.9.16~test5-0ubuntu1 I: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes I: card.c: Created 1 "bluez_card.00_11_67_80_00_14" I: sink.c: Created sink 1 "bluez_sink.00_11_67_80_00_14" with sample spec s16le 1ch 8000Hz and channel map mono I: sink.c: bluetooth.protocol = "sco" I: sink.c: device.intended_roles = "phone" I: sink.c: device.description = "BCK-08" I: sink.c: device.string = "00:11:67:80:00:14" I: sink.c: device.api = "bluez" I: sink.c: device.class = "sound" I: sink.c: device.bus = "bluetooth" I: sink.c: device.form_factor = "headset" I: sink.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14" I: sink.c: bluez.class = "0x240404" I: sink.c: bluez.name = "BCK-08" I: sink.c: device.icon_name = "audio-headset-bluetooth" I: source.c: Created source 2 "bluez_sink.00_11_67_80_00_14.monitor" with sample spec s16le 1ch 8000Hz and channel map mono I: source.c: device.description = "Monitor of BCK-08" I: source.c: device.class = "monitor" I: source.c: device.string = "00:11:67:80:00:14" I: source.c: device.api = "bluez" I: source.c: device.bus = "bluetooth" I: source.c: device.form_factor = "headset" I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14" I: source.c: bluez.class = "0x240404" I: source.c: bluez.name = "BCK-08" I: source.c: device.icon_name = "audio-headset-bluetooth" I: source.c: Created source 3 "bluez_source.00_11_67_80_00_14" with sample spec s16le 1ch 8000Hz and channel map mono I: source.c: bluetooth.protocol = "hsp" I: source.c: device.intended_roles = "phone" I: source.c: device.description = "BCK-08" I: source.c: device.string = "00:11:67:80:00:14" I: source.c: device.api = "bluez" I: source.c: device.class = "sound" I: source.c: device.bus = "bluetooth" I: source.c: device.form_factor = "headset" I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14" I: source.c: bluez.class = "0x240404" I: source.c: bluez.name = "BCK-08" I: source.c: device.icon_name = "audio-headset-bluetooth" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/416725/+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 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720
This is still an issue for me in 20.04 -- how can we get some traction on this issue? -- 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/1769936 Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Happy to do further testing, fresh install of Bionic. Discovered this when trying to do a video conference using the built in mic and was able to verify the issue by installing gnome-sound-recorder. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: asif 2213 F...m pulseaudio /dev/snd/controlC0: asif 2213 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 8 11:58:37 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN31WW(V2.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.family: YOGA 720-15IKB dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+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 1566357] Re: Unable to type passwords with the "Japanese (Anthy)" input method
So, I've found this issue through a question on https://askubuntu.com/questions/1214208/input-language-switching-in- password-fields . It looks like I'm facing this bug and it makes GNOME basicly unusable for me. The behaviour I've encountered is as follows: * I have 2 input languages set: Korean (default one) and Russian. Korean language has English build in it, so I don't have add English to my system. Korean uses IBus for input (even in English mode). * Hidden input fields across the system do not like IBus input languages. When I focus the hidden input (password field), the Korean is removed from the input language options, and I'm left only with Russian. And as my passwords are not in Russian, I cannot log in to anything. This includes password fields in browsers, WIFI connection dialog etc. * If the password field has the "show password" button, I press it, and in this mode I can use Korean as normal. * Even more frustraiting. I've added English input language just for passwords. Now when I set the focus on a password field, Korean is removed, so two languages are left: Russian and English. Since I don't usually use English, Russian is chosen. I press Ctrl+Space to change it to English. At this moment input language switching dialog is shown, which makes the focus leave the password field, Korean added to the list, and being chosen. Then the dialog disappears, password field is focused, Korean removed again and my active language is Russian again. It took me 5 minutes to log into Ubuntu One with GNOME (by typing my password in an open form in another field and copy-paste it). Does anyone knows if there is any workaround for this? -- 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/1566357 Title: Unable to type passwords with the "Japanese (Anthy)" input method Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+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 1865824] [NEW] Upgrade to 20.04 removes saved fingerprints
Public bug reported: 18.04 Ubuntu MATE upgraded to 20.04 Ubuntu MATE on 2 March 2020. T430N Upgrade competes and reboots. Upon reboot login screen appears and there is no prompt to login using fingerprint scanner. After login using password the user needs to: run fprintd-enroll and fingerprints are enrolled. On logout/reboot login using fingerprint scanner is available. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 2 22:21:29 2020 InstallationDate: Installed on 2019-12-05 (88 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: fprintd UpgradeStatus: Upgraded to focal on 2020-03-02 (0 days ago) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1865824 Title: Upgrade to 20.04 removes saved fingerprints Status in fprintd package in Ubuntu: New Bug description: 18.04 Ubuntu MATE upgraded to 20.04 Ubuntu MATE on 2 March 2020. T430N Upgrade competes and reboots. Upon reboot login screen appears and there is no prompt to login using fingerprint scanner. After login using password the user needs to: run fprintd-enroll and fingerprints are enrolled. On logout/reboot login using fingerprint scanner is available. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 2 22:21:29 2020 InstallationDate: Installed on 2019-12-05 (88 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: fprintd UpgradeStatus: Upgraded to focal on 2020-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1865824/+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 1858067] Re: package firefox 71.0+build5-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1858067 Title: package firefox 71.0+build5-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in firefox package in Ubuntu: Expired Bug description: I found /var/lib/dpkg/lock-frontend was locked by dpkg when I was trying to install other app, then i killed it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: firefox 71.0+build5-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: whp2038 F pulseaudio BuildID: 20191202093317 Channel: Unavailable Date: Thu Jan 2 14:40:51 2020 DpkgHistoryLog: Start-Date: 2020-01-02 14:40:45 Commandline: apt install gstreamer-tools Requested-By: whp (1000) Install: libgstreamer0.10-0:amd64 (0.10.36-1.5ubuntu1, automatic), gstreamer0.10-tools:amd64 (0.10.36-1.5ubuntu1, automatic), gstreamer-tools:amd64 (0.10.36-1.5ubuntu1) DuplicateSignature: package:firefox:71.0+build5-0ubuntu0.16.04.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package firefox (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-11 (22 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) IpRoute: default via 192.168.166.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.166.0/24 dev wlo1 proto kernel scope link src 192.168.166.64 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 71.0+build5-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0Y0YC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd05/23/2019:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0Y0YC0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1858067/+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 1865645] [NEW] its crash sometimes and its hang
Public bug reported: its crash sometimes and its hang ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 04:50:48 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e] InstallationDate: Installed on 2019-06-24 (252 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 064e:3401 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ac0XX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ac0XX dmi.product.sku: Y4P52AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1865645 Title: its crash sometimes and its hang Status in xorg package in Ubuntu: New Bug description: its crash sometimes and its hang ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 04:50:48 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e] InstallationDate: Installed on 2019-06-24 (252 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 064e:3401 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ac0XX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV
@seb128 - I just noticed this - Apport popped up just after login saying Files (aka nautilus) had crashed - and pointed at this bug report. This was the first time I have seen it so not sure if it is reproducible and I didn't take any particular steps to make it occur. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+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 1865577] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1865577 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: While updating my system running Focal (20.04), my nvidia drivers are not working and now I cannot install the updates (ubuntu-drivers autoinstall). I tried to purge everything installed and named nvidia and after autoinstalling the correct driver for my system. Thanks for helping out. 1) aurion@w540:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2) aurion@w540:~$ apt-cache policy nvidia-340 nvidia-340: Installed: (none) Candidate: 340.108-0ubuntu2 Version table: 340.108-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 3) I would like to be able to install this version of nvidia driver since I have a dockstation and I use the thunderbolt connection for my external monitor 4) I got an error message that the script could not install the drivers. I also had a look into the synaptic additional drivers and the nvidia is selected as installed. However the rendering of my screen is very slow and when I switch to another screen, I can see the window been reloaded. Also I am unable to connect my external monitor via thunderbolt. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sun Mar 1 21:36:20 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.12 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1865577/+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 1865577] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: While updating my system running Focal (20.04), my nvidia drivers are not working and now I cannot install the updates (ubuntu-drivers autoinstall). I tried to purge everything installed and named nvidia and after autoinstalling the correct driver for my system. Thanks for helping out. 1) aurion@w540:~$ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2) aurion@w540:~$ apt-cache policy nvidia-340 nvidia-340: Installed: (none) Candidate: 340.108-0ubuntu2 Version table: 340.108-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 3) I would like to be able to install this version of nvidia driver since I have a dockstation and I use the thunderbolt connection for my external monitor 4) I got an error message that the script could not install the drivers. I also had a look into the synaptic additional drivers and the nvidia is selected as installed. However the rendering of my screen is very slow and when I switch to another screen, I can see the window been reloaded. Also I am unable to connect my external monitor via thunderbolt. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sun Mar 1 21:36:20 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.12 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1865577 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: While updating my system running Focal (20.04), my nvidia drivers are not working and now I cannot install the updates (ubuntu-drivers autoinstall). I tried to purge everything installed and named nvidia and after autoinstalling the correct driver for my system. Thanks for helping out. 1) aurion@w540:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2) aurion@w540:~$ apt-cache policy nvidia-340 nvidia-340: Installed: (none) Candidate: 340.108-0ubuntu2 Version table: 340.108-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 3) I would like to be able to install this version of nvidia driver since I have a dockstation and I use the thunderbolt connection for my external monitor 4) I got an error message that the script could not install the drivers. I also had a look into the synaptic additional drivers and the nvidia is selected as installed. However the rendering of my screen is very slow and when I switch to another screen, I can see the window been reloaded. Also I am unable to connect my external monitor via thunderbolt. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sun Mar 1 21:36:20 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440
[Desktop-packages] [Bug 1865410] Re: Xorg freeze
** Also affects: gnome-shell Importance: Undecided Status: New -- 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/1865410 Title: Xorg freeze Status in GNOME Shell: New Status in xorg-server package in Ubuntu: Incomplete Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 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: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865410/+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 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Agreed. This seems like fundamental desktop functionality to me. My approach so far is to right click on the link, copy it, and then in a terminal type xdg-open "" where is the pasted link. In case it's useful, here's an updated list from above, but clearly there should be a way for people to choose themselves what to whitelist. Can someone explain how to add to the whitelist? - steam - apt - ssh - tg - magnet - urn - zoommtg - irc - git - tg -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+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 1833116] Re: chtmax98090 not working out of the box
On the latest 18.04.4 ISO, it's a little different. After following the Github instructions, the chtmax98098 device appears, and there appears to be output in Pulsemixer when you play sound, but nothing comes out of the speakers. -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1865571] [NEW] Sound card not detected on HP Spectre x360 13-aw0xxx
Public bug reported: On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0 (via proposed-packages), no sound card detected (CPU: Intel i7-1065G). Relevant dmesg output: ``` [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-icl.ri failed with error -2 [4.544997] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-icl.ri failed err: -2 [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Mon Mar 2 20:47:33 2020 InstallationDate: Installed on 2020-02-28 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.44 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8NF08EA#ABU dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1865571 Title: Sound card not detected on HP Spectre x360 13-aw0xxx Status in alsa-driver package in Ubuntu: New Bug description: On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0 (via proposed-packages), no sound card detected (CPU: Intel i7-1065G). Relevant dmesg output: ``` [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-icl.ri failed with error -2 [4.544997] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-icl.ri failed err: -2 [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Mon Mar 2 20:47:33 2020 InstallationDate: Installed on 2020-02-28 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.44 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8NF08EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1865571/+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 1833116] Re: chtmax98090 not working out of the box
Thanks for the link, but I'm a little confused. That seems to be a patch for 4.19? I've still got no audio on the C200 on today's daily ISO of Ubuntu Mate 20.04 out of the box. Kernel version is 5.4.0-14-generic. Following the instructions to use the settings from the OP to use the Github repo makes the device (chtmax98090) appear in the volume control, but the device is muted and cannot be unmuted. -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
Then I have another problem, I'm using Ubuntu 20.04 daily build with mutter-common 3.35.91-1ubuntu1. Unfortunately, I'm still finding a similar issue. Right now, I cannot copy from Clipboard Indicator extension to geany text editor and I cannot copy and paste properly in WPS office editor. Is someone also finding this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Wow. This is all remarkably chill for a bug that boils down to "Chrome can't launch external apps". I just started a new job and I'm trying to set up ubuntu 19.10 as my primary desktop and I'm being blocked by this. Both slack and zoom fail to launch because of this. It also means that apps that want to use Google to authenticate, and thus launch chrome to run the google login and then get a URL callback don't work (Slack in particular). -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+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 1861408] Re: firefox apparmor messages
I can not speak to specifics but there are a lot of potential reason's a
packager (not firefox specific) might not be updating the profile.
- They don't use the profile / or maybe apparmor. (package
maintainership evolves and not everyone who might even be aware of it
without digging in)
- The auto package tests don't report a failure. This could be the tests
aren't set up to use apparmor or just that they don't have a specific
test for a change. Packagers are often very busy and won't dig into an
update unless there are problems being reported.
- The packager can be using a different kernel version which results in
apparmor or the kernel/apparmor having different features being used.
Yes they should be testing on a given release but there are HWE kernels
and upstream kernel builds that users may be using that are different
from what the packager tests on.
- Testing didn't show up an issue, but a different config or usage
pattern that a user has will show up an issue.
- The packager is not familiar with apparmor and can't or at least
doesn't feel compfortable updating the profile.
- The upstream packager tries to maintain a single profile version for
all releases of a package. Eg. FF 71 is released on multiple distro
versions (xenial, bionic, ...) each of those distros have different
kernels and the application will use different features and apparmor
presents different features.
- AppArmor does not provide adequate means to distribute/use a single
profile version across multiple releases when the features required are
significantly different.
I am not arguing that the profile should not be updated, just providing
some reasons for why it might not be. Ideally it should be tested, and
updated if necessary with every release especially when the profile is
part of the package.
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker"
[Desktop-packages] [Bug 1865351] Re: Update to poppler 0.86.0 in Focal
Poppler 0.86.1 has nice fixes in the glib backend, which is used by Evince, as it is has this MR https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/377 which fixes this 3 year old bug https://gitlab.freedesktop.org/poppler/poppler/issues/129 https://gitlab.gnome.org/GNOME/evince/issues/1280 And it fixes a leak in the glib backend (which is considered under- maintained by upstream). https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS Release 0.86.1: core: * Fix regression in Browse Link handling * Internal code improvements ** Bug watch added: gitlab.freedesktop.org/poppler/poppler/issues #129 https://gitlab.freedesktop.org/poppler/poppler/issues/129 ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1280 https://gitlab.gnome.org/GNOME/evince/issues/1280 ** Summary changed: - Update to poppler 0.86.0 in Focal + Update to poppler 0.86.1 in Focal ** Description changed: - Please update to poppler 0.86.0 in Focal + Please update to poppler 0.86.1 in Focal + + https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS + + Release 0.86.1: + core: + * Fix regression in Browse Link handling + * Internal code improvements Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1865351 Title: Update to poppler 0.86.1 in Focal Status in poppler package in Ubuntu: Incomplete Bug description: Please update to poppler 0.86.1 in Focal https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS Release 0.86.1: core: * Fix regression in Browse Link handling * Internal code improvements Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1865351/+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 1865563] [NEW] password box not centered
Public bug reported: When logging in, one of the two isn't centered on screen: either the password input box, or the avatar. See attached photograph. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:41:54 2020 InstallationDate: Installed on 2019-10-13 (141 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-30 (31 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Attachment added: "login-not-centered.jpg" https://bugs.launchpad.net/bugs/1865563/+attachment/5332781/+files/login-not-centered.jpg ** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865563 Title: password box not centered Status in gdm3 package in Ubuntu: New Bug description: When logging in, one of the two isn't centered on screen: either the password input box, or the avatar. See attached photograph. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 16:41:54 2020 InstallationDate: Installed on 2019-10-13 (141 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-30 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865563/+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 1865410] Re: Xorg freeze
Yes, I still can actually -- 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/1865410 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 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: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1865410/+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 1865555] [NEW] libxml2
Public bug reported: when i want to install a package for example reportbug this happens: Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 2.9.4+dfsg1-8ubuntu3 is to be installed libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). And with apt --fix-broken install: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libxml2-dev:i386 The following packages will be upgraded: libxml2-dev:i386 1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded. 1 not fully installed or removed. Need to get 0 B/799 kB of archives. After this operation, 30,7 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 540117 files and directories currently installed.) Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ... Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) .. . dpkg: error processing archive /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1 ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/bin/xml2-config', which is different from othe r instances of package libxml2-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libxml2 2.9.10+dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 20:46:30 2020 InstallationDate: Installed on 2020-01-23 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libxml2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: libxml2 Status in libxml2 package in Ubuntu: New Bug description: when i want to install a package for example reportbug this happens: Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 2.9.4+dfsg1-8ubuntu3 is to be installed libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 2.9.10+dfsg-1ubuntu3 is to be installed reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). And with apt --fix-broken install: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libxml2-dev:i386 The following packages will be upgraded: libxml2-dev:i386 1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded. 1 not fully installed or removed. Need to get 0 B/799 kB of archives. After this operation, 30,7 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 540117 files and directories currently installed.) Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ... Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) .. . dpkg: error processing archive /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1 ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/bin/xml2-config', which is different from othe r instances of package libxml2-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease:
[Desktop-packages] [Bug 1865558] [NEW] gdm-session-worker segmentation fault when checking online crl from smartcard authentication
Public bug reported: Error occurs after pin for the PIV card is entered into the GNOME login GUI. Error in /var/log/messages: gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000] Remove "crl_online" from cert_policy in /etc/pam_pkcs11/pam_pkcs11.conf and there is no segmentation fault. openssl 1.1.1-1ubuntu2.1~18.04.5 opensc 0.17.0-3 libpam-pkcs11 0.6.9-2build2 Using opensc pkcs11_module. Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://. This did not exist in Ubuntu 16. This started in 18.04 (first release) and has existed in all minor versions of 18. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: crl gdm-session-worker libcrypto segfault smartcard ** Package changed: gnome-settings-daemon (Ubuntu) => openssl (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865558 Title: gdm-session-worker segmentation fault when checking online crl from smartcard authentication Status in openssl package in Ubuntu: New Bug description: Error occurs after pin for the PIV card is entered into the GNOME login GUI. Error in /var/log/messages: gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000] Remove "crl_online" from cert_policy in /etc/pam_pkcs11/pam_pkcs11.conf and there is no segmentation fault. openssl 1.1.1-1ubuntu2.1~18.04.5 opensc 0.17.0-3 libpam-pkcs11 0.6.9-2build2 Using opensc pkcs11_module. Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://. This did not exist in Ubuntu 16. This started in 18.04 (first release) and has existed in all minor versions of 18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1865558/+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 1865298] Re: Request for update: hplip 3.20.2
Thanks for reporting. I see that Debian has packaged 3.20.2+dfsg0-1 (https://tracker.debian.org/pkg/hplip). I tried to take a look at the current Ubuntu delta, but it wasn't clear to me if this was already included in the Debian package or if a merge is needed. ** Tags added: needs-debian-merge -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: Request for update: hplip 3.20.2 Status in hplip package in Ubuntu: New Bug description: Version 3.20.2 of hplip was released this month adding support for these printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 If possible, this should be included in focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+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 1865444] Re: Dual monitor loop login
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+attachment/5332756/+files/prevjournal.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865444] Re: Dual monitor loop login
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+attachment/5332757/+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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865444] Re: Dual monitor loop login
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+attachment/5332754/+files/journal.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865444] Re: Dual monitor loop login
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+attachment/5332755/+files/lspcik.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865536] [NEW] OBS consumes all memory, fixed in upstream Mesa
Public bug reported: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Package changed: mesa (Ubuntu) => mesa ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1426 https://gitlab.freedesktop.org/mesa/mesa/issues/1426 ** Changed in: mesa Importance: Undecided => Unknown ** Changed in: mesa Status: New => Unknown ** Changed in: mesa Remote watch: None => gitlab.freedesktop.org/mesa/mesa/issues #1426 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. - Unfortunately, this issue is in all released Ubuntu versions. + Unfortunately, this issue is in all recent Ubuntu versions. ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+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 1833116] Re: chtmax98090 not working out of the box
https://bugzilla.kernel.org/show_bug.cgi?id=201787 ** Bug watch added: Linux Kernel Bug Tracker #201787 https://bugzilla.kernel.org/show_bug.cgi?id=201787 -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1832812] Re: Locking and unlocking the screen is slow and stuttery
I was wrong. gnome-shell 3.35 does not yet have sufficient fixes for this. If anything the performance is now worse with 3.35. ** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) ** Tags removed: fixed-in-3.35.4 fixed-upstream -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gnome-shell package in Ubuntu: Triaged Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+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 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
Is it a kernel, systemd or Nvidia issue to get the right device nodes exposed here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1848951] Re: High CPU when just moving the mouse
** Tags added: fixed-in-3.35.92 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Triaged ** Changed in: mutter (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1848951 Title: High CPU when just moving the mouse Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1848951/+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 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
I think forcing all users (even on systems that don't use the NVIDIA driver) to run X with root privileges would be a little heavy-handed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1854485] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-440 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-440/440.59-0ubuntu0.19.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels.
[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
I don't have any headset exhibiting such issues myself, but it sounds
like pulseaudio is not detecting all available profiles reliably, maybe
due to a race condition.
Since there are three newer versions of PulseAudio in Ubuntu releases
after 18.04, the first thing we should check is to see if this has
already been fixed. When you can please boot 20.04 (prerelease) from
USB:
http://cdimage.ubuntu.com/daily-live/current/
and tell us if the bug still exists there.
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size
** No longer affects: gnome-shell ** Tags added: focal -- 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/1717453 Title: Shell menus (panel, dock, window) font size does not match configured interface font size Status in gnome-shell package in Ubuntu: Confirmed Bug description: Shell menus (panel, dock, window) font size does not match configured interface font size. Test case: gnome-tweak-tool > Fonts > Interface = (something different) Expected: Shell menus to use the same font size. Observed: Shell menu fonts never change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 15 15:17:15 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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/1717453/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Tags added: bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865444] Re: Dual monitor loop login
I can see quite a few graphics-related errors in your log but can't tell what type of GPU it is and also the log is truncated. Please run: lspci -k > lspcik.txt journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt xrandr > xrandr.txt# while both monitors are plugged in and attach the resulting text files here. -- 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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865222] Re: windows disappearing unless in Activities view
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2297 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/1865222 Title: windows disappearing unless in Activities view Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865222/+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 1865326] Re: extra spaces on right and bottom border of gnome terminal's scrollbar
*** This bug is a duplicate of bug 1691678 *** https://bugs.launchpad.net/bugs/1691678 ** This bug has been marked a duplicate of bug 1691678 Scrollbars escape the bottom and right side of the Terminal window by 1px -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1865326 Title: extra spaces on right and bottom border of gnome terminal's scrollbar Status in gnome-terminal package in Ubuntu: New Bug description: On Ubuntu 19.10, On certain themes including the default adwaita theme which is used in vaniall gnome session, there are some extra ugly spaces around the scrollbar of the gnome terminal at right and bottom. I've checked other linux versions with same GNOME version, they don't have it. I've attached a screenshot of that I've asked a question on AskUbuntu site and many suggested to file a bug report https://askubuntu.com/q/1206023/61218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1865326/+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 1864071] Re: [SRU] libreoffice 6.3.5 for eoan
Hello Heather, or anyone else affected, Accepted libreoffice into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.3.5-0ubuntu0.19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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/1864071 Title: [SRU] libreoffice 6.3.5 for eoan Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Eoan: Fix Committed Bug description: [Impact] * LibreOffice 6.3.5 is in its fifth bugfix release of the 6.3 line. For a list of fixed bugs compared to 6.3.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.3.5/RC2#List_of_fixed_bugs (that's a total of 84 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 84 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1864071/+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 1865370] Re: login messagebox re-occurs despite autologin=true
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1865370 Title: login messagebox re-occurs despite autologin=true Status in gnome-keyring package in Ubuntu: Confirmed Bug description: 'Enter password to unlock your keyring' I had to install seahorse and enter null password for a temporary fix to lightdm.conf not being sticky. This worked for a week or so, but today reverted back to keyring prompt. This thing has been plaguing several variants of Linux for many years on and off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.35.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Mar 2 08:25:30 2020 InstallationDate: Installed on 2020-01-23 (38 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1865370/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
** Summary changed:
- pulseaudio doesn't new usb headset
+ pulseaudio doesn't detect (new) USB headset
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] [NEW] pulseaudio doesn't detect (new) USB headset
Public bug reported:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized, or
the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker and
the "multichannel" microphone are recognized, only one can be used -
either speaker or microphone. When selecting the speaker, the microphone
is switched back to any other device available, them same goes for the
microphone and the speaker - any other speaker is selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a second
headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282) and
it sounds somewhat very familiar, but instead of "env={}" in /usr/share
/ubuntu-drivers-common/detect/sl-modem.py there's "env=env". Removing
"env=env" doesn't resolve the problem.
Do you require additional information?
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "pulseaudio.info"
https://bugs.launchpad.net/bugs/1865499/+attachment/5332737/+files/pulseaudio.info
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in pulseaudio package in Ubuntu:
New
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865170] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332724/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332723/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332722/+files/CurrentDmesg.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332732/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332721/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332734/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332725/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332726/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332733/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332731/+files/PulseList.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332729/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332730/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332727/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332728/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
apport information ** Tags added: apport-collected ** Description changed: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re- open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re- opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.11 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: colton 4205 F pulseaudio + /dev/snd/controlC0: colton 4205 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-01-08 (53 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 + MachineType: Dell Inc. XPS 13 7390 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-1073-oem N/A + linux-backports-modules-4.15.0-1073-oem N/A + linux-firmware 1.173.15 + Tags: bionic + Uname: Linux 4.15.0-1073-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/25/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.4.0 + dmi.board.name: 0377MH + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 7390 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1865170/+attachment/5332720/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu.
[Desktop-packages] [Bug 1865222] Re: windows disappearing unless in Activities view
d'oh… ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2297 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2297 -- 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/1865222 Title: windows disappearing unless in Activities view Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1865222/+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 1865222] Re: windows disappearing unless in Activities view
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2297 -- 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/1865222 Title: windows disappearing unless in Activities view Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1865222/+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 1865283] Re: gnome calendar icon missing Ubuntu 20.04
Thank you for your bug report, the issue is fixed in the 3.35.90 update which has been uploaded to Debian and will be synced ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1865283 Title: gnome calendar icon missing Ubuntu 20.04 Status in gnome-calendar package in Ubuntu: Fix Committed Bug description: see screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1865283/+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 1865351] Re: Update to poppler 0.86.0 in Focal
Thank you for your bug report, why do you think we should update to this version? Focal is feature frozen now and new poppler versions come with soname changes which makes they require full transitions to their rdepends so it's not trivial update ** Changed in: poppler (Ubuntu) Importance: Undecided => Wishlist ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1865351 Title: Update to poppler 0.86.0 in Focal Status in poppler package in Ubuntu: Incomplete Bug description: Please update to poppler 0.86.0 in Focal Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1865351/+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 1865363] Re: nm-applet unstable behaviour when multiple AP have the same name
Thank you for your bug report, could you also report it upstream? ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1865363 Title: nm-applet unstable behaviour when multiple AP have the same name Status in network-manager-applet package in Ubuntu: New Bug description: Hi, I'm using a public wifi network to access the internet (in the spirit of FON - https://fon.com/). Let's name it XXX. There are multiple access points with the same name that "offer" this network. Many are in conflict with one another, using the same channel. Also, each AP is regularly switching channel, so I cannot associate a channel to a bssid and work with bssids instead of network name. nm-applet manages this situation very badly: - nm-applet seems to select the AP with the strongest signal, even if it is in conflict with 10s of others APs, leading to a very bad connexion, while still displaying an icon showing very good signal; - Also, as a consequence of its selection, quite often, nm-applet switches from one AP to the other, creating very instable situations, leading to even worse connexions throughput; - Trying to solve the problem, I saved the network, modified the connexion manually to fix one channel (let's name it YYY1), saved the connexion as "XXX-c[han]YYY1", then disconnected. Then I reconnected to the network, but nm-applet seemed to have switched to another AP using another chanel (YYY2), so I repeated the operation, and saved a "XXX-c[han]YYY2" network. Now, nm-applet, in its list of available networks, now randomly displays either simply "XXX", or at times "XXX >" (with a triangular char showing that there are sunetworks available) with "XXX-channelYYY1" are "XXX-channelYYY2" as sub networks. In the second case, if I select the network with less/no channel conflict, then the connexion is quite good and stable. > As can be seen in the attached picture, in the terminal, there are many access points available for XXX network, several using channel 11 or 7. As can also be seen there are 2 saved networks in nm-applet "Edit networks", one fixed to chan7, one fixed to chan11. However, nm- applet just lists "XXX" in its list of available networks... - Finally, there is no simple way in "Edit connections" to copy an existing configuration, so I cannot easily create a connection for each possible chanel. So, even if point above would be solved and nm- applet always display the avaliable "XXX-c[han]YYY" sub networks, I cannot simply create an entry for each channel and manually select the channel that is less in conflict than the others, based on my script that lists all the APs and the channels they use. Does anyone has a solution to this kind of situation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1865363/+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 1865460] Re: Saving file in libreoffice crashes gnome-shell session
Found connection to Bug #1497832 reported by Michael Gratton on 2015-09-21: This bug only occurs when 'Use Libreoffice Dialogs' is ticked off in the general preferences. Thus, it seems to be a GTK3 issue. -- 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/1865460 Title: Saving file in libreoffice crashes gnome-shell session Status in libreoffice package in Ubuntu: New Bug description: Hi! I freshly installed Ubuntu 18.04.4 LTS on a new laptop two weeks ago. Since then, I have been unable to save files in Libreoffice (version 1:6.0.7-0ubuntu0.18.04.10). What I expected expected to happen: When I click 'Save as' in the File menu of Libreoffice, a file dialog pops up where I can specify a filename to save the document in. Upon hitting ENTER, I expect the dialog to vanish and the file to be saved under that name. What happened instead: As soon as I hit ENTER, I get logged out of the gnome-shell session (back to the login screen). No file is saved. I just repeated the bug three times to confirm. Debugging information: According to the syslog data, saving the file causes gnome-shell to segfault (see event at 11:11:34 below). I'm including some context before and after the segfault to help with the debugging: Mar 2 11:11:02 NHolgersson org.gnome.Shell.desktop[1457]: message repeated 2 times: [ libinput error: client bug: timer event21 debounce short: offset negative (-2ms)] Mar 2 11:11:18 NHolgersson org.gnome.Nautilus[1427]: func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26 Mar 2 11:11:21 NHolgersson soffice.bin[22707]: GtkDialog mapped without a transient parent. This is discouraged. Mar 2 11:11:21 NHolgersson dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.719' (uid=1000 pid=22707 comm="/usr/lib/libreoffice/program/soffice.bin --writer " label="libreoffice-soffice (complain)") Mar 2 11:11:21 NHolgersson kernel: [55178.608920] audit: type=1400 audit(1583143881.573:132): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/jean/Downloads/README" pid=22707 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Mar 2 11:11:21 NHolgersson kernel: [55178.609164] audit: type=1400 audit(1583143881.573:133): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/jean/Downloads/README" pid=22707 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Mar 2 11:11:21 NHolgersson kernel: [55178.609857] audit: type=1400 audit(1583143881.573:134): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name=2F686F6D652F6A65616E2F446F776E6C6F6164732F44656E207376656E736B6120626F73746164736D61726B6E6164656E20617072696C2032303138 pid=22707 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Mar 2 11:11:21 NHolgersson systemd[1]: Starting Hostname Service... Mar 2 11:11:21 NHolgersson kernel: [55178.609860] audit: type=1400 audit(1583143881.573:135): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name=2F686F6D652F6A65616E2F446F776E6C6F6164732F44656E207376656E736B6120626F73746164736D61726B6E6164656E20617072696C2032303138 pid=22707 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Mar 2 11:11:21 NHolgersson kernel: [55178.609862] audit: type=1400 audit(1583143881.577:136): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/jean/Downloads/android-x86-9.0-rc2.iso" pid=22707 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Mar 2 11:11:21 NHolgersson dbus-daemon[884]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 2 11:11:21 NHolgersson systemd[1]: Started Hostname Service. Mar 2 11:11:34 NHolgersson kernel: [55191.104967] show_signal_msg: 1 callbacks suppressed Mar 2 11:11:34 NHolgersson kernel: [55191.104968] gnome-shell[1457]: segfault at 0 ip 7f3bb0601f6f sp 7ffe4701e160 error 4 in libgnome-shell.so[7f3bb05e5000+248000] Mar 2 11:11:34 NHolgersson evolution[7204]: Error reading events from display: Broken pipe Mar 2 11:11:34 NHolgersson soffice.bin[22707]: Error reading events from display: Connection reset by peer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1865460/+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 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size
Sadly this still doesn't work in 3.35.91-1ubuntu2 ** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Confirmed ** Changed in: gnome-shell (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) -- 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/1717453 Title: Shell menus (panel, dock, window) font size does not match configured interface font size Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Shell menus (panel, dock, window) font size does not match configured interface font size. Test case: gnome-tweak-tool > Fonts > Interface = (something different) Expected: Shell menus to use the same font size. Observed: Shell menu fonts never change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 15 15:17:15 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1717453/+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 1799266] Re: gnome-shell uses high CPU when simply moving windows
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799266 Title: gnome-shell uses high CPU when simply moving windows Status in Mutter: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gjs source package in Bionic: Fix Released Status in gjs source package in Cosmic: Fix Released Status in gjs source package in Disco: Fix Released Bug description: After doing a stock install Ubuntu 18.04.1 LTS on an imac 27" 2010 8G ram, Intel® Core™ i7 CPU 870 @ 2.93GHz × 8 Simply moving a window around on the screen increases the cpu usage by gnome-shell to 44%. When displaying a movie, totem takes 10%, gnome-shell takes 22%. etc etc System:Host: oldie Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: desktop System: Apple product: iMac11 3 v: 1.0 serial: N/A Mobo: Apple model: Mac-F2238BAE v: iMac11 3 serial: N/A UEFI: Apple v: IM112.88Z.0057.B01.1112090906 date: 12/09/11 CPU: Quad core Intel Core i7 870 (-MT-MCP-) cache: 8192 KB clock speeds: max: 2927 MHz 1: 1271 MHz 2: 1206 MHz 3: 1374 MHz 4: 1271 MHz 5: 1377 MHz 6: 1266 MHz 7: 1693 MHz 8: 1279 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Broadway PRO [Mobility Radeon HD 5850] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 2560x1440@59.95hz OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 3.3 Mesa 18.0.5 Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card-1: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: c4:2c:03:30:ce:8e Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k IF: wls1 state: down mac: d8:30:62:67:2a:19 Drives:HDD Total Size: 2500.5GB (38.0% used) ID-1: /dev/sda model: WDC_WD1001FALS size: 1000.2GB ID-2: USB /dev/sdb model: MK1059GSM size: 1000.2GB ID-3: USB /dev/sdd model: Elements_10B8 size: 500.1GB Partition: ID-1: / size: 226G used: 125G (58%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 701G used: 876M (1%) fs: btrfs dev: /dev/sda4 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: 936 Info: Processes: 342 Uptime: 3:07 Memory: 2087.3/7967.4MB Client: Shell (bash) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:09:59 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-22 (0 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=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799266/+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 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Confirmed Bug description: Cannot dismiss reminders for a recurrence with exceptions. Calendar entries like this are generated: BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:My recurrence TRIGGER;VALUE=DURATION:-PT120M X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame ter with an illegal type for property: VALUE=DURATION END:VALARM ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2004 F pulseaudio /dev/snd/controlC0: vectro 2004 F pulseaudio BuildID: 20190705212852 Channel: Unavailable CurrentDesktop: KDE Date: Wed Oct 2 17:50:39 2019 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) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.sku: T4M40UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1855938] Re: [nvidia] Screen freezes and only mouse moves
I'm experiencing the same issue as the OP. Here is the requested 'pevboot.txt'. It's happening for me multiple times during the week - I'd say two to three times a week on Ubuntu 19.10. gnome-shell 3.34.3-1ubuntu1~19.10.1 nvidia-driver-440440.59-0ubuntu0~0.19.10.1 Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+attachment/5332695/+files/prevboot.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/1855938 Title: [nvidia] Screen freezes and only mouse moves Status in gnome-shell package in Ubuntu: Incomplete Bug description: The screen freezes but the mouse can be moved. SSH access works. This is on Legion Y545, Ubuntu 19.10 Nvidia Geforce 1660Ti Intel 9750h Symptoms: This only happens when: Nvidia-Prime is selected as "on-demand" And maybe most likely after the laptop comes out of sleep. xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1 If I choose prime-select "nvidia", this never happens. Makes me believe this has to do with intel video drivers. Error trace: GpuWatchdog[22171]: segfault at 0 ip 56163556379d sp 7fdeb6dd8480 error 6 in chrome[561631628000+717] Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 01 80 7d 8f 00 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 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' Date: Tue Dec 10 15:01:38 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc] InstallationDate: Installed on 2019-10-23 (48 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81Q6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545: dmi.product.family: Legion Y545 dmi.product.name: 81Q6 dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545 dmi.product.version: Legion Y545 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
[Desktop-packages] [Bug 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1855893 Title: Properly let PCM leave suspended state when hardware doesn't support PCM resume Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Bug description: [Impact] Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume. [Fix] According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume. For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal. [Test] 1. See if microphone on snd-usb-audio works in gnome-control-center/cheese. 2. Suspend/resume. 3. See if microphone still works in those apps. I can the issue is fixed after each suspend/resume cycle. [Regression Potential] Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855893/+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 1863584] Re: Drop gnombg for background drawing
This bug was fixed in the package unity-control-center - 15.04.0+19.10.20190921-0ubuntu2 --- unity-control-center (15.04.0+19.10.20190921-0ubuntu2) focal; urgency=medium [ Khurshid Alam ] * Drop libgnome-desktop for background drawing. Use libunity-settings-daemon instead. (LP: #1863584) * Update version to 20.04 LTS -- Sebastien Bacher Thu, 27 Feb 2020 16:09:49 +0100 ** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1863584 Title: Drop gnombg for background drawing Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Copy the code into unity-settings-daemon so that we can use it with other unity (unity & u-c-c) components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863584/+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 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
This bug was fixed in the package mutter - 3.35.91-1ubuntu1 --- mutter (3.35.91-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + 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 -- Marco Trevisan (Treviño) Wed, 26 Feb 2020 15:33:52 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Fix Released Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+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 1751593] Re: Weird black border flickers around windows in Wayland sessions
This bug was fixed in the package mutter - 3.35.91-1ubuntu1 --- mutter (3.35.91-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + 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 -- Marco Trevisan (Treviño) Wed, 26 Feb 2020 15:33:52 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1751593 Title: Weird black border flickers around windows in Wayland sessions Status in GNOME Shell: Expired Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Whenever I open any new window, a black border around the window appears for a fraction of a second (like a flicker). Although this doesn't happen very frequently, happens around 3-4 times out of 10. This is most noticeable when I right click on Desktop and click on "Open terminal". I can replicate this bug every time when I open terminal this way. Also, when I open terminal by pressing Control+Alt+T, the caption buttons kind of grey out after the flicker and are un-clickable. They look as if the window is not at focus. Workaround is to switch to another window (Alt+Tab) and then switch back to terminal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 19:58:24 2018 InstallationDate: Installed on 2018-02-13 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1751593/+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 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received
[Desktop-packages] [Bug 1827751] Re: Shield screen is displayed after blanking even when lock screen disabled
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Released
--
You received this
[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto
This bug was fixed in the package mutter - 3.35.91-1ubuntu1 --- mutter (3.35.91-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + 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 -- Marco Trevisan (Treviño) Wed, 26 Feb 2020 15:33:52 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 --- This has begun happening in the last few days; I was unable to create a bug for the last crash because I had some outdated packages installed. This crash occurred as I started Firefox Nightly on my machine with a fairly large session being restored. GNOME logged me out as the windows were being spawned by session restored. My Firefox is being started in pure Wayland mode -- MOZ_ENABLE_WAYLAND=1 I am using "Basic" compositing (not WebRender) in this session. Happy to provide any other details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 10 20:22:13 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-01-05 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax PC (0x7fa5318821db) ok source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1859259/+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 1697143] Re: GNOME Shell's Suspend feature is hidden in power menu
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received
[Desktop-packages] [Bug 1721319] Re: On-screen keyboard pops up with touchscreen even when physical keyboard present
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received
[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
This bug was fixed in the package mutter - 3.35.91-1ubuntu1 --- mutter (3.35.91-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + 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 -- Marco Trevisan (Treviño) Wed, 26 Feb 2020 15:33:52 +0100 ** Changed in: mutter (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1860540] Re: Password entry has no emblem to displaying what you type
This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
---
gnome-shell (3.35.91-1ubuntu2) focal; urgency=medium
* control: Fix package for Yaru Breaks. It's called `yaru-theme-gnome-shell`
and not `yaru-theme`
* control: Bump Breaks on appindicator and desktop-icons.
These have been updated for GNOME 3.36
gnome-shell (3.35.91-1ubuntu1) focal; urgency=medium
* Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
- ubuntu-session (| gnome-session) to have the ubuntu session available
- xserver-xorg-legacy
- yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
- add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
- quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
- Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
- Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/background_login.patch
- Change default background color as we modified the default GDM color
for our ubuntu session.
+ ubuntu/gdm_alternatives.patch
- Add support for GDM3 theme alternatives
+ optional-hot-corner.patch
- enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ main-show-an-error-message-on-gnome-shell-crash.patch,
global-make-possible-to-set-debug-flags-dynamically.patch,
main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
main-add-backtrace-crashes-all-and-backtrace-all.patch,
sessionMode-add-support-for-debugFlags-parameter.patch:
- Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
- Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
- stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
- Show monitor scaled cursor when magnifier is enabled
+ Break gnome-shell-extension-appindicator (<< 30)
+ Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
+ Break gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
+ Break yaru-theme (<< 20.04.2)
* debian/control:
- Bump breaks on gnome-shell-extension-ubuntu-dock (<< 67ubuntu20.04.1)
- Bump breaks on gnome-shell-extension-dashtodock (<< 67+git20200225-1)
- Bump breaks on yaru-theme (<< 20.04.2)
- Build depend and Depend on gjs 1.58.1-2ubuntu1
* d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch,
* d/p/volume-Add-back-sound-feedback-on-scroll.patch:
- Dropped, applied upstream
* d/p/ubuntu/background_login.patch:
- Simplify: just change the default background color to match Yaru
* d/p/ubuntu/lock_on_suspend.patch:
- Update to use string formatting not to confuse gettext with templates
* d/p/ubuntu/meson-Depend-on-gjs-1.58.1.patch:
- Lower the dependency on gjs 1.58.1
* debian/patches:
- Refreshed
* debian/{control,patches}: Build depend on gjs 1.58.1-2ubuntu1
gnome-shell (3.35.91-1) experimental; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release
- Improve visual appearance of Weather integration
- New system dialog designs
- Sandbox the portal helper
- Improvements to the magnifier
- New lock screen (a merge of screen shield and unlock dialog)
(LP: #1832812, LP: #1827751)
- Show the suspend button in the power menu (LP: #1697143)
- Font size matches configured interface font size (LP: #1717453)
- Only enable OSK automatically if touch-mode is enabled (LP: #1721319)
- Added show-password emblem to password entries (LP: #1860540)
* debian/control:
- Update build dependencies
* debian/gnome-shell-common.install: Add extensions tool icons
* d/p/Style-looking-glass-variant-independant.patch:
- Allow to style looking glass properly
[ Laurent Bigonville ]
* debian/rules: Do not override libexecdir so things are installed in
/usr/libexec now that's allowed by the policy
-- Iain Lane Thu, 27 Feb 2020 15:35:57 +
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received
[Desktop-packages] [Bug 1836700] Re: [regression] Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions
This bug was fixed in the package mutter - 3.35.91-1ubuntu1 --- mutter (3.35.91-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + 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 -- Marco Trevisan (Treviño) Wed, 26 Feb 2020 15:33:52 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1836700 Title: [regression] Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Subpixel font rendering doesn't work any more in shell panels/menus for Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 Date: Tue Jul 16 14:40:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-02 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1836700/+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 1863584] Re: Drop gnombg for background drawing
This bug was fixed in the package unity-settings-daemon - 15.04.1+19.10.20190921-0ubuntu3 --- unity-settings-daemon (15.04.1+19.10.20190921-0ubuntu3) focal; urgency=medium [ Khurshid Alam ] * Fix gnome-update-wallpaper-cache build -- Sebastien Bacher Wed, 26 Feb 2020 23:42:39 +0100 ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1863584 Title: Drop gnombg for background drawing Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Copy the code into unity-settings-daemon so that we can use it with other unity (unity & u-c-c) components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863584/+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 1865444] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332688/+files/GsettingsChanges.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865379] Re: Raspberry Pi fails to wake at login prompt
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Raspberry Pi fails to wake at login prompt + Raspberry Pi 4 fails to wake at login prompt -- 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/1865379 Title: Raspberry Pi 4 fails to wake at login prompt Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10 Eoan) fails to wake from sleep when no user is logged in and the screen is sitting at the gdm login prompt. This has happened on two different systems. One system uses the official RPi 7 inch touchscreen via (LCD DSI Display Connector). The other system has a 10 inch non-touchscreen from SunFounder via (Micro HDMI). Nothing wakes the Pi: Keyboard, mouse, or touchscreen. After a user logs in and the screen locks on sleep the system wakes just fine with a lock screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8 Uname: Linux 5.4.0-1001-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu18 Architecture: armhf CurrentDesktop: XFCE Date: Sun Mar 1 20:03:12 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865379/+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 1865444] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332689/+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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865444] Re: Dual monitor loop login
apport information ** Tags added: apport-collected package-from-proposed ** Description changed: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu18 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-02-29 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-shell 3.35.91-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 + RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 + Tags: focal package-from-proposed + Uname: Linux 5.4.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332687/+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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1864980] Re: using hebrew in a german basic setup
Thanks for your report! I don't quite understand. Is it input languages you are talking about, i.e. do you want to be able to switch between English, German and Hebrew for typing? There should be no problem to do so. Can you please describe in more detail what you tried to do, and exactly how you reached the conclusion that it's "not possible". ** Changed in: gnome-control-center (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/1864980 Title: using hebrew in a german basic setup Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: Hi! I was trying to use different languages/keyboards like german, english and hebrew in a german setup, meaning I put the basić language of my ubuntu into german and then wanted to use hebrew aswell, which was not possible and I also didn't find a workaround. When I put the basic language of ubuntu into hebrew it works (of course), and I realized that in english as basic language it also works to change between different languages/keyboards. Would be nice to have this option in a german environment aswell. You know, these two countries, they have enough issues already ;) Best regards Benedikt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 10:26:24 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f910] InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd11/27/2014:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCLUE-01W010GR:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.sku: PSCLUE dmi.product.version: PSCLUE-01W010GR dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1864980/+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 1865371] Re: Mouse Cursor or Touchpad indicator/pointer not working
Please run this command to send us more relevant information about the machine: apport-collect 1865371 ** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu) ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1865371 Title: Mouse Cursor or Touchpad indicator/pointer not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: after some updates this week, my mouse/touchapad cursor/indicator/pointer started not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.5.7-050507-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 20:29:07 2020 InstallationDate: Installed on 2017-07-14 (960 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170714) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-10-29T04:23:27.400327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371/+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 1865444] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332692/+files/monitors.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865444] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332690/+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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865373] Re: Authentication Prompt cut off
Can you please run this command to send us more information about your gnome-shell? apport-collect 1865373 ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** 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/1865373 Title: Authentication Prompt cut off Status in gnome-shell package in Ubuntu: Incomplete Bug description: Every time the "Authentication Required" prompt pops up, the right side is cut off short. My resolution is currently set to 1600x900 on a 1920x1080 13." screen. The same thing happened at native resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:40:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081b] InstallationDate: Installed on 2020-02-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_evtvik@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu_evtvik ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865373/+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 1865444] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1865444/+attachment/5332691/+files/ShellJournal.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/1865444 Title: Dual monitor loop login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 20.04 desktop gnome 3 no virtualisation Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected also since last update No mouse pointer on login screen --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal package-from-proposed Uname: Linux 5.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865444/+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 1865222] Re: windows disappearing unless in Activities view
No that's a different 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/1865222 Title: windows disappearing unless in Activities view Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1865222/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I can't reproduce this with Focal daily image. Can you guys please confirm? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/1767654/+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 1865222] Re: windows disappearing unless in Activities view
@Daniel is it not what you just filed? https://gitlab.gnome.org/GNOME/gnome-shell/issues/2295 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2295 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2295 -- 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/1865222 Title: windows disappearing unless in Activities view Status in gnome-shell package in Ubuntu: New Bug description: It's happened to me twice after a recent update that I couldn't reach a window, even though it was visible in the Activities view and listed on the launcher. The windows seemed to take focus, but couldn't be seen. Alt+Tab switching didn't help either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 22:00:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-10 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1865222/+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 1865257] Re: Pulseaudio needs kernal conf IMU=size (64)
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1865257 Title: Pulseaudio needs kernal conf IMU=size (64) Status in linux package in Ubuntu: Incomplete Bug description: Since Pulseaudio 11.0 https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ "Improved bluetooth MTU configuration The packet size (a.k.a. MTU, "maximum transmission unit") that PulseAudio uses with the bluetooth HSP profile was previously always configured to be 48 bytes. That worked with most hardware, but some adapters require a different packet size. Now PulseAudio asks the kernel what packet size should be used, which fixes the problem. However, a new problem appeared: some adapters that used to work with 48 byte packet size don't any more work with the size that the kernel tells PulseAudio to use. If you find that HSP audio stopped working when upgrading to PulseAudio 11.0, you can revert to the old behaviour by passing option "autodetect_mtu=no" to module-bluetooth-discover in /etc/pulse/default.pa. If that fixes the problem, then please report the problem to the BlueZ and/or PulseAudio developers, so that the kernel can be fixed. Update: We decided to disable the MTU autodetection in 11.1 by default, because the feature caused too much problems and it looked like the kernel would not really get fixed even when people reported issues." Presume its a config option in the kernel that differs on each model. Pi3/4 should be 64 as they are very much like the 48 byte packages in reverse as don't work with the default of 48. Its listed as Pulse audio but presume it should be a config setting of the kernel for each Pi model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865257/+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
