[Desktop-packages] [Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
I'm also experiencing this problem after upgrading to Ubuntu 19.10. I'm using xserver-xorg-video-amdgpu 19.0.1-1ubuntu1 so either it's not completely fixed, or I'm experiencing a different but very similar issue. One of the linked bug reports suggested the crash occurs in the XFCE compositor. I tried disabling the compositor: xfconf-query -c xfwm4 -p /general/use_compositing -s false This seems to be a usable workaround for now, though it does introduce some visual glitches. -- More detail: After booting to login screen, if I select an "XFCE" or "Xubuntu" session and log in, the system crashes to a black screen and is unresponsive to Ctrl-Alt-F2 or Ctrl-Alt-Del or anything else I try. (Alt+SysRq+b does reboot though.) Selecting an "Ubuntu" session is fine. After rebooting, I see 232 lines in syslog like this: WARNING: CPU: 2 PID: 274 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] -- Hardware and version info: $ cat /proc/cpuinfo model name : AMD Ryzen 5 2400G with Radeon Vega Graphics $ lsb_release -a Description:Ubuntu 19.10 Release:19.10 Codename: eoan $ uname -r 5.3.0-23-generic $ apt show xserver-xorg Version: 1:7.7+19ubuntu12 $ apt show xserver-xorg-core Version: 2:1.20.5+git20191008-0ubuntu1 $ apt show xserver-xorg-video-amdgpu Version: 19.0.1-1ubuntu1 $ xfce4-session --version xfce4-session 4.14.0 (Xfce 4.14) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) Status in Linux: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: This is a freeze which is obviously caused by a bug in the xserver- xorg-video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eoan" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+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 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
It sounds like the dmic is connected to PCH instead of codec. please generate a log under windows10 by this tool. thx. ** Attachment added: "RtHDDump_V236.zip" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+attachment/5306138/+files/RtHDDump_V236.zip -- 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/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
uname -a Linux lilian-dev 5.0.0-37-generic #41+redmiv2 SMP Mon Nov 18 05:09:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 1. installed as the order below: 789 sudo dpkg -i linux-headers-5.0.0-37_5.0.0-37.41+redmiv2_all.deb 790 sudo dpkg -i linux-headers-5.0.0-37-generic_5.0.0-37.41+redmiv2_amd64.deb 792 sudo dpkg -i linux-modules-5.0.0-37-generic_5.0.0-37.41+redmiv2_amd64.deb 793 sudo dpkg -i linux-modules-extra-5.0.0-37-generic_5.0.0-37.41+redmiv2_amd64.deb 794 sudo dpkg -i linux-image-unsigned-5.0.0-37-generic_5.0.0-37.41+redmiv2_amd64.deb 2. restart and boot to the test kernel. 3. Open settings and find Input tag from Sound. - The internal mic was not visible 3. insert the external mic - It appears as "Microphone - BuiltinAudio" - unplug it, still appears as "Microphone - BuiltinAudio" 4. Test recording for no external mic case: - no sound at all. - no change even change the input sound level to max in settings 5. Test recording for external mic case - no sound at all. - no change even change the input sound level to max in settings Attached alsa-info.ext collected ** Attachment added: "alsa-info.txt.p8ApzEvbP8" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5306137/+files/alsa-info.txt.p8ApzEvbP8 -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
** Attachment added: "pactl_list_before_switching_output_device_back_and_forth.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850766 Title: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 (using -proposed pocket) Kernel 5.3.0-21-generic #22 pulseaudio 1:13.0-1ubuntu1 bluez 5.50-0ubuntu4 Device: Dell Inspiron 7370 Step to reproduce = 1. Pair a bluetooth headset with the laptop 2. Go to sound settings -> in "Output device", the bluetooth headset is selected 3. Click Test, then "Front Left" and/or "Front Right" -> the sound outputs to the laptop speakers instead of the bluetooth headset If I select "Speakers - Built-in audio" in the "Output device", then select back the bluetooth headset from the "Output device" list and test it, it works as expected. I tried this with 2 different bluetooth headsets (UE Boom and TaoTronics TT-BH07) which work fine on an Android device. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1532 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 31 17:36:10 2019 InstallationDate: Installed on 2019-07-02 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850766/+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 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
I ran the following steps: 1. Power laptop on with bluetooth turned off 2. Turn BT on in gnome settings and set my BT headphones in pairing mode 3. Pair the headphones. 4. In Sound settings, it looks like the selected device is the BT headphones, but if I play something it outputs on the laptop speakers. output of `pactl list` gives something interesting though: Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 30421 / 46% / -20.00 dB, front-right: 30421 / 46% / -20.00 dB balance 0.00 Base Volume: 6554 / 10% / -60.00 dB Monitor of Sink: n/a Latency: 123 usec, configured 4 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC3254 Analog" alsa.id = "ALC3254 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xd1128000 irq 128" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC3254" alsa.components = "HDA:10ec0295,102807e9,0012 HDA:8086280b,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-input-internal-mic: Internal Microphone (priority: 8900) analog-input-headphone-mic: Microphone (priority: 8700, not available) analog-input-headset-mic: Headset Microphone (priority: 8800, not available) Active Port: analog-input-internal-mic Formats: pcm Source #2 State: SUSPENDED Name: bluez_sink.E3_28_E9_21_94_78.a2dp_sink.monitor Description: Monitor of TaoTronics TT-BH07 Driver: module-bluez5-device.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 25 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: bluez_sink.E3_28_E9_21_94_78.a2dp_sink Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of TaoTronics TT-BH07" device.class = "monitor" device.string = "E3:28:E9:21:94:78" device.api = "bluez" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_E3_28_E9_21_94_78" bluez.class = "0x240404" bluez.alias = "TaoTronics TT-BH07" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" Formats: pcm This matches what I have, but not what I see in Sound settings. 5. Now, if I select the speakers as the output device in the sound settings, then back to BT device, the sound is correctly output to the BT headphones (and not the laptop speakers), and I see this in `pactl list`: Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 30421 / 46% / -20.00 dB, front-right: 30421 / 46% / -20.00 dB
[Desktop-packages] [Bug 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Yes, the internal microphone works perfectly fine in Windows 10 and is being detected as Intel Smart Sound -- 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/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
** Attachment added: "pactl_list_after_switching_output_device_back_and_forth.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850766 Title: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 (using -proposed pocket) Kernel 5.3.0-21-generic #22 pulseaudio 1:13.0-1ubuntu1 bluez 5.50-0ubuntu4 Device: Dell Inspiron 7370 Step to reproduce = 1. Pair a bluetooth headset with the laptop 2. Go to sound settings -> in "Output device", the bluetooth headset is selected 3. Click Test, then "Front Left" and/or "Front Right" -> the sound outputs to the laptop speakers instead of the bluetooth headset If I select "Speakers - Built-in audio" in the "Output device", then select back the bluetooth headset from the "Output device" list and test it, it works as expected. I tried this with 2 different bluetooth headsets (UE Boom and TaoTronics TT-BH07) which work fine on an Android device. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1532 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 31 17:36:10 2019 InstallationDate: Installed on 2019-07-02 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850766/+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 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS
@GrzesiekC, can you check for apparmor denials when running thunderbird? I.e. have a terminal running "journalctl -f | grep DEN", and share the output here. Do you have an apparmor profile being enforced for thunderbird? I.e. what is the output of: sudo apparmor_status | grep thunderbird -- 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/1850064 Title: Please upgrade it to 68.x on Ubuntu 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Committed Bug description: Now the official upgrade way from 60 to 68 got open by mozilla. Plus there are security fixes and performance enhancements. https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2 NOTE TO SRU TEAM: Please do not release this package without consulting first. This is a security update pushed via -proposed to get a bit more testing. Will be released via it's own processes. Packages that are part of this security update: thunderbird, mozilla- devscripts, jsunit and enigmail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850064/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
please test the v2 kernel, at least you could see a front mic as internal mic from UI. https://people.canonical.com/~hwang4/redmi/v2/ make sure the kernel is redmiv2 by checking with uname -a thx. -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
1) external mic not plugin :~$ sudo hdajacksensetest -a [sudo] password for lilian: Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Left side): present = Yes Pin 0x1a (Black Mic, Right side): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Left side): present = No External mic plug in sudo hdajacksensetest -a Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Left side): present = Yes Pin 0x1a (Black Mic, Right side): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Left side): present = Yes -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
1. installed as the order below: sudo dpkg -i linux-image-xxx.deb sudo dpkg -i linux-modules-.deb sudo dpkg -i linux-modules-extra-xxx.deb 2. restart and boot to the test kernel. 3. Open settings and find Input tag from Sound. - The internal mic was not visible 3. insert the external mic - It appears as "Microphone - BuiltinAudio" - unplug it, still appears as "Microphone - BuiltinAudio" 4. Test recording for no external mic case: - Only random electric noise. 5. Test recording for external mic case - Only random electric noise. Attached alsa-info.ext collected ** Attachment added: "alsa-info.txt.cX0MHoMXkI" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5306128/+files/alsa-info.txt.cX0MHoMXkI -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
Can also confirm the issue is fixed with the -proposed package -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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 1842022] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1842022 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync() Status in ibus package in Ubuntu: Expired Bug description: Didn't do anything special. Logged out and checked if "Ubuntu" or Ubuntu on Wayland" was set and "Ubuntu" was set. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 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: ubuntu:GNOME Date: Fri Aug 30 08:47:18 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2019-08-02 (27 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 SegvAnalysis: Segfault happened at: 0x7fd6131738ce <__vfprintf_internal+30>: mov %rsi,-0x4b8(%rbp) PC (0x7fd6131738ce) ok source "%rsi" ok destination "-0x4b8(%rbp)" (0x7ffdb5e52bf8) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() 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/ibus/+bug/1842022/+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 1843927] Re: HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1843927 Title: HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8] Status in xorg-server package in Ubuntu: Expired Bug description: I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY laptop. The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor. No warnings where raised during the installation process regarding problems with the graphics driver. When I connected a HDMI connected monitor I found it did not work. I have attached the graphics driver logs == cat /var/log/gpu-manager.log log_file: /var/log/gpu-manager.log last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot can't access /run/u-d-c-nvidia-was-loaded file can't access /opt/amdgpu-pro/bin/amdgpu-pro-px Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms Is nvidia loaded? no Was nvidia unloaded? no Is nvidia blacklisted? no Is intel loaded? no Is radeon loaded? no Is radeon blacklisted? no Is amdgpu loaded? no Is amdgpu blacklisted? no Is amdgpu versioned? no Is amdgpu pro stack? no Is nouveau loaded? no Is nouveau blacklisted? no Is nvidia kernel module available? no Is amdgpu kernel module available? no Vendor/Device Id: 1002:67ef BusID "PCI:1@0:0:0" Is boot vga? no Error: can't access /sys/bus/pci/devices/:01:00.0/driver The device is not bound to any driver. Vendor/Device Id: 1002:15d8 BusID "PCI:5@0:0:0" Is boot vga? yes Error: can't access /sys/bus/pci/devices/:05:00.0/driver The device is not bound to any driver. Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Does it require offloading? no last cards number = 2 Has amd? yes Has intel? no Has nvidia? no How many cards? 2 Has the system changed? No Unsupported discrete card vendor: 1002 Nothing to do == sudo lshw -C display *-display UNCLAIMED description: Display controller product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: e5 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi cap_list configuration: latency=0 resources: memory:e000-efff memory:f000-f01f ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5 *-display UNCLAIMED description: VGA compatible controller product: Picasso vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:05:00.0 version: c2 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: latency=0 resources: memory:c000-cfff memory:d000-d01f ioport:c000(size=256) memory:fe50-fe57 * QUESTIONS 1. Why is the problem with unsupported drivers not flagged during the installation process? The default driver does work for the laptop's monitor, but will not drive a second monitor attached to the HDMI port 2. I have seen reference to a general purpose AMD graphics driver, but there is no reference to this driver being supported on Ubuntu 19.04. If I went ahead and attempted to install the general purpose graphics driver, how would I back it out if it did not work. I have raised this issue as a "question", but I think it is probably a bug but I could not find out how to raise a bug associated with a lack of device drivers. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: disco DistroRelease: Ubuntu 19.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-25-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-27-generic, x86_64: installed rtl8821ce, 1.0.0, 5.0.0-25-generic, x86_64: installed rtl8821ce, 1.0.0, 5.0.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 460/560D / Pro
[Desktop-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
Please install and test this kernel, at least you could see the internal mic, and maybe the internal mic can work. https://people.canonical.com/~hwang4/redmi/v1/ And please also test the external mic. If they don't work as expected, please collect an alsa-info.txt with coeff enabled. sudo su echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef Then run alsa-info to collect alsa-info.txt. thx. -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1791454] Re: system-monitor produces many apparmor permission denied warnings
My new machine (one week old) is receiving these as well: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ journalctl | grep "operation=\"open\" profile=\"snap.gnome-system-monitor.gnome" | wc -l 77549 which half the log! $ journalctl | wc -l 144263 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1791454 Title: system-monitor produces many apparmor permission denied warnings Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: gnome-system-monitor (installed as snap, latest stable version) on Ubuntu 18.04.1 causes while running many warnings in the system log of the following type: audit[2095]: AVC apparmor="DENIED" operation="open" profile="snap .gnome-system-monitor.gnome-system-monitor" name="/proc/2932/wchan" pid=2095 comm="gnome-system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 audit[2095]: AVC apparmor="DENIED" operation="open" profile="snap .gnome-system-monitor.gnome-system-monitor" name="/proc/1/cgroup" pid=2095 comm="gnome-system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 The output of journalctl | grep "operation=\"open\" profile=\"snap.gnome-system-monitor.gnome" | wc -l amounts on my system to 4 924 215 . For comparison journalctl | wc -l amounts to 5 143 715 . Thus it is really spamming my system log. output of snap info gnome-system-monitor is attached. output of lsb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791454/+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 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Has the internal mic ever worked before? or on other OS like windows or other linux distributions? -- 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/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1850651]
First of all, TB 68.2.1 with gData 68.2.1 installed from https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for- google-calendar/ should work. The workaround is described in comment #22. -- 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/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Triaged Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Triaged Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 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) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+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 1850651]
(In reply to llh from comment #71) > (In reply to paul from comment #23) > > I tested the workaround with gData for Calendar and it worked as expected. > > Confirmed! /Lars What is this workaround you mention? I'm still stuck -- 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/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Triaged Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Triaged Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 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) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+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 1807056] Re: Occasional Keyboard freeze
I took a screenshot of typing switching to dash search box as reported in comment #46. Typing froze, and what I typed was put into the dash search box as seen below. It was supposed to be in the browser where I was typing it. ** Attachment added: "keyboard freeze.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+attachment/5306125/+files/keyboard%20freeze.png -- 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/1807056 Title: Occasional Keyboard freeze Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/907 --- I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1807056/+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 1839837] Re: Your icon theme suffers from uncanny valley effect
** Bug watch added: Red Hat Bugzilla #1740610 https://bugzilla.redhat.com/show_bug.cgi?id=1740610 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1740610 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1839837 Title: Your icon theme suffers from uncanny valley effect Status in yaru-theme package in Ubuntu: Opinion Status in Fedora: Unknown Bug description: Your icon theme suffers from uncanny valley effect. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1839837/+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 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Update: the issue at GNOME repository was re-classified from nautilus- related to glib-related: https://gitlab.gnome.org/GNOME/glib/issues/1942 . ** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1942 https://gitlab.gnome.org/GNOME/glib/issues/1942 -- 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/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in nautilus package in Ubuntu: New Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+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 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
I can actually only get this to manifest *for files created by Nautilus*. Files that are created from an ssh session or by cd-ing into the /run/user/1000/... directory are unaffected. So I guess this also affects Nautilus? ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1813679] Re: vim-gtk can no longer save to GVFS STFP mounts in 18.04
This is an interaction between vim and GVFS, so I've added GVFS as affected. ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - vim-gtk can no longer save to GVFS STFP mounts in 18.04 + vim-gtk can no longer save to GVFS SFTP mounts in 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1852922] [NEW] Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
Public bug reported: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description:Ubuntu 19.10 Release:19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+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 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Thanks for pointing that out because I also had __GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot to mention that in my previous comment to yours here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+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 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
** Attachment added: "Screenshot of a message that requires extra authentication." https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+attachment/5306087/+files/Screenshot%20from%202019-11-15%2022-01-33-1.png -- 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/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in nautilus package in Ubuntu: New Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+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 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Thank you Sebatien for looking into that. The GNOME bug is filed as https://gitlab.gnome.org/GNOME/nautilus/issues/1293 . ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1293 https://gitlab.gnome.org/GNOME/nautilus/issues/1293 -- 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/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in nautilus package in Ubuntu: New Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
Just had a look at my own settings: I have "Dim display when idle" unchecked in the AC power tab, checked in the Battery tab. I am still getting a dark screen every now and then, even though I mostly work on AC power. -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
@Maik Schulze did that change anything? are you still getting the error? -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Additionnal note for the previous comment: it also works when Sync to VBlank is enabled (tested with glxgears), but causes tearing for the 60 hz monitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+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 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Hello, In my case, appending __GL_SYNC_DISPLAY_DEVICE=DP-0 in the /etc/environment file (DP-0 is my 144hz monitor - see X Server XVideo Settings in NVIDIA X Server Settings) seems to works (config: GTX 1070/60 Hz + 144 Hz monitors). I forced resolution + frequency in NVIDIA X Server Settings for the two monitors in the X Server Display Configuration section. Disabled Force Composition Pipeline + Force Full Composition Pipeline. Disabled Sync to VBlank + Allow Flipping (OpenGL Settings). NVIDIA driver version: 435.21 (the latest in Ubuntu 18.04.3 with HWE enabled). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+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 1852911] [NEW] CriticalPowerAction=Suspend should be supported
Public bug reported: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in upower package in Ubuntu: New Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+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 1756901] Re: GNOME Calendar crashes in remove_source when I try to add my Google Calendar account
** Changed in: gnome-calendar Status: Unknown => Fix Released -- 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/1756901 Title: GNOME Calendar crashes in remove_source when I try to add my Google Calendar account Status in GNOME Calendar: Fix Released Status in gnome-calendar package in Ubuntu: Triaged Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1756901/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
Black internal screen on my G1 820 too. May be its a problem with function "lower screen intensity when inactive" (energy), i have disabled it now. -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1852908] Re: Reboot button does nothing on login screen
*** This bug is a duplicate of bug 1847896 *** https://bugs.launchpad.net/bugs/1847896 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1847896, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1847896 Unable to shutdown or restart from log-in screen -- 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/1852908 Title: Reboot button does nothing on login screen Status in gnome-shell package in Ubuntu: New Bug description: Hi, When I'm boot my computer and the Gnome Shell login screen appears, if I try to reboot the computer from the menu available in the top right, the button does nothing. I tried clicking multiple times, my computer won't reboot. However, If i'm logged into my desktop, and then ask for a reboot, it works. So either there is a permission issue to reboot on Gnome Shell login screen, or there is a deeper issue here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 13:52:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-26 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-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/1852908/+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 1852908] [NEW] Reboot button does nothing on login screen
Public bug reported: Hi, When I'm boot my computer and the Gnome Shell login screen appears, if I try to reboot the computer from the menu available in the top right, the button does nothing. I tried clicking multiple times, my computer won't reboot. However, If i'm logged into my desktop, and then ask for a reboot, it works. So either there is a permission issue to reboot on Gnome Shell login screen, or there is a deeper issue here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 13:52:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-26 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1852908 Title: Reboot button does nothing on login screen Status in gnome-shell package in Ubuntu: New Bug description: Hi, When I'm boot my computer and the Gnome Shell login screen appears, if I try to reboot the computer from the menu available in the top right, the button does nothing. I tried clicking multiple times, my computer won't reboot. However, If i'm logged into my desktop, and then ask for a reboot, it works. So either there is a permission issue to reboot on Gnome Shell login screen, or there is a deeper issue here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 13:52:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-26 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-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/1852908/+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 1849055] Re: gnome-extensions fails to load after boot
I too have the same problem with my Dell Inspiron 1525. I doubt it's the extension Dash to Panel that's getting kicked out. -- 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/1849055 Title: gnome-extensions fails to load after boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions that I have enabled fail to load. I am forced to go each time to gnome-tweaks to re-enable these extensions which is very frustrating. This worked fine in Ubuntu 19.04. I am using a Dell Inspiron 1420 laptop. Thank you for any help with this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:14:29 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3] InstallationDate: Installed on 2016-01-26 (1363 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 1420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0Y918J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 xserver.bootTime: Sun Oct 20 21:04:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.5+git20191008-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: lightdm DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2016-01-26 (1363 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1756901] Re: GNOME Calendar crashes in remove_source when I try to add my Google Calendar account
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/issues #264 https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264 Importance: Unknown Status: Unknown -- 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/1756901 Title: GNOME Calendar crashes in remove_source when I try to add my Google Calendar account Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Triaged Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1756901/+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 1781049] Re: WiFi hard blocked after resuming laptop from suspend
I have the same problem with Asus K54HR, rfkill says that phy0 is hard blocked. I tried to reinstall Ubuntu 19.04 and 19.10, reset the bios, with no solution. WiFi works well on Windows 10. I am happy to provide any additional information to solve the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781049 Title: WiFi hard blocked after resuming laptop from suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythreya 1281 F pulseaudio /dev/snd/controlC1: mythreya 1281 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-26 (16 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.87 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-30T14:39:45.608645 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2018-06-28T16:23:51.596655 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR71 1a9d81bf-e7f5-4f8a-956f-96180dc493e1 wifi 1531450229 Thu 12 Jul 2018 09:50:29 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlo1activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Ethernet 81087af0-5c8d-451f-84c0-1a95c6034098 ethernet 1530214661 Thu 28 Jun 2018 02:37:41 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 no
[Desktop-packages] [Bug 1852900] Re: Gnome-shell restart-refresh causes minimized applications to become unresponsive and unminimized
In this attachment it can be seen that Minimized Nautilus File Manager
is unminimized and unresponsive after Gnome Shell refresh/reload.
Also Nautlilus become responsive when I click to open Nautilus File
Manager.
** Attachment added: "After Gnome-Shell refresh/reload, Minimized Nautilus File
Manager becomes unminimized and unresponsive"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852900/+attachment/5306043/+files/Screencast%20from%202019-11-17%2012%3A32%3A03.webm
** Description changed:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
- become unminimized after gnome-shell restart and become unresponsive,
- unless I press to minimize/maximize them, they won't be responsive.
+ become unminimized after gnome-shell restart and also become
+ unresponsive, unless I press to minimize/maximize them, they will stay
+ permanently unresponsive.
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval
s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
become unminimized after gnome-shell restart and also become
- unresponsive, unless I press to minimize/maximize them, they will stay
- permanently unresponsive.
+ unresponsive, unless I press to minimize/maximize them, these
+ applications stay permanently unresponsive.
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval
s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
--
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/1852900
Title:
Gnome-shell restart-refresh causes minimized applications to become
unresponsive and unminimized
Status in gnome-shell package in Ubuntu:
New
Bug description:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
become unminimized after gnome-shell restart and also become
unresponsive, unless I press to minimize/maximize them, these
applications stay permanently unresponsive.
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell
Eval s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-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/1852900/+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 1852900] [NEW] Gnome-shell restart-refresh causes minimized applications to become unresponsive and unminimized
Public bug reported:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
become unminimized after gnome-shell restart and become unresponsive,
unless I press to minimize/maximize them, they won't be responsive.
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval
s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
** Description changed:
+ Let's say you have minimized one or more applications such as Firefox,
+ Gnome Tweaks or even Nautilus File Manager. These applications will be
+ become unminimized after gnome-shell restart and become unresponsive,
+ unless I press to minimize/maximize them, they won't be responsive.
+
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval
s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
--
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/1852900
Title:
Gnome-shell restart-refresh causes minimized applications to become
unresponsive and unminimized
Status in gnome-shell package in Ubuntu:
New
Bug description:
Let's say you have minimized one or more applications such as Firefox,
Gnome Tweaks or even Nautilus File Manager. These applications will be
become unminimized after gnome-shell restart and become unresponsive,
unless I press to minimize/maximize them, they won't be responsive.
No matter what is your method of restarting Gnome Shell:
Either combination of ALT+F2+R
Or a command line command:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell
Eval s 'Meta.restart("Restarting…")'
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 17 12:22:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-07-20 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
RelatedPackageVersions: mutter-common 3.34.1-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/1852900/+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 1852890] Re: Nautilus freezes when trying to delete an item from the desktop
Correction: When I said "Alt+F2" above, I meant "Ctrl+Alt+F1", as the whole X had frozen. I should also mention that I'm running a Radeon RX 5700 GPU with the default AMDGPU driver - and am separately experiencing random GPU lockups, which could explain the whole-screen lockup I mentioned in parentheses - but the Nautilus issue feels separate because of its reproducability. -- 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/1852890 Title: Nautilus freezes when trying to delete an item from the desktop Status in nautilus package in Ubuntu: New Bug description: When hitting the delete key on an item on the desktop, a beep is emitted, and nothing happens. When launching a separate Nautilus window, navigating to ~/Desktop, and trying to delete items from this folder, the Nautilus window freezes. At this point, no new Nautilus windows can be launched, and the window eventually emits a ""Files" is not responding" dialog. (When trying to reproduce this bug for this report, the whole screen froze and I had to escape with Alt+F2 - not sure if this is a separate bug). When launching nautilus from a terminal, and repeating the procedure above, no error message or other output is printed to the terminal. The file in question was steam.desktop, and I then deleted it using rm without any issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 08:05:39 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1245, 746)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-11-07 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852890/+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 1852890] [NEW] Nautilus freezes when trying to delete an item from the desktop
Public bug reported: When hitting the delete key on an item on the desktop, a beep is emitted, and nothing happens. When launching a separate Nautilus window, navigating to ~/Desktop, and trying to delete items from this folder, the Nautilus window freezes. At this point, no new Nautilus windows can be launched, and the window eventually emits a ""Files" is not responding" dialog. (When trying to reproduce this bug for this report, the whole screen froze and I had to escape with Alt+F2 - not sure if this is a separate bug). When launching nautilus from a terminal, and repeating the procedure above, no error message or other output is printed to the terminal. The file in question was steam.desktop, and I then deleted it using rm without any issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 08:05:39 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1245, 746)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-11-07 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1852890 Title: Nautilus freezes when trying to delete an item from the desktop Status in nautilus package in Ubuntu: New Bug description: When hitting the delete key on an item on the desktop, a beep is emitted, and nothing happens. When launching a separate Nautilus window, navigating to ~/Desktop, and trying to delete items from this folder, the Nautilus window freezes. At this point, no new Nautilus windows can be launched, and the window eventually emits a ""Files" is not responding" dialog. (When trying to reproduce this bug for this report, the whole screen froze and I had to escape with Alt+F2 - not sure if this is a separate bug). When launching nautilus from a terminal, and repeating the procedure above, no error message or other output is printed to the terminal. The file in question was steam.desktop, and I then deleted it using rm without any issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 08:05:39 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1245, 746)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-11-07 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852890/+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
