date:20200607

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1877102

Title:
  snap policy module can be unloaded, circumventing audio recording
  restrictions for snaps

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This collates information about a security vulnerability discussed in
  email.  It has been assigned CVE-2020-11931.

  Ubuntu's PulseAudio package is shipped with a custom "module-snap-
  policy" module intended to restrict snap confined clients from
  recording audio unless they have the "audio-record" plug connected.
  However, it does not restrict access to the "PA_COMMAND_UNLOAD_MODULE"
  command.

  This allows a snap that has only plugged "audio-playback" to request
  that PulseAudio unload the security policy module, which in turn makes
  it possible to record audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877102/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1876065

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  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: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1866194

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/pulseaudio/+bug/1866194/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1882016] Re: Unable to uninstall Calibre

2020-06-07 Thread Robert Uomini

Thank you, Hans.

Regards,

Bob

On Sun, Jun 7, 2020 at 12:35 PM Hans Joachim Desserud <
1882...@bugs.launchpad.net> wrote:

> Then I don't know I'm afraid. I've marked this as also affecting gnome-
> software for someone to take a look at it from that angle.
>
> ** Also affects: gnome-software (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: calibre (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1882016
>
> Title:
>   Unable to uninstall Calibre
>
> Status in calibre package in Ubuntu:
>   New
> Status in gnome-software package in Ubuntu:
>   New
>
> Bug description:
>   When I try to remove Calibre, I get an error "No packages to remove".
>   Same thing with E-book editor, LRF Viewer and E-book viewer. Is this
>   malware?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: calibre (not installed)
>   ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
>   Uname: Linux 5.4.0-33-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.2
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Jun  4 06:48:01 2020
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-20160624-2
>   InstallationDate: Installed on 2018-03-12 (815 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20160624-10:47
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: calibre
>   UpgradeStatus: Upgraded to focal on 2020-05-08 (26 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1882016/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1882016

Title:
  Unable to uninstall Calibre

Status in calibre package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I try to remove Calibre, I get an error "No packages to remove".
  Same thing with E-book editor, LRF Viewer and E-book viewer. Is this
  malware?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: calibre (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 06:48:01 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-03-12 (815 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: calibre
  UpgradeStatus: Upgraded to focal on 2020-05-08 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1882016/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-06-07 Thread Lyubomir Parvanov

Also experience the issue with Intel Corporation Dual Band Wireless-AC
3168NGW [Stone Peak]. Ubuntu 20.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1859308

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+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 1838249]

2020-06-07 Thread Qa-admin-q

Dear Davide Soresinetti,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249

Title:
  crash on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-29 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Tags:  disco
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1838249/+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 1860827] Re: [snap] chromium does not open

Thanks for the feedback.
Issue resolved by updates.
Closing as per above request.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1860827

Title:
  [snap] chromium does not open

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Just upgraded to fossa.  When clicking chromium-browser, title bar
  switches to "Chromium Web Browser", spins for awhile and then
  disappears nothing opens.

  If it helps, running 'chromium-browser' at CLI is:

  mark@zynxps:~$ chromium-browser
  Failed to move to new namespace: PID namespaces supported, Network namespace 
supported, but failed: errno = Operation not permitted
  Trace/breakpoint trap (core dumped)
  mark@zynxps:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 79.0.3945.79-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 15:55:10 2020
  InstallationDate: Installed on 2018-10-06 (475 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   55   Done2020-01-24T12:55:57-08:00  2020-01-24T12:56:26-08:00  Install 
"chromium" snap
   56   Done2020-01-24T14:30:02-08:00  2020-01-24T14:30:02-08:00  Connect 
chromium:password-manager-service to core:password-manager-service
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117 
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
  Snap.ChromiumVersion: Chromium 79.0.3945.117 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860827/+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 1838249] Re: crash on startup

2020-06-07 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: Incomplete => Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249

Title:
  crash on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice --norestore --safe-mode
  dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
  This is normally a bug in some application using the D-Bus library.

D-Bus not built with -rdynamic so unable to print a backtrace

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d]
  /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4]
  
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669]
  
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e]
  /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-29 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Tags:  disco
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1838249/+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 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2020-06-07 Thread Krishna Sai Chintala

Same with me, tried in 18.04 and 20.04 versions. No sound in internal
speakers and in 3.5mm audio jack but works with bluetooth headset and
type-c earphones.

-- 
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/1834566

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+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 1882434] [NEW] gnome-shell crashes on lock screen

2020-06-07 Thread JP

Public bug reported:

I upgraded to Ubuntu 20.04 LTS
Now, when I lock my screen (super + L or in the menu), gnome-shell crashes (my 
dash panel disappear and restarts)

lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

apt-cache policy gnome-shell
gnome-shell:
  Installé : 3.36.2-1ubuntu1~20.04.1
  Candidat : 3.36.2-1ubuntu1~20.04.1
 Table de version :
 *** 3.36.2-1ubuntu1~20.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.1-5ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages

syslog at the time of crash :

Jun  7 17:15:28 Antec systemd[1780]: Started VTE child process 14050 launched 
by tilix process 5095.
Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] Activating 
via systemd: service name='org.freedesktop.Tracker1' 
unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata database store 
and lookup manager...
Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1'
Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata database store 
and lookup manager.
Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] Activating 
via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' 
unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata extractor...
Jun  7 17:15:48 Antec tracker-extract[14092]: Set scheduler policy to SCHED_IDLE
Jun  7 17:15:48 Antec tracker-extract[14092]: Setting priority nice level to 19
Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata extractor.
Jun  7 17:15:49 Antec gnome-shell[13114]: 
../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() virtual function.
Jun  7 17:15:50 Antec kernel: [20249.831809] traps: gnome-shell[13114] general 
protection fault ip:7fd01f2c829a sp:7ffdc90eac98 error:0 in 
libc-2.31.so[7fd01f166000+178000]
Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=11/SEGV
Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Scheduled restart 
job, restart counter is at 6.
Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session (session: 
ubuntu).
Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session (session: 
ubuntu).
Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session.
Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session.
Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME Shell on X11.
Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME Shell on X11.
Jun  7 17:15:51 Antec systemd[1780]: Stopped GNOME Shell on X11.
Jun  7 17:15:51 Antec systemd[1780]: Starting GNOME Shell on X11...
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): EDID 
vendor "ACR", prod id 134
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): Using 
hsync ranges from config file
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): Using 
vrefresh ranges from config file
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Printing DDC gathered Modelines:
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1110 
-hsync -vsync (66.6 kHz eP)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)

[Desktop-packages] [Bug 1882348] Re: Gnome shell 'Show Applications' app names commonly truncated

*** This bug is a duplicate of bug 968213 ***
https://bugs.launchpad.net/bugs/968213

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 968213, 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 968213
   Too many icons in Gnome Shell Activities Overview require ellipses

-- 
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/1882348

Title:
  Gnome shell 'Show Applications' app names commonly truncated

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The  way people browse their apps and is key to discoverability for
  new Linux users. Despite the grid layout including quite a lot of
  space, whenever apps have more than about 12-13 characters in their
  name they get truncated and even when you hover over the icons it
  still doesn't display the names of the apps. Therefore you are left
  not knowing what the app is unless you know the icon or launch the app
  to discover the full name. This is surprising common. A few examples:

  Firefox Web Br...
  LibreOffice Imp...
  LibreOffice Wri...
  Language Supp...
  Document Sca...
  Document Vie...
  Passwords and ...
  Visual Studio C...
  Software & Up...

  While we know or can guess what most of them are, there's loads of
  space so why can't we give two lines for app names so all reasonably
  named apps have their names displayed in full?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882348/+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 334624] Re: Thunderbird doesn't synchronize IMAP until the program is closed

Noted that reporter no longer uses Launchpad
and there has been no activity for 11+ years.

Using Thunderbird 68.8 and Ubuntu 18.04 I was
not able to reproduce a problem following the
steps in the bug description. I used my mail
provider's webmail and Gmail to send, receive
and delete mail. No problems found, I did not
have to close and re-open Thunderbird to see
newly arrived ir deleted mail.

Marking "Incomplete" in case anyone subscribed
to the report still sees an issue.

** Changed in: thunderbird (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/334624

Title:
  Thunderbird doesn't synchronize IMAP until the program is closed

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: thunderbird

  I'm using 64-bit Jaunty Kubuntu on two machines. I use an IMAP account
  because it's important to me that I have the same email on both
  machines.

  While I was using Intrepid, changes to my email happened immediately.
  For example, if I had both machines running with thunderbird open on
  both, if I deleted an email on one, it would be deleted on the other.
  Now, in order for the changes on one Thunderbird to propogate to the
  other I have to close Thunderbird. As soon as I do, all the changes
  I've made propogate to the other thunderbird and then on my webmail.

  The first thing I did was call my email support number, and they reset
  my account and that didn't fix it. They said no configuration changed,
  so it must be Thunderbird.

  Another example is if I have Thunderbird open and webmail open in
  Firefox, then I delete an email in Thunderbird, the email isn't
  deleted in webmail. Once I close Thunderbird, the changes I've made to
  my messages then appear in webmail. For whatever reason, Thunderbird
  does something when it closes to synchronize, instead of in real time.

  Steps to reproduce:
  1. Open Thunderbird for an IMAP account
  2. Send a test email to that account from a different account (such as 
webmail)
  3. No change in Thunderbird
  4. Close Thunderbird
  5. Open Thunderbird again
  6. The new email appears

  Expected behaviour:
  The new email should appear as soon as step #3 above

  Actual behaviour:
  The new email only appears at step #6 above, after closing and re-opening 
Thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/334624/+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 1882437] [NEW] High CPU usage by gnome-shell (until 54% of CPU)

2020-06-07 Thread Fred

Public bug reported:

"top" command show  that the process "gnome-shell" have very often a big CPU 
usage between 10% and 80%. In the same time the hard-disk seems to be used.
It's very worst than the Ubuntu 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 17:51:46 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-11-30 (190 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882437

Title:
  High CPU usage by gnome-shell (until 54% of CPU)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  "top" command show  that the process "gnome-shell" have very often a big CPU 
usage between 10% and 80%. In the same time the hard-disk seems to be used.
  It's very worst than the Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 17:51:46 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-30 (190 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882437/+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 1880954] Re: Ubuntu 20.04 freezes when logging in

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon
  
  I'm able to restart the machine using 'alt+PrtSc rseiub' but everything
  else is unresponsive.
  
  I have the following system:
  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  
  With the following package version:
  
  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1
  
  I see the following in my syslog when this happens:
  
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-23 (136 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
+ RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
+ Tags:  wayland-session focal
+ Uname: Linux 5.4.0-33-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
+ UserGroups: docker sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381239/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be

[Desktop-packages] [Bug 1880954] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381244/+files/monitors.xml.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1880954] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381243/+files/ShellJournal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1880954] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381242/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
Mo

[Desktop-packages] [Bug 1880954] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381241/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~deskt

[Desktop-packages] [Bug 1880954] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1880954/+attachment/5381240/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-p

[Desktop-packages] [Bug 1880954] Re: Ubuntu 20.04 freezes when logging in

Hi Daniel,

I did see a crash in google-chrome that seemed to coincide with the
login freeze a couple of times, but I've also seen the login freeze
occur without any crash files appearing in /var/crash.

I tried, unplugging any external monitors and I haven't witnessed the
problem occurring without any external screens, but then again the
problem seems to occur somewhat randomly.

-- 
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/1880954

Title:
  Ubuntu 20.04 freezes when logging in

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Successfully activated service 'org.gnome.Nautilus'
  May 27 14:07:06 admin2-ThinkPad-X1-Carbon-7th org.gnome.Nautilus[130586]: 
Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
  May 27 14:07:10 admin2-ThinkPad-X1-Carbon-7th systemd[1]: fprintd.service: 
Succeeded.
  May 27 14:07:22 admin2-ThinkPad-X1-Carbon-7th gsd-power[2004]: Error setting 
property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout 
was reached (g-io-error-quark, 24)
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79074.772030] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.143012] sysrq: 
Emergency Sync
  May 27 14:07:25 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.155014] 
Emergency Sync complete
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.455113] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79075.885112] sysrq: 
This sysrq operation is disabled.
  May 27 14:07:26 admin2-ThinkPad-X1-Carbon-7th kernel: [79076.256171] sysrq: 
Emergency Remount R/O
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-23 (136 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  wayland-session focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (17 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bug

[Desktop-packages] [Bug 1882440] [NEW] BadLength (poly request too large or internal Xlib length error) when using xfreerdp

2020-06-07 Thread Hans-Peter

Public bug reported:

when using xfreerdp with Windows 10 and using the a screen capture tool on the 
remote host (windows 10) xfreerdp consistently fails with BadLength X error. 
I reported this also to xfreerdp, where it was designated as potential internal 
error in X/Xlib.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 18:27:46 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
InstallationDate: Installed on 2020-05-14 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b63e-4e73-4175-99a6-641a1284aeb3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1882440

Title:
  BadLength (poly request too large or internal Xlib length error) when
  using xfreerdp

Status in xorg package in Ubuntu:
  New

Bug description:
  when using xfreerdp with Windows 10 and using the a screen capture tool on 
the remote host (windows 10) xfreerdp consistently fails with BadLength X 
error. 
  I reported this also to xfreerdp, where it was designated as potential 
internal error in X/Xlib.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 18:27:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2020-05-14 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b63e-4e73-4175

[Desktop-packages] [Bug 1882440] Re: BadLength (poly request too large or internal Xlib length error) when using xfreerdp

2020-06-07 Thread Hans-Peter

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882440/+attachment/5381249/+files/CurrentDmesg.txt

-- 
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/1882440

Title:
  BadLength (poly request too large or internal Xlib length error) when
  using xfreerdp

Status in xorg package in Ubuntu:
  New

Bug description:
  when using xfreerdp with Windows 10 and using the a screen capture tool on 
the remote host (windows 10) xfreerdp consistently fails with BadLength X 
error. 
  I reported this also to xfreerdp, where it was designated as potential 
internal error in X/Xlib.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 18:27:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2020-05-14 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b63e-4e73-4175-99a6-641a1284aeb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882440/+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 930813] Re: Fix thunderbird behaviour (hide , not quit)

*** This bug is a duplicate of bug 376715 ***
https://bugs.launchpad.net/bugs/376715

Re comment #4, found email in archive but doesn't seem to
have been discussed. So marking Papercuts task as "Won't Fix'

Upstream bug was marked as a duplicate of 
https://bugzilla.mozilla.org/show_bug.cgi?id=208923
which is also linked to LP: #376715 so marking this bug as
a duplicate of that one to close.


** Changed in: hundredpapercuts
   Status: Confirmed => Won't Fix

** Bug watch added: Mozilla Bugzilla #208923
   https://bugzilla.mozilla.org/show_bug.cgi?id=208923

** This bug has been marked a duplicate of bug 376715
   Thunderbird - feature request - nest in toolbar

-- 
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/930813

Title:
  Fix thunderbird behaviour (hide , not quit)

Status in One Hundred Papercuts:
  Won't Fix
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
   Now on clicking the [X] on the window Thunderbird quits . I'm pretty
  sure it would be much better to have TB hide on clicking the [X] (much
  like Rhythmbox does) , because I (and maybe many others) prefer having
  TB in the background .

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/930813/+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 1882445] [NEW] Applications read ICC profile always from primary monitor

2020-06-07 Thread Usamm

Public bug reported:

Ubuntu 20.04
NVidia properietary drivers
2 monitors, each with its own ICC profile loaded
Monitors are configured in "Join Displays" mode.

Image Viewer and Chrome always use the color profile of whatever monitor
is set as the Primary Display, regardless of which monitor they're on.
Refreshing the window or creating new tabs doesn't help.

Since one of my monitors is wide gamut and the other is standard gamut,
the issue is extremely glaring, leading to extremely oversaturated
colors on the wide gamut monitor if the standard gamut monitor is
primary, or extremely undersaturated colors on the standard gamut
monitor if the wide gamut one is set as primary.

Expected behaviour:
All color-managed applications apply the ICC profile of the monitor they're 
currently displayed on, as soon as they're dragged on it.
I tested that Chrome on Windows 10 uses this behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 18:23:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] 
[1462:3160]
InstallationDate: Installed on 2020-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. B450 GAMING X
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=3a087e9b-0230-4c3c-93fa-663dcecc108d ro quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450 GAMING X
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450GAMINGX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450GAMINGX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450 GAMING X
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1882445

Title:
  Applications read ICC profile always from primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  NVidia properietary drivers
  2 monitors, each with its own ICC profile loaded
  Monitors are configured in "Join Displays" mode.

  Image Viewer and Chrome always use the color profile of whatever
  monitor is set as the Primary Display, regardless of which monitor
  they're on. Refreshing the window or creating new tabs doesn't help.

  Since one of my monitors is wide gamut and the other is standard
  gamut, the issue is extremely glaring, leading to extremely
  oversaturated colors on the wide gamut monitor if the standard gamut
  monitor is primary, or extremely undersaturated colors on the standard
  gamut monitor if the wide gamut one is set as primary.

  Expected behaviour:
  All color-managed applications apply the ICC profile of the monitor they're 
currently displayed on, a

[Desktop-packages] [Bug 306673] Re: autofs timeout

2020-06-07 Thread Dark Dragon

Not yet migrated to gitlab.

** Bug watch added: bugzilla.gnome.org/ #101673
   https://bugzilla.gnome.org/show_bug.cgi?id=101673

** Changed in: nautilus
   Importance: High => Unknown

** Changed in: nautilus
   Status: Confirmed => Unknown

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #101673 => bugzilla.gnome.org/ #101673

-- 
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/306673

Title:
  autofs timeout

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  OS: Ubuntu 8.10 Intrepid, upgraded from Hardy
  Software: SSHFS, AutoFS, no changes concerning Nautilus

  I'm using SSHFS with AutoFS to mount remote shares, which I must have
  unmounted after some time because of security concerns. This has had
  me set a timeout on the AutoFS mounts.

  The problem is that when opening a remote folder in Nautilus, the timeout 
countdown starts as soon as I stop clicking on folders/files. When it's down, I 
get a password prompt.
  This is buggy behaviour to me, because if I set the timeout to 10 seconds, 
there is a password prompt every 10 seconds if I just have a remote folder open 
in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's 
still quite annoying.

  I think that it should either:
  1. Start the timeout as soon as I don't browse around or poll the file system 
manually in any other way. Then ask for a password only if user interaction 
occurs.

  2. Don't time out as long as I have an open remote folder (after
  closing the last remote directory, let AutoFS time out and unmount).
  This is how KDE's Konqueror and gnome-terminal behave.


  There is already a bug filed at the GNOME bugzilla about this. But it 
originates from 2002 and the last comment is from 2006... which is about the 
issue still not being resolved.
  That's why I'm reporting here. If anyone has a better idea who to harass into 
fixing this, speak up ;)
  Here's the GNOME bug:
  http://bugzilla.gnome.org/show_bug.cgi?id=101673

  I've also started a thread at the ubuntuforums.org:
  http://ubuntuforums.org/showthread.php?t=1003656

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/306673/+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 1882446] Re: package thunderbird 1:68.7.0+build1-0ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/thunderbird/libxul.so' before installing new versi

2020-06-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
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/1882446

Title:
  package thunderbird 1:68.7.0+build1-0ubuntu2 failed to
  install/upgrade: unable to make backup link of
  './usr/lib/thunderbird/libxul.so' before installing new version:
  Input/output error

Status in thunderbird package in Ubuntu:
  New

Bug description:
  installing update crashed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.7.0+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4753 F pulseaudio
  BuildID: 20200407160932
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445
  Channel: Unavailable
  Date: Sun Jun  7 18:00:23 2020
  DuplicateSignature:
   package:thunderbird:1:68.7.0+build1-0ubuntu2
   Unpacking thunderbird (1:68.8.0+build2-0ubuntu0.20.04.2) over 
(1:68.7.0+build1-0ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PDmKzG/169-thunderbird_1%3a68.8.0+build2-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
unable to make backup link of './usr/lib/thunderbird/libxul.so' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/thunderbird/libxul.so' 
before installing new version: Input/output error
  ForcedLayersAccel: False
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:68.7.0+build1-0ubuntu2 failed to 
install/upgrade: unable to make backup link of 
'./usr/lib/thunderbird/libxul.so' before installing new version: Input/output 
error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX504GD.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX504GD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX504GD.312:bd07/13/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF GAMING
  dmi.product.name: TUF GAMING FX504GD_FX80GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1882446/+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 1882446] [NEW] package thunderbird 1:68.7.0+build1-0ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/thunderbird/libxul.so' before installing new ver

2020-06-07 Thread Jacob McLeod

Public bug reported:

installing update crashed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: thunderbird 1:68.7.0+build1-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 4753 F pulseaudio
BuildID: 20200407160932
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.445
Channel: Unavailable
Date: Sun Jun  7 18:00:23 2020
DuplicateSignature:
 package:thunderbird:1:68.7.0+build1-0ubuntu2
 Unpacking thunderbird (1:68.8.0+build2-0ubuntu0.20.04.2) over 
(1:68.7.0+build1-0ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-PDmKzG/169-thunderbird_1%3a68.8.0+build2-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
  unable to make backup link of './usr/lib/thunderbird/libxul.so' before 
installing new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/thunderbird/libxul.so' 
before installing new version: Input/output error
ForcedLayersAccel: False
IpRoute:
 default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird 1:68.7.0+build1-0ubuntu2 failed to install/upgrade: 
unable to make backup link of './usr/lib/thunderbird/libxul.so' before 
installing new version: Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX504GD.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX504GD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX504GD.312:bd07/13/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF GAMING
dmi.product.name: TUF GAMING FX504GD_FX80GD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
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/1882446

Title:
  package thunderbird 1:68.7.0+build1-0ubuntu2 failed to
  install/upgrade: unable to make backup link of
  './usr/lib/thunderbird/libxul.so' before installing new version:
  Input/output error

Status in thunderbird package in Ubuntu:
  New

Bug description:
  installing update crashed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.7.0+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4753 F pulseaudio
  BuildID: 20200407160932
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445
  Channel: Unavailable
  Date: Sun Jun  7 18:00:23 2020
  DuplicateSignature:
   package:thunderbird:1:68.7.0+build1-0ubuntu2
   Unpacking thunderbird (1:68.8.0+build2-0ubuntu0.20.04.2) over 
(1:68.7.0+build1-0ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PDmKzG/169-thunderbird_1%3a68.8.0+build2-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
unable to make backup link of './usr/lib/thunderbird/libxul.so' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/thunderbird/libxul.so' 
before installing new version: Input/output error
  ForcedLayersAccel: False
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'l

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-06-07 Thread khitschler

I can confirm that #61 removes the bug.

I'm running Kubuntu 18.04 with a hwe kernel 5.3.0-51-generic
#44~18.04.2-Ubuntu. (Not 5.3.0-53 because it contains a power off bug.)

Great! Now I hope it will find a way to an "official" update.

-- 
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/1849084

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.30939

[Desktop-packages] [Bug 306673] Re: autofs timeout

2020-06-07 Thread Bug Watch Updater

Launchpad has imported 26 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=101673.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2002-12-20T09:42:55+00:00 Dmills-b wrote:

Whilst setting up some Linux boxes for normal users (who don't know about
mounting/unmounting...) I noticed that when you try to access an autofs'd
floppy drive from nautilus (1.0.4), the device will mount, but the mount
doesn't hold, it disappears as soon as the timeout (in this case 2
secondes) expires, upon which nautilus throws you back to your home directory.

The problem doesn't arise with supermount (patching the kernel is a viable
workaround).

>From what I know about autofs, I'd say that nautilus is lsing the directory
it  shows, but isn't cding to it before hand, hence the loss of lock, and
the unmounting.

I'm not too familiar with the nautilus code, so I can't say for sure, but I
think a 

sprintf(&buffer,"cd %s",dir);
system(buffer); 

in the function that's invoked when you change directory should do the
trick for this one (needs testing though, I can't quite remember if
system() opens a new shell for it's commands, which is closed upon exit, or
whether it goes straight through the applications interfaces. If it's the
former, this fix would not work).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/0


On 2002-12-20T09:56:51+00:00 Alexander Larsson wrote:

Its a lot easier to call chdir() directly instead of launching a shell
to do it. But that won't help anyway, we can't use cwd to keep the dir
open, since several directories may be open at the same time, not to
mention that it would be a very strange thing to do.

I guess we could have the view hold an open ref to the directory though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/1


On 2002-12-20T09:59:05+00:00 Alexander Larsson wrote:

Not to mention what happens when you go to a uri with "; rm -rf /" at
the end...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/2


On 2003-07-05T23:28:14+00:00 Kjartan Maraas wrote:

Is this still a problem with 2.2 or newer?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/3


On 2003-07-06T07:42:57+00:00 Kjartan Maraas wrote:

Just thought I'd make a note that mail to the reporter is bouncing.

: Name service error for technisys.com.ar: 
Hostfound but no data record of requested type


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/4


On 2004-02-19T08:15:45+00:00 Matthew Gatto wrote:

*** Bug 119488 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/5


On 2004-02-19T09:31:54+00:00 Matthew Gatto wrote:

*** Bug 131665 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/6


On 2004-02-19T09:40:13+00:00 Matthew Gatto wrote:

Changing Summary to reflect new info from dups, adding a URL from one
of the dups, and setting Severity -> Major since it sucks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/7


On 2004-04-01T23:44:57+00:00 Bugmaster-3 wrote:

The URL field has been removed from bugzilla.gnome.org. This URL was in
the old URL field, and is being added as a comment so that the data is
not lost. Please email bugmas...@gnome.org if you have any questions.

URL: 
http://mail.gnome.org/archives/nautilus-list/2004-January/msg00105.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/306673/comments/8


On 2004-07-28T22:45:33+00:00 Gbdavey wrote:

I just upgraded from 2.4 to 2.6 in hopes of having this bug fixed, but no luck.
 As well as loosing the window on an automounted fs after the timeout, the
computer icon that shows various fs's gives errors when trying to view an fs
that is controlled by automount.  It gives an "unable to mount the selected
volume" error with details of:
"mount:  already mounted or  busy
mount: according to mtab,  is

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-06-07 Thread Pietrek B.

The power-off bug can be fixed by installing .56 kernel. I'm using the
following PPA to get that release until it makes into official repos:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed.

-- 
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/1849084

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c6

[Desktop-packages] [Bug 1882453] [NEW] GUI blanks after long period of use

2020-06-07 Thread Chris

Public bug reported:

GUI screen goes blank with a right click on the desktop or a click on
the power button. The entire systems seems to slow too, with CPU
utilization reaching 100% at a consistent interval. This has happened
twice already after a long period of idle or when conducting many
actions with several applications. Not sure if any of it is causation
given its only happened twice and I can't replicate the problem
consistently. If you need further information reach me at
clmora...@pm.me.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
Uname: Linux 5.4.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 15:00:40 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974]
InstallationDate: Installed on 2020-05-20 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: MSI MS-7885
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic 
root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X99A SLI PLUS(MS-7885)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7885
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1882453

Title:
  GUI blanks after long period of use

Status in xorg package in Ubuntu:
  New

Bug description:
  GUI screen goes blank with a right click on the desktop or a click on
  the power button. The entire systems seems to slow too, with CPU
  utilization reaching 100% at a consistent interval. This has happened
  twice already after a long period of idle or when conducting many
  actions with several applications. Not sure if any of it is causation
  given its only happened twice and I can't replicate the problem
  consistently. If you need further information reach me at
  clmora...@pm.me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Composi

[Desktop-packages] [Bug 1882375] Re: Cinnamon custom keyboard shortcuts don't work until logout

2020-06-07 Thread Daniel Pirch

** Package changed: gnome-settings-daemon (Ubuntu) => cinnamon (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1882375

Title:
  Cinnamon custom keyboard shortcuts don't work until logout

Status in cinnamon package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  cinnamon: 4.4.8-4
  cinnamon-settings-daemon: 4.4.0-3

  Steps to Reproduce:
  - on Cinnamon desktop, run cinnamon-settings
  - go to Keyboard > Shortcuts > Custom Shortcuts
  - add a custom shortcut, or edit the command or shortcut of an existing 
custom shortcut

  Expected behavior:
  the shortcut should become active immediately

  Actual behavior:
  the shortcut does not work until you log out and log in again

  This seems similar to bug #1243532, but I'm reporting this as a new
  bug now because it is cinnamon-specific. Other shortcuts (e.g. Close
  Window) are updated immediately, this only affects custom shortcuts. I
  think this bug appeared in 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1882375/+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 1703638] Re: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA

2020-06-07 Thread Adolfo Jayme

** Changed in: libreoffice (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1703638

Title:
  [snap] symlink ~/.fonts by default to $SNAP_USER_DATA

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  (initially reported here: https://forum.snapcraft.io/t/call-for-
  testing-libreoffice-5-3-4-snap/1205/2)

  The libreoffice snap doesn't seem to find custom fonts installed by
  the user under $HOME/.fonts/. It does find them after copying/linking
  them under $SNAP_USER_DATA/.fonts/ though, so ideally that link would
  happen automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1703638/+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 306673] Re: autofs timeout

2020-06-07 Thread Dark Dragon

I don't know how I can additionally link the following bug report in GNOME 
Gitlab:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1514

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1514
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1514

-- 
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/306673

Title:
  autofs timeout

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  OS: Ubuntu 8.10 Intrepid, upgraded from Hardy
  Software: SSHFS, AutoFS, no changes concerning Nautilus

  I'm using SSHFS with AutoFS to mount remote shares, which I must have
  unmounted after some time because of security concerns. This has had
  me set a timeout on the AutoFS mounts.

  The problem is that when opening a remote folder in Nautilus, the timeout 
countdown starts as soon as I stop clicking on folders/files. When it's down, I 
get a password prompt.
  This is buggy behaviour to me, because if I set the timeout to 10 seconds, 
there is a password prompt every 10 seconds if I just have a remote folder open 
in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's 
still quite annoying.

  I think that it should either:
  1. Start the timeout as soon as I don't browse around or poll the file system 
manually in any other way. Then ask for a password only if user interaction 
occurs.

  2. Don't time out as long as I have an open remote folder (after
  closing the last remote directory, let AutoFS time out and unmount).
  This is how KDE's Konqueror and gnome-terminal behave.


  There is already a bug filed at the GNOME bugzilla about this. But it 
originates from 2002 and the last comment is from 2006... which is about the 
issue still not being resolved.
  That's why I'm reporting here. If anyone has a better idea who to harass into 
fixing this, speak up ;)
  Here's the GNOME bug:
  http://bugzilla.gnome.org/show_bug.cgi?id=101673

  I've also started a thread at the ubuntuforums.org:
  http://ubuntuforums.org/showthread.php?t=1003656

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-06-07 Thread Mateusz Stachowski

Magnet links are working.

I just tried opening it in Chromium snap and I got the "xdg-open" prompt
and than a window with selection between qBittorrent and Transmission. I
selected qBittorrent and it opened the magnet link.

$ snap version
snap2.45
snapd 2.45
series 16
ubuntu 20.04
kernel 5.7.0-xanmod1

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1776873

Title:
Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
Triaged
Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:

https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

snapd has a hard-coded list of allowed URL schemes. Currently that is
limited to "http", "https", "mailto", "snap".

We have a number of applications in the store which are trying to use
protocol handlers outside this scope and break when that's not
possible.

e.g.

Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/

These are the ones I know of, others may also be affected. Can we
please at least expand the list to those that we know of, and perhaps
research other popular protocol handlers?

Ideally we wouldn't have a whitelist, because this delays our ability
to land new applications with as-yet unknown url schemes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1882462] [NEW] Displays wake up pre-maturely (likely driven by notification)

2020-06-07 Thread Dean Henrichsmeyer

Public bug reported:

After a period of time, my displays go to sleep as they should. However,
I often come back to find that the displays are awake, the mouse pointer
is on a screen, but the screens are otherwise black. They're in this
weird "awake but not fully on" mode. At that point, they will not go
back to sleep as they should unless I fully awake them and let them go
back to sleep.

I don't know exactly what triggers the "half awake" but I suspect it's a
notification. The displays shouldn't turn on without a user action. It
wastes power and is clearly broken. I've attached a photo for an
example.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 16:10:20 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-07-24 (684 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882462

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

2020-06-07 Thread Dean Henrichsmeyer

** Attachment added: "Screens-awake.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+attachment/5381404/+files/Screens-awake.jpg

-- 
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/1882462

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-06-07 Thread Balazs Gyurak

Just tested it too, magnet links work for me as well! Thanks

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1776873

Title:
Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
Triaged
Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:

https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

snapd has a hard-coded list of allowed URL schemes. Currently that is
limited to "http", "https", "mailto", "snap".

We have a number of applications in the store which are trying to use
protocol handlers outside this scope and break when that's not
possible.

e.g.

Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/

These are the ones I know of, others may also be affected. Can we
please at least expand the list to those that we know of, and perhaps
research other popular protocol handlers?

Ideally we wouldn't have a whitelist, because this delays our ability
to land new applications with as-yet unknown url schemes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions

[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect

2020-06-07 Thread Martin

I can confirm this issue with Epson Workforce WF-2835.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1327801

Title:
  Bightness and contrast settings have no effect

Status in simple-scan package in Ubuntu:
  Triaged

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-06-07 Thread Edward Gibbs

I have the same issue with 8260 on 20.04.  Without backports installed
the wi-fi worked but there was often a very long delay when connecting
to or loading a site.  Ran speed test (google speed test) and there was
a 15 - 20-second delay connecting to the server, but then good speed
(around 40 MBPS) was reported.  This was repeatable.  Installed
backports and selected it as the driver and the delay disappeared.  Now
connects instantly and reports the same good speed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1859308

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+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 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: hplip (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1881401

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


  $ hp-check 
  Saving output in log file: /home/mate/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=3947d85c-2c09-420b-802f-edf59648248a ro quiet splash
  SourcePackage: hplip

[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

2020-06-07 Thread Volodymyr Dudenko

I second this, if there is something included in the lts, it should
work, and HPLIP clearly doesn't. Besides that, the new version cannot be
installed either because it cannot find several dependencies, including
a required one (pyqt5).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1881401

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


  $ hp-check 
  Saving output in log file: /home/mate/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.

[Desktop-packages] [Bug 1882466] [NEW] mythtv frontend crash when calling glClear in iris driver

2020-06-07 Thread Ken

Public bug reported:

on startup, mythfrontend crashes repeatedly when calling glClear - the 
following traceback:
Core was generated by `/usr/bin/mythfrontend.real'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
[Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))]
(gdb) bt
#0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#1  0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#2  0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#6  0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, 
mask=16384)
at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628
#7  0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer (
this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801
#8  0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, 
Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136

I can work around this problem with this:
export MESA_LOADER_DRIVER_OVERRIDE=i965
(then running mythfrontend works fine)

sorry for the lack of debug symbols in iris_dri.so
if there is a .deb around with a debug version i can generate the traceback 
again
not sure if the problem belongs to iris_dri.so or to mythfrontend but I put it 
here due to the workaround.


$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 20.0.4-2ubuntu1
  Candidate: 20.0.4-2ubuntu1
  Version table:
 *** 20.0.4-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1882466

Title:
  mythtv frontend crash when calling glClear in iris driver

Status in mesa package in Ubuntu:
  New

Bug description:
  on startup, mythfrontend crashes repeatedly when calling glClear - the 
following traceback:
  Core was generated by `/usr/bin/mythfrontend.real'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))]
  (gdb) bt
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #6  0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, 
  mask=16384)
  at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628
  #7  0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer (
  this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801
  #8  0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, 
  Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136

  I can work around this problem with this:
  export MESA_LOADER_DRIVER_OVERRIDE=i965
  (then running mythfrontend works fine)

  sorry for the lack of debug symbols in iris_dri.so
  if there is a .deb around with a debug version i can generate the traceback 
again
  not sure if the problem belongs to iris_dri.so or to mythfrontend but I put 
it here due to the workaround.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 20.0.4-2ubuntu1
Candidate: 20.0.4-2ubuntu1
Version table:
   *** 20.0.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1882466/+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 1810176] Re: libmtp error could not get object handles

2020-06-07 Thread Chris

Experiencing the same problem on Ubuntu 20.04 when trying to copy files
to DCIM/Camera folder on Android Samsung a20 device.

MTP is basically unusable.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1810176

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+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 1327801] Re: Bightness and contrast settings have no effect

2020-06-07 Thread Martin

It is only an issue with the out of the box drivers, installing the proper 
Epson drivers and importantly, configuring the Network Plugin, solves the 
matter for me.
http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec6-1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1327801

Title:
  Bightness and contrast settings have no effect

Status in simple-scan package in Ubuntu:
  Triaged

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: gnome-shell (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-3.36.4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865300

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected

The bug automatically closed because we received no response to comment
#1. Please follow the instructions in comment #1 and in comment #5.

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1864287

Title:
  pulseaudio still trying to reproduce audio to HDMI without the HDMI
  cable connected

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Yesterday I was using the HDMI cable to duplicate the monitor in the
  tv and play sound with the tv by selecting HDMI exit sound in ubuntu
  settings.

  With the pc turned off I removed the HDMI from the tv but ubuntu
  doesn't automatically set the exit sound to the default till in the
  settings there is only that option and till I selected it, ubuntu was
  still trying to reproduce the audio via HDMI...

  Also rebooting the system the problem persists.

  Also by reloading pulseaudio the problem persists.

  The only solution was installing a third-party program to switch
  correctly to the default audio exit...

  lsb_release -rd:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  apt-cache policy pulseaudio:
  pulseaudio:
Installato: 1:11.1-1ubuntu7.2
Candidato:  1:11.1-1ubuntu7.4
Tabella versione:
   1:11.1-1ubuntu7.4 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 1:11.1-1ubuntu7.2 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

The most common issue we're seeing in this area right now is that gnome-
shell crashes on lock, and so locking fails. That's bug 184 with a
fix coming soon. Please also check /var/crash in case there is any
evidence there (it might be a different crash).

Secondly, we find extensions cause a lot of bugs in gnome-shell. So
please try without these:

  'system-moni...@paradoxxx.zero.gmail.com',
  'topic...@phocean.net',
  'pixel-sa...@deadalnix.me'

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882462

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+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 1882434] Re: gnome-shell crashes on lock screen

This is probably bug 184. But in case it's not...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

-- 
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/1882434

Title:
   gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 20.04 LTS
  Now, when I lock my screen (super + L or in the menu), gnome-shell crashes 
(my dash panel disappear and restarts)

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy gnome-shell
  gnome-shell:
Installé : 3.36.2-1ubuntu1~20.04.1
Candidat : 3.36.2-1ubuntu1~20.04.1
   Table de version :
   *** 3.36.2-1ubuntu1~20.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  syslog at the time of crash :

  Jun  7 17:15:28 Antec systemd[1780]: Started VTE child process 14050 launched 
by tilix process 5095.
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Activating via systemd: service name='org.freedesktop.Tracker1' 
unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
  Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata database store 
and lookup manager...
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1'
  Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata database store 
and lookup manager.
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' 
unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
  Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata extractor...
  Jun  7 17:15:48 Antec tracker-extract[14092]: Set scheduler policy to 
SCHED_IDLE
  Jun  7 17:15:48 Antec tracker-extract[14092]: Setting priority nice level to 
19
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
  Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata extractor.
  Jun  7 17:15:49 Antec gnome-shell[13114]: 
../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() virtual function.
  Jun  7 17:15:50 Antec kernel: [20249.831809] traps: gnome-shell[13114] 
general protection fault ip:7fd01f2c829a sp:7ffdc90eac98 error:0 in 
libc-2.31.so[7fd01f166000+178000]
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=11/SEGV
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 6.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session.
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Starting GNOME Shell on X11...
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): EDID 
vendor "ACR", prod id 134
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Using hsync ranges from config file
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Using vrefresh ranges from config file
  Jun  7 17:15:51 Antec /usr/

[Desktop-packages] [Bug 1882434] Re: gnome-shell crashes on lock screen

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1882434

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Tags added: focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882434

Title:
   gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 20.04 LTS
  Now, when I lock my screen (super + L or in the menu), gnome-shell crashes 
(my dash panel disappear and restarts)

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy gnome-shell
  gnome-shell:
Installé : 3.36.2-1ubuntu1~20.04.1
Candidat : 3.36.2-1ubuntu1~20.04.1
   Table de version :
   *** 3.36.2-1ubuntu1~20.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  syslog at the time of crash :

  Jun  7 17:15:28 Antec systemd[1780]: Started VTE child process 14050 launched 
by tilix process 5095.
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Activating via systemd: service name='org.freedesktop.Tracker1' 
unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
  Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata database store 
and lookup manager...
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1'
  Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata database store 
and lookup manager.
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' 
unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=1789 
comm="/usr/libexec/tracker-miner-fs " label="unconfined")
  Jun  7 17:15:48 Antec systemd[1780]: Starting Tracker metadata extractor...
  Jun  7 17:15:48 Antec tracker-extract[14092]: Set scheduler policy to 
SCHED_IDLE
  Jun  7 17:15:48 Antec tracker-extract[14092]: Setting priority nice level to 
19
  Jun  7 17:15:48 Antec dbus-daemon[1792]: [session uid=1000 pid=1792] 
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
  Jun  7 17:15:48 Antec systemd[1780]: Started Tracker metadata extractor.
  Jun  7 17:15:49 Antec gnome-shell[13114]: 
../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() virtual function.
  Jun  7 17:15:50 Antec kernel: [20249.831809] traps: gnome-shell[13114] 
general protection fault ip:7fd01f2c829a sp:7ffdc90eac98 error:0 in 
libc-2.31.so[7fd01f166000+178000]
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=11/SEGV
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  7 17:15:51 Antec systemd[1780]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 6.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME X11 Session.
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME X11 Session.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped target GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Stopping GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Stopped GNOME Shell on X11.
  Jun  7 17:15:51 Antec systemd[1780]: Starting GNOME Shell on X11...
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): EDID 
vendor "ACR", prod id 134
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Using hsync ranges from config file
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Using vrefresh ranges from config file
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Printing DDC gathered Modelines:
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1110 
-hsync -vsync (66.6 kHz eP)
  Jun  7 17:15:51 Antec /usr/lib/gdm3/gdm-x-session[1865]: (II) AMDGPU(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  60

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

Thanks but that also is failing to retrace. Try a different signal like:

  kill -SEGV ...


** Changed in: mutter (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1878275

Title:
  [qxl] wayland session hard freezes on login from GDM (X11 session
  works fine)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │ ├─gsd-power───3*[{gsd-power}]
  │ ├─gsd-print-notif───2*[{gsd-print-notif}]
  │ ├─gsd-printer───2*[{gsd-printer}]
  │ ├─gsd-rfkill───2*[{gsd-rfkill}]

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410

Title:
   GNOME Shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync 
+vsync (60.0 kHz eP)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 8

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

And if all else fails, please attach 'gdb' to the process:

  sudo gdb /usr/bin/gnome-shell PID

and retrieve a backtrace of all threads using:

  thread apply all bt

** Summary changed:

- wayland session hard freezes on login from GDM (X11 session works fine)
+ [qxl] wayland session hard freezes on login from GDM (X11 session works fine)

-- 
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/1878275

Title:
  [qxl] wayland session hard freezes on login from GDM (X11 session
  works fine)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │ ├─gsd-power───3*[{gsd

[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5

2020-06-07 Thread themusicgod1

alas there are 2 files in /var/crash neither of them line up with when
the crash happened

nothing in https://errors.ubuntu.com/user/ID since 2017

I've made the change to /etc/apport/crashdb.conf (that was the
workaround right?)

we'll see when it happens again after I reboot next

-- 
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/1882410

Title:
   GNOME Shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync 
+vsync (60.0 kHz eP)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync 
-vsync (56.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync 
(49.7 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"

[Desktop-packages] [Bug 1880954] Re: Ubuntu 20.04 freezes when logging in with external monitors connected

An upstream bug:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/938

suggests that:

  Error setting property 'PowerSaveMode' on interface
org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark,
24)

is a symptom and not the problem. So...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Summary changed:

- Ubuntu 20.04 freezes when logging in
+ Ubuntu 20.04 freezes when logging in with external monitors connected

** Tags added: multimonitor

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #938
   https://gitlab.gnome.org/GNOME/mutter/-/issues/938

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/938
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Ubuntu 20.04 freezes when logging in with external monitors connected
+ Ubuntu 20.04 freezes when logging in with external monitors connected [Error 
setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: 
Timeout was reached (g-io-error-quark, 24)]

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: mutter

** No longer affects: gnome-settings-daemon (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880954

Title:
  Ubuntu 20.04 freezes when logging in with external monitors connected
  [Error setting property 'PowerSaveMode' on interface
  org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark,
  24)]

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when logging in to my laptop, it freezes just after entering
  my password. I assume the problem package is gnome-settings-daemon
  because the only error I can see in my syslog seems to be related to
  gnome-settings-daemon

  I'm able to restart the machine using 'alt+PrtSc rseiub' but
  everything else is unresponsive.

  I have the following system:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ uname -a
  Linux admin2-ThinkPad-X1-Carbon-7th 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 
20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  With the following package version:

  $ apt show gnome-settings-daemon
  Package: gnome-settings-daemon
  Version: 3.36.1-0ubuntu1

  I see the following in my syslog when this happens:

  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.139' (uid=1001 pid=1888 
comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Starting 
Fingerprint Authentication Daemon...
  May 27 14:06:35 admin2-ThinkPad-X1-Carbon-7th kernel: [79025.239325] usb 1-9: 
reset full-speed USB device number 5 using xhci_hcd
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[936]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th systemd[1]: Started Fingerprint 
Authentication Daemon.
  May 27 14:06:36 admin2-ThinkPad-X1-Carbon-7th gnome-shell[1888]: 
clutter_input_focus_set_cursor_location: assertion 
'clutter_input_focus_is_focused (focus)' failed
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th NetworkManager[938]:   
[1590584801.7453] agent-manager: 
agent[6ebc664fc14fe9de,:1.139/org.gnome.Shell.NetworkAgent/1001]: agent 
registered
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.freedesktop.FileManager1' 
requested by ':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " 
label="unconfined")
  May 27 14:06:41 admin2-ThinkPad-X1-Carbon-7th dbus-daemon[1763]: [session 
uid=1001 pid=1763] Activating service name='org.gnome.Nautilus' requested by 
':1.32' (uid=1001 pid=1888 comm="/usr/bin/gnome-shell " label="unconfined")
  May 27 14:07

[Desktop-packages] [Bug 1882481] [NEW] A dialog box stays on desktop and does not go away

You have been subscribed to a public bug:

Upon rebooting, I get dialog box

Authentication Required

Authentication is required to start 'cups.service'.

I can type in the password and click Authenticate, but then nothing
happens. I can't see under the box. I can't move the box, can't cancel
the dialog.

But, I can click on where I know the underneath icon to be and that
click is accepted and the program in question runs. It appears the
display manager does not remove the image after it is done with the
dialog.


I have recently done a clean install of 20.04.


There is a screenshot in this Stack Exchange post:
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 23:10:43 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
 amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92]
InstallationDate: Installed on 2020-05-12 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0804
dmi.board.asset.tag: Default string
dmi.board.name: ROG ZENITH EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu
-- 
A dialog box stays on desktop and does not go away
https://bugs.launchpad.net/bugs/1882481
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1882481] Re: A dialog box stays on desktop and does not go away

2020-06-07 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1882481

Title:
  A dialog box stays on desktop and does not go away

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon rebooting, I get dialog box

  Authentication Required

  Authentication is required to start 'cups.service'.

  I can type in the password and click Authenticate, but then nothing
  happens. I can't see under the box. I can't move the box, can't cancel
  the dialog.

  But, I can click on where I know the underneath icon to be and that
  click is accepted and the program in question runs. It appears the
  display manager does not remove the image after it is done with the
  dialog.


  I have recently done a clean install of 20.04.

  
  There is a screenshot in this Stack Exchange post:
  
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 23:10:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
   amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 
[1462:8a92]
  InstallationDate: Installed on 2020-05-12 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0804
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882481/+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 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

I suggest using 'Ubuntu on Wayland' as a workaround. You can fix the
"too small" problem by running:

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
framebuffer','x11-randr-fractional-scaling']"

and then log into 'Ubuntu on Wayland' again. You should now have
fractional scaling options and without this bug.


** Tags added: multimonitor

** Changed in: mutter (Ubuntu)
   Status: Incomplete => New

-- 
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/1882212

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference

  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON

  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON

  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
  Expected behavior: Pointer doesn't blink
  Current behavior: Pointer blinks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+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 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it

2020-06-07 Thread Jerry Quinn

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1881669

Title:
  Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been
  already finalized. Impossible to set any property to it

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  jlquinn@cerberus:~/Videos$ apt-cache policy  
gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
Installed: 18.04.1
Candidate: 18.04.1
Version table:
   *** 18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  This may be related to bug 1879016, but my stack trace is smaller and 
different.  I enabled the appindicator extension, and see the following my logs:

  Jun 01 17:24:15 cerberus gnome-shell[3318]: Object 
.Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. 
Impossible to set any property to it.
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for 
context 0x5582a28894b0 ==
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718eda00 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5a930 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7f6ee00
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718ee5e0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718eed80 b   
self-hosted:916 (0x7f70f00f12b8 @ 367)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718eee70 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190
 (0x7f6ee00adf78 
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718efac0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5a800 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:176
 (0x7f6e
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718f06a0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5a760 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:170
 (0x7f6e
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #10 0x7ffc718f1290 I  
 resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71)
  Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #11 0x7ffc718f1a50 b  
 self-hosted:918 (0x7f70f00f12b8 @ 394)
  Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While 
reading menu layout: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.
  Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy 
is null
  
DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9
  
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-appindicator 18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  1 17:41:57 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-05-29 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1881669/+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 1882481] Re: A dialog box stays on desktop and does not go away

This sounds like bug 1824874. To help us check that please:

1. Provide a screenshot or photo of the problem; and

2. After the dialog has appeared run:

   journalctl -b0 > journal.txt

   or if you had to reboot then run:

   journalctl -b-1 > prevboot.txt

   and attach the resulting text file here.


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882481

Title:
  A dialog box stays on desktop and does not go away

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon rebooting, I get dialog box

  Authentication Required

  Authentication is required to start 'cups.service'.

  I can type in the password and click Authenticate, but then nothing
  happens. I can't see under the box. I can't move the box, can't cancel
  the dialog.

  But, I can click on where I know the underneath icon to be and that
  click is accepted and the program in question runs. It appears the
  display manager does not remove the image after it is done with the
  dialog.


  I have recently done a clean install of 20.04.

  
  There is a screenshot in this Stack Exchange post:
  
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 23:10:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
   amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 
[1462:8a92]
  InstallationDate: Installed on 2020-05-12 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0804
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882481/+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 1871536] Re: "Ubuntu Software" icon absent from dash after installing 20.04 beta

[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1871536

Title:
  "Ubuntu Software" icon absent from dash after installing 20.04 beta

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Ubuntu: 20.04 (beta image)

  Summary
  ===

  After a fresh install, the "Ubuntu Software" icon is absent from the
  dash. To find it, user has to click "Show Applications" at the bottom
  left and search for "Ubuntu Software".

  Steps to reproduce
  ==

  1. Install 20.04 beta (in my case, because of lp:1871268, I did the 
installation without being connected to the Internet)
  2. When the first use panel is shown (asking if you want Live Update, send 
the anonymized info to Canonical, etc.), when the screen about softwares is 
shown, don't click "Open".

  Expected results
  

  At the end of the installation, "Ubuntu Software" is among the icons
  available in the dash.

  Actual results
  ==

  No "Ubuntu Software" icon in the dash.

  My guess is that since the "snap store" snap is now being used instead
  of the gnome-software Debian package, something is missing to add the
  icon to the dash by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 01:43:15 2020
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871536/+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 1871385] Re: gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string()

[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1871385

Title:
  gnome-control-center crashed with SIGSEGV in
  _cogl_gpu_info_parse_version_string()

Status in gnome-control-center package in Ubuntu:
  Expired

Bug description:
  i need help

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr  7 14:53:42 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200405)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>:   
movsbq 0x0(%r13),%rax
   PC (0x7f57bb0eb1ea) ok
   source "0x0(%r13)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, 
group=, loc=0x7f57bb289960 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
   ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871385/+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 1881687] Re: Desktop is blank after logging in without a monitor attached

2020-06-07 Thread Scoot Lee

Thanks.  Here is the issue in the gnome-shell tracker:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2883
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883

-- 
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/1881687

Title:
  Desktop is blank after logging in without a monitor attached

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04, I have an AMD system with an integrated GPU (Ryzen 3 3200G 
with Radeon Vega 8)
  I am using lightdm instead of gdm3. My GPU is using the amdgpu driver. I have 
no specific xorg.conf in place.  I am using x11vnc to login and view the 
desktop remotely.  There is no monitor attached.

  After logging into lightdm's greeter, I am presented with a blank
  desktop with the Focal Fossa background image and a mouse cursor, but
  no other visible interface or windows.  There is no menu bar at the
  top of the desktop and no application bar on the left.

  This all works perfectly fine if a monitor is attached before lightdm
  (and thus Xorg) is started.

  If I change the settings at login to use fvwm for my session it works
  fine.  This is also the case for Gnome Flashback mode (using
  metacity).  But the default of gnome-shell/mutter does not work
  without the monitor.  Nor does using Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 31 13:34:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.6.0+dfsg, 5.4.0-31-generic, x86_64: installed
   evdi, 1.6.0+dfsg, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
  InstallationDate: Installed on 2020-05-21 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=0030bb65-9e5e-4a70-bba3-da14892ec5b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881687/+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 1882490] [NEW] gsd-media-keys unable to get default source or sink

2020-06-07 Thread Jerry Quinn

Public bug reported:

jlquinn@cerberus:~$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
jlquinn@cerberus:~$ apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
  Installed: 3.28.1-0ubuntu1.3
  Candidate: 3.28.1-0ubuntu1.3
  Version table:
 *** 3.28.1-0ubuntu1.3 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.28.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

In my log, I see the following messages:

Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default sink
Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default source

This seems like something is amiss.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1.3
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  8 01:03:33 2020
InstallationDate: Installed on 2020-05-29 (9 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1882490

Title:
  gsd-media-keys unable to get default source or sink

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  jlquinn@cerberus:~$ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.28.1-0ubuntu1.3
Candidate: 3.28.1-0ubuntu1.3
Version table:
   *** 3.28.1-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  In my log, I see the following messages:

  Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default sink
  Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default source

  This seems like something is amiss.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  8 01:03:33 2020
  InstallationDate: Installed on 2020-05-29 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1882490/+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 1882491] Re: /usr/bin/gnome-control-center:11:GI___strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_

*** This bug is a duplicate of bug 1871385 ***
https://bugs.launchpad.net/bugs/1871385

** This bug has been marked a duplicate of bug 1871385
   gnome-control-center crashed with SIGSEGV in 
_cogl_gpu_info_parse_version_string()

-- 
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/1882491

Title:
  /usr/bin/gnome-control-
  
center:11:__GI_strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.36.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882491/+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 1882491] [NEW] /usr/bin/gnome-control-center:11:GI___strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_updat

2020-06-07 Thread errors.ubuntu.com bug bridge

*** This bug is a duplicate of bug 1871385 ***
https://bugs.launchpad.net/bugs/1871385

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.36.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic cosmic disco eoan focal groovy xenial zesty

-- 
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/1882491

Title:
  /usr/bin/gnome-control-
  
center:11:__GI_strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.36.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882491/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-07 Thread Pandu Rakimanputra

I also experience this issue with 2 different Brand of Bluetooth Headset:
ATH-CRK75BTH
Edifier W200BT

Problem also appears every time I switch bluetooh devices as INPUT
device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar
doesn't move and test OUTPUT doesn't produce any sound. When I tried
video conferencing with my friend, he couldn't hear my voice and of
course I can't hear him either.

This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other
Linux distro in this laptop). A2DP mode works normal. Currently I'm
using internal laptop microphone and A2DP combination for video
conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were
updated. But still not work for HSP/HFP mode output and Bluetooth mic
input.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1881687] Re: Desktop is blank after logging in without a monitor attached

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

-- 
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/1881687

Title:
  Desktop is blank after logging in without a monitor attached

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 20.04, I have an AMD system with an integrated GPU (Ryzen 3 3200G 
with Radeon Vega 8)
  I am using lightdm instead of gdm3. My GPU is using the amdgpu driver. I have 
no specific xorg.conf in place.  I am using x11vnc to login and view the 
desktop remotely.  There is no monitor attached.

  After logging into lightdm's greeter, I am presented with a blank
  desktop with the Focal Fossa background image and a mouse cursor, but
  no other visible interface or windows.  There is no menu bar at the
  top of the desktop and no application bar on the left.

  This all works perfectly fine if a monitor is attached before lightdm
  (and thus Xorg) is started.

  If I change the settings at login to use fvwm for my session it works
  fine.  This is also the case for Gnome Flashback mode (using
  metacity).  But the default of gnome-shell/mutter does not work
  without the monitor.  Nor does using Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 31 13:34:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.6.0+dfsg, 5.4.0-31-generic, x86_64: installed
   evdi, 1.6.0+dfsg, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
  InstallationDate: Installed on 2020-05-21 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=0030bb65-9e5e-4a70-bba3-da14892ec5b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1881687/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-07 Thread Pandu Rakimanputra

I also experience this issue with 2 different Brand of Bluetooth Headset:
ATH-CRK75BTH
Edifier W200BT

Problem also appears every time I switch bluetooh devices as INPUT
device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar
doesn't move and test OUTPUT doesn't produce any sound. When I tried
video conferencing with my friend, he couldn't hear my voice and of
course I can't hear him either.

This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other
Linux distro in this laptop). A2DP mode works normal. Currently I'm
using internal laptop microphone and A2DP combination for video
conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were
updated. But still not work for HSP/HFP mode output and Bluetooth mic
input.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1871385] Re: gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string()

Actually it looks like a common issue:

https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e

** Description changed:

+ https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e
+ 
+ ---
+ 
  i need help
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr  7 14:53:42 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200405)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
-  LANGUAGE=fr_FR
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=fr_FR
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>:   
movsbq 0x0(%r13),%rax
-  PC (0x7f57bb0eb1ea) ok
-  source "0x0(%r13)" (0x) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>:   
movsbq 0x0(%r13),%rax
+  PC (0x7f57bb0eb1ea) ok
+  source "0x0(%r13)" (0x) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
-  __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, 
group=, loc=0x7f57bb289960 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, 
group=, loc=0x7f57bb289960 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Changed in: gnome-control-center (Ubuntu)
   Status: Expired => Confirmed

** Summary changed:

- gnome-control-center crashed with SIGSEGV in 
_cogl_gpu_info_parse_version_string()
+ gnome-control-center crashed with SIGSEGV in strtoul() from 
_cogl_gpu_info_parse_version_string()

** Summary changed:

- gnome-control-center crashed with SIGSEGV in strtoul() from 
_cogl_gpu_info_parse_version_string()
+ gnome-control-center crashed with SIGSEGV in __GI_strtoul_l_internal() 
from _cogl_gpu_info_parse_version_string()

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1019
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-control-center (Ubuntu)
   Importance: Low => Medium

** Tags added: bionic groovy xenial

-- 
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/1871385

Title:
  gnome-control-center crashed with SIGSEGV in
  __GI_strtoul_l_internal() from
  _cogl_gpu_info_parse_version_string()

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e

  ---

  i need help

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr  7 14:53:42 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200405)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>:   
movsbq 0x0(%r13),%rax
   PC (0x7f57bb0eb1ea) ok
   source "0x0(%r13)" (0x) not located in a known VMA region (needed 
readable r

[Desktop-packages] [Bug 1882231] Re: Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash"

** Summary changed:

-  Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish Bin 
..." 
+ Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty 
Trash"

** Summary changed:

- Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty 
Trash"
+ Context menu for Rubbish Bin desktop icon displays "Empty Wastebasket" or 
"Empty Trash"

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => Low

** Bug watch added: 
gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #208
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/208

** Also affects: gnome-shell-extension-desktop-icons via
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/208
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1882231

Title:
  Context menu for Rubbish Bin desktop icon displays "Empty Wastebasket"
  or "Empty Trash"

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
   Tooltip for Rubbish Bin displays "Wastebasket ..." instead of
  "Rubbish Bin ..."

  This bug is in the Ubuntu desktop 20.04 LTS. Same issue reported
  before in 2016 release as above

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1882231/+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 1882354] Re: [Intel T4200] all application open in black

Can you please attach a screenshot or photo of the problem?

** Summary changed:

- graphics card
+ [Intel T4200] all application open in black

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

-- 
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/1882354

Title:
  [Intel T4200] all application open in black

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  all application open in black

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 18:13:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
  InstallationDate: Installed on 2020-06-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R468/R418
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=c84a78a6-96a8-49ab-9350-c471429971dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04NG.MP01.20090728.HCW
  dmi.board.name: R468/R418
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04NG.MP01.20090728.HCW:bd07/28/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR468/R418:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR468/R418:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R468/R418
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882354/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-06-07 Thread Rex Tsai

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :

[Desktop-packages] [Bug 1882368] Re: Sound is louder after resume from suspend or logging in Ubuntu 20.04

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1882368

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882368

Title:
  Sound is louder after resume from suspend or logging in Ubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 20.04 and have noticed that after logging back on
  to a machine either after its been asleep/suspended or logged out due
  to inactivity the sound is much louder at the same volume. I haven't
  enabled amplification or any other sound feature.

  To duplicate, boot machine with volume at say 50% and listen to some
  music. Let it either log out or suspend/sleep and then log back in,
  start music/sound and it will be much louder.

  In fact this louder sound at the volume sounds correct, because the
  windows boot sounds the same at that level. When ubuntu boots the
  volume is much softer. The sound post logging in after a suspend or
  lock out is what it should be from the get go.

  Soundcard details
  00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
DeviceName: Onboard - Sound
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Flags: bus master, fast devsel, latency 32, IRQ 143
Memory at a351 (64-bit, non-prefetchable) [size=16K]
Memory at a310 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882361] Re: Dead/frozen mouse pointer after login

*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052

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 1873052, 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 1873052
   GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps 
another not scaled cursor mid 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/1882361

Title:
  Dead/frozen mouse pointer after login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  A dead/frozen copy of the mouse pointer remains on the screen, after
  login.  This issue has been previously reported by other users.  The
  dead mouse pointer goes away if you switch the the Scale on Display
  Settings to any alternative and then back to your desired scale.
  Using an AMD Ryzen processor with a Radeon Vega graphics chip and
  default Gnome desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 06:41:46 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-10 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  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/1882361/+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 1881482] Re: adding fingerprints not possible

2020-06-07 Thread frank

i had defined 1 fingerprint and want to add more...

attached screenshot of settings-dialog and the question dialog (where i
asked for deleting existing fingerprints).

i klick on (1) and get the dialog where i press cancel (2),because i
don't want to delete existing fingerprint. dialog gets closed and not
showing the dialog for adding fingerprints.

** Attachment added: "dialog where i try to add fingerprints includung dialog 
asking for deleting them"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881482/+attachment/5381517/+files/Screenshot%20from%202020-06-08%2008-21-29_.png

-- 
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/1881482

Title:
  adding fingerprints not possible

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  hi,

  after getting my fingerprint-reader working, i wonder why i can only
  define 1 fungerprint in gnome-settings dialog
  (system->users->fingerprint login add finger).

  i have defined one, fingerprint-usage is activated, if i click on the
  setting i will be asked about deleting the fingerprints to disable.
  here i can delete or cancel...as i do not want to delete i click
  cancel and expect the dialog for adding additional fingers...but this
  does not happen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun May 31 16:20:32 2020
  InstallationDate: Installed on 2020-04-27 (34 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881482/+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 1882399] Re: Window placements

Modal dialogs are meant to move the parent window. If you want to turn
that feature off then install 'gnome-tweaks' and set:

  Tweaks > Windows > Attach Modal Dialogs = OFF

If you have any other issues then please report them in separate bugs by
running:

  ubuntu-bug gnome-shell

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

-- 
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/1882399

Title:
  Window placements

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When moving a chrome pop-up window (file selection for upload), moving
  this window moves the original window.

  Also: the new window don't launch to the last closed position as they
  used to in 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882399/+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 1882415] Re: artifact in top-right corner