date:20200407

The issue is on my workstation which might have all kind of config history.
On a fresh focal system it looks like "default off, start works"

root@f:~# systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
 Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor 
preset: enabled)
 Active: inactive (dead)

root@f:~# systemctl start rtkit-daemon.service
root@f:~# systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
 Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2020-04-08 06:12:27 UTC; 1s ago
   Main PID: 76699 (rtkit-daemon)
  Tasks: 3 (limit: 38284)
 Memory: 684.0K
 CGroup: /system.slice/rtkit-daemon.service
 └─76699 /usr/libexec/rtkit-daemon

Apr 08 06:12:27 f systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 08 06:12:27 f systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully called chroot.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully dropped privileges.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully limited resources.
Apr 08 06:12:27 f rtkit-daemon[76699]: Running.
Apr 08 06:12:27 f rtkit-daemon[76699]: Canary thread running.
Apr 08 06:12:27 f rtkit-daemon[76699]: Watchdog thread running.

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  New

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

Start through dbus fails the same way.
$ rtkitctl --start

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  New

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

Reproducible:
$ sudo /usr/libexec/rtkit-daemon --stderr
rtkit-daemon[1764664]: Successfully called chroot.
rtkit-daemon[1764664]: Successfully dropped privileges.
rtkit-daemon[1764664]: Successfully limited resources.
rtkit-daemon[1764664]: pthread_create failed: Resource temporarily unavailable
rtkit-daemon[1764664]: Canary thread running.
rtkit-daemon[1764664]: Exiting canary thread.
rtkit-daemon[1764664]: Demoting known real-time threads.
rtkit-daemon[1764664]: Demoted 0 threads.

It seems I can "fix" it by adding: --no-drop-privileges

So does it drop more privs on my system than on those where it works?

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  New

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1871543] [NEW] rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

Public bug reported:

I was debugging something else and found rtkit broken on my system.

Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called chroot.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

That state is reproducible through restarts.
I haven't looked any further yet.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rtkit 0.12-4
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 07:59:58 2020
InstallationDate: Installed on 2018-10-12 (543 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: rtkit
UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

** Affects: rtkit (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 rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1871543

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  New

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice

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

Most likely this was bug 1843982. So let's use that for now.

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

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

Title:
  Gnome Shell crashed on background upgrade of accountsservice

Status in accountsservice package in Ubuntu:
  New
Status in dbus package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: sw

[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-07 Thread Mathew Hodson

** Changed in: pulseaudio (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: pulseaudio (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869750] Re: [nvidia] Screens turn off when setting display scaling to 200%

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

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

Title:
  [nvidia] Screens turn off when setting display scaling to 200%

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Issue: When setting display scaling to 200% in GNOME settings with
  proprietary nvidia drivers installed displays go to sleep until
  settings automatically revert to previous settings.

  Steps to reproduce:

  - Install proprietary nvidia drivers

  - Open GNOME settings

  - Navigate to Display settings

  - Set display scaling to 200%

  
  NOTE: This issue has been solved in upstream mutter git master branch. 
Confirmed on both Arch and Fedora packages that have been created from mutter 
master branch.

  GPU: GeForce GTX 1080 Ti
  Driver: 440.64

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 11:01:56 2020
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1869750/+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 1870929] Re: [nvidia] Display Scaling causes monitors to sleep

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

** This bug is no longer a duplicate of bug 1870758
   [nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
   [nvidia] Screens turn off when setting display scaling to 200%

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

Title:
  [nvidia] Display Scaling causes monitors to sleep

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  Default install  of Focal Fossa 20.04 Beta downloaded April 4, 2020.

  Steps to Reproduce:
  1. Open Settings
  2. Navigate to Displays.
  3. In Scale section, select `200%`
  4. Click Apply
  Expected behavior: Screens refresh with a 200% scale applied and a dialog to 
confirm.
  Error encountered: Screens switch to "power saving mode" (go blank).  After 
about 15 seconds, they wake up in the original 100% scale mode.

  Other notes:
  I have done this successfully with 18.04 on the exact same hardware 
(different hard drive partitions) in the past after installing NVidia drivers.
  I have successfully rearranged the monitors in Settings and changed the 
Primary Display in Settings with this install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 10:09:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-21-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2070 Rev. A] [3842:2173]
  InstallationDate: Installed on 2020-04-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B17
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a4cb80c1-f367-4150-afd3-31e3ee90bd50 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PRO CARBON (MS-7B17)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd03/25/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B17:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPROCARBON(MS-7B17):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B17
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870929/+subscriptions

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

[Desktop-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)

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

Excellent news: This appears to be a duplicate of bug 1869750.

** This bug has been marked a duplicate of bug 1869750
   [nvidia] Screens turn off when setting display scaling to 200%

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

Title:
  [nvidia] Display scaling results in a blank screen (power save state)

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  Working on fully updated focal fossy

  Procedure to make bug happen:

  1. open gnome control center and select screen (skærme in danish)

  2. click the "fractional scaling" switch

  3. select 150% scaling and click the green button at top right

  4. Result is a blank screen and the monitor going into a power save
  state

  
  A reboot doesn't help. The login screen appears, when I log in the screen 
goes blank again and the monitor power save kicks in.

  If I select the "unity" environment, the display does work.

  If I do this on the command line "gsettings set org.gnome.mutter
  experimental-features ['']", I can log in as usual and fractional
  scaling has been turned off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu3
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 12:11:39 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

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

** This bug is no longer a duplicate of bug 1870758
   [nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
   [nvidia] Screens turn off when setting display scaling to 200%

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870922] Re: [nvidia] GUI Scaling does not work with multiple monitors

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

** This bug is no longer a duplicate of bug 1870758
   [nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
   [nvidia] Screens turn off when setting display scaling to 200%

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

Title:
  [nvidia] GUI Scaling does not work with multiple monitors

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  When changing the GUI scaling factor on a multiple monitor setup the
  monitors all just go blank and then revert to the previous values.

  Changing the scaling factor manually in the config file does not work
  either, it causes all monitors to go blank as well.

  I observed that it is trying to set a mode "null", here is the line from the 
Xorg log:
  `NVIDIA(0): Setting mode "NULL"`

  I have initially noticed this after upgrading from Ubuntu 19.10 to
  20.04 and my screens would all be just blank after the system has
  booted up. I had to delete the monitor configuration files manually
  via SSH to get a screen output in xorg again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.2-050602-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..2a.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:2a: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 15:00:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-45-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   nvidia, 440.64, 5.6.2-050602-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [TITAN Xp] [10de:1b02] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GP102 [TITAN Xp] [10de:123e]
  InstallationDate: Installed on 2018-09-06 (576 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.2-050602-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.78
  dmi.board.name: X570 Phantom Gaming-ITX/TB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..2a.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:2a: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 0

[Desktop-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)

2020-04-07 Thread Erik Steiner

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

Scaling to 200% is fine until I decide to use nvidia-driver, instead of
X.Org-X-Server.

Some reported that the monitor would go to power save state when they
applied the scaling setting immediately. I can not confirm that. Scaling
with nvidia-driver works until I reboot.

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

Title:
  [nvidia] Display scaling results in a blank screen (power save state)

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  Working on fully updated focal fossy

  Procedure to make bug happen:

  1. open gnome control center and select screen (skærme in danish)

  2. click the "fractional scaling" switch

  3. select 150% scaling and click the green button at top right

  4. Result is a blank screen and the monitor going into a power save
  state

  
  A reboot doesn't help. The login screen appears, when I log in the screen 
goes blank again and the monitor power save kicks in.

  If I select the "unity" environment, the display does work.

  If I do this on the command line "gsettings set org.gnome.mutter
  experimental-features ['']", I can log in as usual and fractional
  scaling has been turned off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu3
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 12:11:39 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+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 1871458] Re: No display signal if NVIDIA driver and display scaling is active

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

** This bug is no longer a duplicate of bug 1870758
   [nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
   [nvidia] Screens turn off when setting display scaling to 200%

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

Title:
  No display signal if NVIDIA driver and display scaling is active

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 20.04 (20200402) with LVM encryption and 
automatic logon.
  So I enter my encryption password and after the motherboards boot logo it 
will login automatically to desktop. I also chose the additional drivers and so 
nvidia-driver-440.
  Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in 
settings. Next reboot, I enter my encryption password. When the automatic logon 
process should happen, the monitor turns off and says that no display signal is 
available.

  Currently I was able to return to a working setup by pressing CTRL + ALT + 
F4, login and enter the following commands to remove nvidia-driver and use XORG 
instead:
  sudo apt purge nvidia-driver-440
  sudo apt autoremove
  sudo reboot

  I am pretty sure that the issue will occur again, if I choose NVIDIA
  driver again.

  Any thoughts?

  EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the
  monitor was not turned on, the monitor reported no signal available
  after turning it on. I was not able to see the boot-up field to enter
  my encryption password. Unfortunately I didn't test, if I were able to
  enter my password and logon anyway. Workaround was to turn the monitor
  on, before starting the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 19:31:50 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] 
[1458:3762]
  InstallationDate: Installed on 2020-04-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd04/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871458/+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 1869653] Re: Sync scowl 2019.10.06-1 (main) from Debian unstable (main)

2020-04-07 Thread Mathew Hodson

** Changed in: scowl (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync scowl 2019.10.06-1 (main) from Debian unstable (main)

Status in scowl package in Ubuntu:
  New

Bug description:
  Please sync scowl 2019.10.06-1 (main) from Debian unstable (main)

  This version adds various new words to the English dictionaries, and
  fixes bugs. It has not been updated since April 2018.

  Changelog entries since current focal version 2018.04.16-1:

  scowl (2019.10.06-1) unstable; urgency=medium

    * New upstream release (Closes: #952736)
    * Deprecate reprized for reprised (Closes: #952653)
    * Use up to 70 wordlists for hunspell (Closes: #933544)
    * Distribute all scowl files as utf-8 (Closes: #775480)

   -- Don Armstrong   Sat, 29 Feb 2020 20:07:46 -0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/1869653/+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 1871538] [NEW] Gnome Shell crashed on background upgrade of accountsservice

Public bug reported:

This morning I found my computer on the login screen.
But not the one of the screen log, no a new one - so something must have 
crashed.

Logging in again confirmed that all apps were gone and the gnome shell
was brought down what seems like triggered by a background update o
accountsservice.

As always things are not perfectly clear :-/
The following goes *back* in time through my logs one by one.

Multiple apps crashed at 06:09, but we will find later that this is a follow on 
issue of the underlying gnome/X/... recycling.
-rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
-rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash


rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling 
Policy Service.
Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53


But that already was only triggered by a gnome restart that kicked of earlier:

Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is 
initialized.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).


X was recycleing before:
Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
...
Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.


It seems like some internal service broke and everything that followed was a 
secondary issue to that:
Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected 
error response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group 
on interface vnet0.IPv6 with address fe80::fc54:ff:fe78:26c2.
Apr 08 06:09:19 Keschdeichel systemd[1]: accounts-daemon.service: Unexpected 
error response from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group 
on interface strswanbr2.IPv4 with address 192.168.2.0.
Apr 08 06:09:19 Keschdeichel systemd[1]: gdm.service: Unexpected error response 
from GetNameOwner(): Connection terminated
Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group 
on interface virbr0.IPv4 with address 192.168.122.1.
Apr 08 06:09:19 Keschdeichel sy

[Desktop-packages] [Bug 1871536] [NEW] "Ubuntu Software" icon absent from dash after installing 20.04 beta

2020-04-07 Thread Pierre Equoy

Public bug reported:

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)

** Affects: gnome-software (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-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:
  New

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 1871534] Re: Ubuntu dock causes Gnome shell to crash

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-extension-ubuntu-dock (Ubuntu)
Status: New => Incomplete

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

Title:
Ubuntu dock causes Gnome shell to crash

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete

Bug description:
Ubuntu dock is causing the gnome shell to crash especially while
opening appfolders and clicking out of the app folders. Same problem
was also observed during minimizing and maximizing (by clicking the
launcher button).

The entire gnome shell was frozen; none of the key bindings worked -
except the only option was to switch to the tty by hitting alt-ctrl-f3
and restart from there.

I have played around with all the options in the settings by installing dash
to dock extension (since some settings seems to be shared) including
transparency, Auto hide, panel & icon size with all kinds of combinations and I
managed to fix this issue by disabling / unchecking the option:
Panel mode:extend to screen edge.

After disabling/Unchecking the option- Panel mode:extend to screen
edge; this problem could not be replicated again.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
Codename: focal

apt-cache policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
Installed: 67ubuntu20.04.3
Candidate: 67ubuntu20.04.3
Version table:
*** 67ubuntu20.04.3 500
500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://in.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 8 09:56:27 2020
InstallationDate: Installed on 2020-04-02 (5 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_IN
SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
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-ubuntu-dock/+bug/1871534/+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 1871534] [NEW] Ubuntu dock causes Gnome shell to crash

2020-04-07 Thread Bhaskar Chatterjee

Public bug reported:

Ubuntu dock is causing the gnome shell to crash especially while opening
appfolders and clicking out of the app folders. Same problem was also
observed during minimizing and maximizing (by clicking the launcher
button).

The entire gnome shell was frozen; none of the key bindings worked -
except the only option was to switch to the tty by hitting alt-ctrl-f3
and restart from there.

I have played around with all the options in the settings by installing dash to 
dock extension (since some settings seems to be shared) including transparency, 
Auto hide, panel & icon size with all kinds of combinations and I managed to 
fix this issue by disabling / unchecking the option:
Panel mode:extend to screen edge.

After disabling/Unchecking the option- Panel mode:extend to screen edge;
this problem could not be replicated again.


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Codename:   focal


apt-cache policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
  Installed: 67ubuntu20.04.3
  Candidate: 67ubuntu20.04.3
  Version table:
 *** 67ubuntu20.04.3 500
500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://in.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 09:56:27 2020
InstallationDate: Installed on 2020-04-02 (5 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Ubuntu dock causes Gnome shell to crash

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Ubuntu dock is causing the gnome shell to crash especially while
  opening appfolders and clicking out of the app folders. Same problem
  was also observed during minimizing and maximizing (by clicking the
  launcher button).

  The entire gnome shell was frozen; none of the key bindings worked -
  except the only option was to switch to the tty by hitting alt-ctrl-f3
  and restart from there.

  I have played around with all the options in the settings by installing dash 
to dock extension (since some settings seems to be shared) including 
transparency, Auto hide, panel & icon size with all kinds of combinations and I 
managed to fix this issue by disabling / unchecking the option:
  Panel mode:extend to screen edge.

  After disabling/Unchecking the option- Panel mode:extend to screen
  edge; this problem could not be replicated again.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  
  apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 67ubuntu20.04.3
Candidate: 67ubuntu20.04.3
Version table:
   *** 67ubuntu20.04.3 500
  500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 09:56:27 2020
  InstallationDate: Installed on 2020-04-02 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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-ubuntu-dock/+bug/1871534/+subscriptions

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

[Desktop-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

2020-04-07 Thread Robert Ancell

Confirmed fixed in Bionic with json-glib 1.4.2-3ubuntu0.18.04.1


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1871281] Re: Latest snap channel not showing

2020-04-07 Thread Robert Ancell

** Also affects: gnome-software (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: gnome-software (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: gnome-software (Ubuntu Eoan)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Latest snap channel not showing

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  In Progress
Status in gnome-software source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Due to a code change for channel names in snapd gnome-software in bionic 
doesn't show versions in the 'latest/*' channels. Solution is to backport 
changes that always use the full name for channels to avoid this problem. 
Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9

  [Test Case]
  1. Open GNOME Software
  2. Search for the 'postman' snap

  Expected result:
  latest/stable channel shown with version like 7.21.1

  Observed result:
  No version shown in for latest/* channels.

  [Regression potential]
  Risk of introducing new bugs in relation to channels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

2020-04-07 Thread Robert Ancell

Confirmed fixed in Eoan with json-glib 1.4.4-2ubuntu0.19.10.1

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)

** Summary changed:

- [nvidia] Display scaling results in monitor power save state
+ [nvidia] Display scaling results in a blank screen (power save state)

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

Title:
  [nvidia] Display scaling results in a blank screen (power save state)

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  Working on fully updated focal fossy

  Procedure to make bug happen:

  1. open gnome control center and select screen (skærme in danish)

  2. click the "fractional scaling" switch

  3. select 150% scaling and click the green button at top right

  4. Result is a blank screen and the monitor going into a power save
  state

  
  A reboot doesn't help. The login screen appears, when I log in the screen 
goes blank again and the monitor power save kicks in.

  If I select the "unity" environment, the display does work.

  If I do this on the command line "gsettings set org.gnome.mutter
  experimental-features ['']", I can log in as usual and fractional
  scaling has been turned off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu3
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 12:11:39 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+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 1871394] Re: modeset: Loss of VGA signal (ast2500) on login

The attached Xorg log files seem to show that it knows about both GPUs
and it claims to be using both...

1. Are you able to work around the problem by logging into "Ubuntu on
Wayland" instead?

2. Does the same problem also occur in Ubuntu 20.04 (to be released
soon)? http://cdimage.ubuntu.com/daily-live/current/ or in 19.10
(https://ubuntu.com/download/desktop)?

** Summary changed:

- no dual head video with 2 on board sources: ast2500 and i915
+ modeset: Loss of VGA signal (ast2500) on login

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

** 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/1871394

Title:
  modeset: Loss of VGA signal (ast2500) on login

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am creating a new computer platforms.  It provides two video
  sources: an Intel i915 DisplayPort and an AST2500 VGA.  The i915 also
  provides HDMI, but it is disconnected/disabled.

  EXPECTED BEHAVIOR: Video is presented through the AST2500 to VGA and
  the i915 to DisplayPort, mergine the displays to a unified layout when
  a layout is provided to xorg.

  ACTUAL BEHAVIOR: Both monitors present a purple background at login,
  but the VGA monitor is quickly disabled at login.

  When I had a problem with these video sources under Windows the Intel
  team provided me a "Switchable Graphics" BIOS module.  It resolved the
  issue there.  My BIOS settings define "Switchable Graphics" as the
  Primary Display.

  When I set the BIOS to use the ast2500 as the only display source the
  system works as intended.  I mention this to confirm the ast2500 and
  kernel can display video even if the ast2500 won't display video
  alongside the i915.

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  test@test:~$ modinfo ast | grep -version
  filename:   
/lib/modules/5.3.0-46-generic/kernel/drivers/gpu/drm/ast/ast.ko
  license:GPL and additional rights
  description:AST
  author: Dave Airlie
  firmware:   ast_dp501_fw.bin
  alias:  pci:v1A03d2010sv*sd*bc03sc*i*
  alias:  pci:v1A03d2000sv*sd*bc03sc*i*
  depends:drm,drm_kms_helper,drm_vram_helper,i2c-algo-bit
  retpoline:  Y
  intree: Y
  name:   ast
  vermagic:   5.3.0-46-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   modeset:Disable/Enable modesetting (int)

  test@test:~$ xrandr --listproviders
  Providers: number : 2
  Provider 0: id: 0x6e cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 
2 associated providers: 0 name:modesetting
  Provider 1: id: 0x41 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 
name:modesetting

  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
  DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 496mm x 292mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x800  59.81  
 1280x720  60.00  
 1024x768  60.00  
 800x600   60.32  
 640x480   59.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  test@test:~$ sudo lshw -C video
  [sudo] password for test: 
*-display 
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:152 memory:9000-90ff memory:8000-8fff 
ioport:6000(size=64) memory:c-d
*-display
 description: VGA compatible controller
 product: ASPEED Graphics Family
 vendor: ASPEED Technology, Inc.
 physical id: 0
 bus info: pci@:04:00.0
 version: 41
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi vga_controller cap_list
 configuration: driver=ast latency=0
 resources: irq:18 memory:9100-91ff memory

[Desktop-packages] [Bug 1870758] Re: [nvidia] Display scaling results in monitor power save state

2020-04-07 Thread Tim Penhey

** Tags added: champagne

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

Title:
  [nvidia] Display scaling results in a blank screen (power save state)

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  Working on fully updated focal fossy

  Procedure to make bug happen:

  1. open gnome control center and select screen (skærme in danish)

  2. click the "fractional scaling" switch

  3. select 150% scaling and click the green button at top right

  4. Result is a blank screen and the monitor going into a power save
  state

  
  A reboot doesn't help. The login screen appears, when I log in the screen 
goes blank again and the monitor power save kicks in.

  If I select the "unity" environment, the display does work.

  If I do this on the command line "gsettings set org.gnome.mutter
  experimental-features ['']", I can log in as usual and fractional
  scaling has been turned off.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu3
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 12:11:39 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

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

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

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

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

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

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

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 1870758, 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 1870758
   [nvidia] Display scaling results in monitor power save state

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1871414] Missing required logs.

2020-04-07 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1871414

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (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/1871414

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting po

[Desktop-packages] [Bug 1871458] Re: No display signal if NVIDIA driver and display scaling is active

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

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 1870758, 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 1870758
   [nvidia] Display scaling results in monitor power save state

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

Title:
  No display signal if NVIDIA driver and display scaling is active

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 20.04 (20200402) with LVM encryption and 
automatic logon.
  So I enter my encryption password and after the motherboards boot logo it 
will login automatically to desktop. I also chose the additional drivers and so 
nvidia-driver-440.
  Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in 
settings. Next reboot, I enter my encryption password. When the automatic logon 
process should happen, the monitor turns off and says that no display signal is 
available.

  Currently I was able to return to a working setup by pressing CTRL + ALT + 
F4, login and enter the following commands to remove nvidia-driver and use XORG 
instead:
  sudo apt purge nvidia-driver-440
  sudo apt autoremove
  sudo reboot

  I am pretty sure that the issue will occur again, if I choose NVIDIA
  driver again.

  Any thoughts?

  EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the
  monitor was not turned on, the monitor reported no signal available
  after turning it on. I was not able to see the boot-up field to enter
  my encryption password. Unfortunately I didn't test, if I were able to
  enter my password and logon anyway. Workaround was to turn the monitor
  on, before starting the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 19:31:50 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] 
[1458:3762]
  InstallationDate: Installed on 2020-04-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd04/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871458/+subscriptions

--

[Desktop-packages] [Bug 1847675] Re: Lenovo thinkpad T440s Trackpoint doesn't work properly

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: libinput (Ubuntu)
   Status: New => Won't Fix

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Lenovo thinkpad T440s Trackpoint doesn't work properly

Status in libinput package in Ubuntu:
  Won't Fix
Status in xserver-xorg-input-libinput package in Ubuntu:
  Won't Fix

Bug description:
  1. middle click scroll doesn't work at all. Holding down the the
  middle scroll button while pushing the trackpoint results in the
  cursor freezing for a couple seconds.

  2. Trackpoint motion is extremely slow.

  3. Right-click doesn't work.

  I hadn't observed these problems with ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Oct 11 00:34:54 2019
  DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-11-15 (329 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet 
splash vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: Upgraded to disco on 2019-04-27 (166 days ago)
  dmi.bios.date: 03/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET98WW (2.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQCTO1WW
  dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1847675/+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 1871475] Re: Black screen after screen lock

Please try logging into "Ubuntu on Wayland" from the login screen and
tell us if that avoids the problem.

** Tags added: amdgpu

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

** Summary changed:

- Black screen after screen lock
+ [amdgpu] Black screen after screen lock

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

Title:
  [amdgpu] Black screen after screen lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I lock the screen with "Windows" + "L" key combination the screen
  gets locked, but I expect it to stay on and be locked. In Ubuntu
  20.04. when I do it the screen gets locked but get immediately black a
  sit would be in standby. The screen should stay on and show locked
  screen.

  This black screen happens often, but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:51:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871475/+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 1871475] Re: [amdgpu] Black screen after screen lock

And in case the problem is a crash somewhere, please also follow these
instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  [amdgpu] Black screen after screen lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I lock the screen with "Windows" + "L" key combination the screen
  gets locked, but I expect it to stay on and be locked. In Ubuntu
  20.04. when I do it the screen gets locked but get immediately black a
  sit would be in standby. The screen should stay on and show locked
  screen.

  This black screen happens often, but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:51:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871475/+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 1871414] Re: Pulseaudio repeatedly detects a headphone being plugged in when nothing is plugged in

** Summary changed:

- Pulseaudio incorrectly detects a headphone being plugged in
+ Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in

** Tags added: focal

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

** Summary changed:

- Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in
+ [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone being 
plugged in when nothing is plugged in

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

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now

[Desktop-packages] [Bug 1870830] Re: gnome-shell-extension-prefs not installed with base GNOME Shell installation

That's bug 1869635. It's unclear if that option should work or shouldn't
be shown at all. Still, it's best discussed in bug 1869635.

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

Title:
  gnome-shell-extension-prefs not installed with base GNOME Shell
  installation

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  This package is required for access to the settings dialog for any
  Gnome Shell extension, which will throw an error without it. It is no
  longer installed in 20.04 by default and has to be manually installed
  by the user, but I believe it should be installed by default.

  Here are some relevant discussions:
  https://www.reddit.com/r/Ubuntu/comments/fql7zz/ubuntu_2004_gnome_extensions/

  https://bugs.launchpad.net/ubuntu/focal/+source/gnome-shell-extension-
  dash-to-panel/+bug/1866070/comments/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870830/+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 1871403] Re: wifi won't connect, but kernel 5.6 fixes it

** Summary changed:

- wifi won't connect
+ wifi won't connect, but kernel 5.6 fixes it

** Package changed: xorg (Ubuntu) => linux (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/1871403

Title:
  wifi won't connect, but kernel 5.6 fixes it

Status in linux package in Ubuntu:
  New

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xser

[Desktop-packages] [Bug 1871477] Re: [nouveau] Ubuntu 18.04 freezes when using Zoom

It appears the nouveau kernel driver is crashing so that's likely the
problem.

You might want to try the proprietary Nvidia driver instead, in:

  Software & Updates > Additional Drivers


** Summary changed:

- Ubuntu 18.04 freezes when using Zoom
+ [nouveau] Ubuntu 18.04 freezes when using Zoom

** Tags added: bionic nouveau

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

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

Title:
  [nouveau] Ubuntu 18.04 freezes when using Zoom

Status in linux package in Ubuntu:
  New

Bug description:
  I use two monitors.
  I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

  I use : 
  Ubuntu 18.04.4 LTS
  5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  I believe that the error is due to what is displayed in :

  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 
i   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 
10)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 
I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 
i   resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 
i   resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

  Any hint?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871477/+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 1866088] Re: Problems with the Dock setting of "Show on" in the Appearance tab

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Problems with the Dock setting of "Show on" in the Appearance tab

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I use a laptop with external monitor in a dual display set-up.

  The "Screen Display" tab of Settings application correctly shows:

  Display 1 as the built-in display
  Display 2 as the external monitor

  If I go to the new "Appearance" tab I see that the Dock is set to
  display on the Built-in display but it is actually being displayed on
  the external monitor. If I change this setting to display on the
  external monitor it displays on the laptop's built-in display.

  Once set to "All displays" the setting can not be unset and the dock
  insists on being displayed on both the laptop's built-in display and
  the external monitor.

  I used the Dconf editor to set
  org.gnome.shell.extensions.dash-to-dock.multi-monitor to off to correct the 
problem although the settings application again shows that the dock is being 
displayed on the built-in display when in fact it is being shown on the 
external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 15:20:47 2020
  InstallationDate: Installed on 2019-05-17 (292 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2019-11-08 (116 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1866088/+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 1871358] Re: Dock Show on All Displays

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)

** Summary changed:

- Dock Show on All Displays
+ Dock shows on all displays even when you don't want it to (because all 
displays are the same model of monitor)

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

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

Title:
  Dock shows on all displays even when you don't want it to (because all
  displays are the same model of monitor)

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  In The Ubuntu Settings > Appearance there is a Dock option to "Show
  On" specific monitor.  If there are multiple monitors and they are of
  the same brand/model number, the setting gets confused and always
  defaults to "All displays".


  > lsb_release -rd

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  
  GNOME 3.36.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871358/+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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

Thanks. The log in comment #27 doesn't seem to provide clarification
other than it *doesn't* look like this bug at all, or any crash for that
matter. And the link in comment #28 is not retraceable :(

So I think we were right to call this bug closed in comment #24. But
also you seem to be experiencing some other bug so please continue
reporting new bugs for new crashes you experience.

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

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)

  The system beeps to indicate that the text isn't found, but then
  crashes.

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1849249/+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 1871519] Re: Cannot Adjust for TV and Scale at same time (simultaneously)

2020-04-07 Thread Gold Star

A very similar thing happens if you keep changing the Adjust for TV
slider after each time you click the green "Apply" button so that code
path should be tested as well.

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

Title:
  Cannot Adjust for TV and Scale at same time (simultaneously)

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

Bug description:
  ## Version tested:
  Ubuntu 20.04 Beta

  ## Reproduction steps:

  Boot Ubuntu 20.04 Beta ISO
  Launch Settings window
  Open the Display settings

  Click the button to set scale to 200%
  Push green apply button at top right of window
  (screen resize)
  Push Keep Changes button

  Click the button to set scale to 100% AND click the Adjust for TV slider
  Push green apply button at top right of window
  Push Keep Changes button
  >>> Adjust for TV is complete but scale is NOT 100% <<<
  >>> Adjust for TV slider is turned off still <<<

  Click the button to set scale to 100%
  Push green apply button at top right of window
  >>> Adjust for TV is turned off now (properly reflecting the slider value) <<<

  Click the button to set scale to 100%
  Push green apply button at top right of window
  Screen is finally adjust back to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 02:15:56 2020
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1871519/+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 1871519] [NEW] Cannot Adjust for TV and Scale at same time (simultaneously)

2020-04-07 Thread Gold Star

Public bug reported:

## Version tested:
Ubuntu 20.04 Beta

## Reproduction steps:

Boot Ubuntu 20.04 Beta ISO
Launch Settings window
Open the Display settings

Click the button to set scale to 200%
Push green apply button at top right of window
(screen resize)
Push Keep Changes button

Click the button to set scale to 100% AND click the Adjust for TV slider
Push green apply button at top right of window
Push Keep Changes button
>>> Adjust for TV is complete but scale is NOT 100% <<<
>>> Adjust for TV slider is turned off still <<<

Click the button to set scale to 100%
Push green apply button at top right of window
>>> Adjust for TV is turned off now (properly reflecting the slider value) <<<

Click the button to set scale to 100%
Push green apply button at top right of window
Screen is finally adjust back to 100%

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  8 02:15:56 2020
ExecutablePath: /usr/bin/gnome-control-center
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1871519

Title:
  Cannot Adjust for TV and Scale at same time (simultaneously)

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

Bug description:
  ## Version tested:
  Ubuntu 20.04 Beta

  ## Reproduction steps:

  Boot Ubuntu 20.04 Beta ISO
  Launch Settings window
  Open the Display settings

  Click the button to set scale to 200%
  Push green apply button at top right of window
  (screen resize)
  Push Keep Changes button

  Click the button to set scale to 100% AND click the Adjust for TV slider
  Push green apply button at top right of window
  Push Keep Changes button
  >>> Adjust for TV is complete but scale is NOT 100% <<<
  >>> Adjust for TV slider is turned off still <<<

  Click the button to set scale to 100%
  Push green apply button at top right of window
  >>> Adjust for TV is turned off now (properly reflecting the slider value) <<<

  Click the button to set scale to 100%
  Push green apply button at top right of window
  Screen is finally adjust back to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 02:15:56 2020
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1871519/+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 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
comment out the last line of:

  /usr/lib/udev/rules.d/61-gdm.rules

Although that will reintroduce bug 1705369 so you might need to also use
one of the other workarounds mentioned in that bug.

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  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.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+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 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
uncomment the last line of:

  /usr/lib/udev/rules.d/61-gdm.rules

Although that will reintroduce bug 1705369 so you might need to also use
one of the other workarounds mentioned in that bug.

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  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.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

2020-04-07 Thread Rocko

Do you mean a link to the original crash? This one has the same date as
the bug report:
https://errors.ubuntu.com/oops/4bb4a564-f475-11e9-b5e5-fa163e102db1

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some un-findable text in the find window and press ENTER (or 
click the Next button)

  The system beeps to indicate that the text isn't found, but then
  crashes.

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1849249/+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 1871422] Re: Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

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

Thanks for the bug report. This does indeed look like a duplicate of bug
1870637:

[10.855] (--) modeset(0): HDMI max TMDS frequency 30KHz
[10.855] (II) modeset(0): Not using default mode "3840x2160" (bad mode 
clock/interlace/doublescan)
[10.855] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)
[10.855] (II) modeset(0): Printing probed modes for output HDMI-1

** This bug has been marked a duplicate of bug 1870637
   Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Title:
  Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1870637

  The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 
2600.
  Still running a zotac nvidia GT1030 graphics card.
  I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

  I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
  If this would have fixed the issue i would have ordered a 3700X for my 
windows system and would have kept the ryzen 5 2600 for my ubuntu system, but 
since this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

  Before i do so; I'll try to enable wayland, as asked, but if i
  remember correctly i read on a post on omgunbuntu that wayland is
  currently disabled on the beta? Anyway, i'll have a look and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29: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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 17:05:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  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.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.9

[Desktop-packages] [Bug 1871391] Re: sound output dont change

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

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 1866194, 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 1866194
   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.

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

Title:
  sound output dont change

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Even with right output selected, the sound plays on the notebook
  output.

  I've tried restart the system, it dont change.  If i test the sound on
  the configs, i hear the sound right (on my phones).  But on spotify \
  chrome, the sound plays on notebook output.

  https://imgur.com/a/9SMeTYA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otavio154337 F pulseaudio
   /dev/snd/controlC0:  otavio154337 F pulseaudio
   /dev/snd/pcmC0D0c:   otavio154337 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 14:26:53 2020
  InstallationDate: Installed on 2020-02-27 (40 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN15WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R33126 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH-1060
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN15WW:bd11/08/2018:svnLENOVO:pn81M7:pvrLenovoLegionY530-15ICH-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R33126WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH-1060:
  dmi.product.family: Legion Y530-15ICH-1060
  dmi.product.name: 81M7
  dmi.product.sku: LENOVO_MT_81M7_BU_idea_FM_Legion Y530-15ICH-1060
  dmi.product.version: Lenovo Legion Y530-15ICH-1060
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871391/+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 1871063] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length()

Ideally, you're right. But this is the way gnome-shell is designed. So
the options we have right now are either to let extensions do anything
(break anything), or to disallow all extensions.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is all the information I was able to gather. GS crashed right
  after pressing Win+L on a bluetooth keyboard.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr  6 11:14:17 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-10-29 (524 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f3d04d6996d :  
mov(%rax),%rdi
   PC (0x7f3d04d6996d) ok
   source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/libffi.so.7
   () at /usr/lib/x86_64-linux-gnu/libffi.so.7
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length()
  UpgradeStatus: Upgraded to focal on 2020-03-27 (9 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871063/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

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

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

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (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: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+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 1871497] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

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

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 1871329, 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 1871329
   No "Select Audio Device" panel when plugging headphones, and no sound output 
to headphones

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

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871497/+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 1871514] [NEW] /usr/sbin/gdm3:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed

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

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 
3.34.1-1ubuntu1pop0~1571429866~19.10~5585283, the problem page at 
https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 
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: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: eoan focal

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

Title:
  
/usr/sbin/gdm3:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed

Status in gdm3 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 
3.34.1-1ubuntu1pop0~1571429866~19.10~5585283, the problem page at 
https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 
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/gdm3/+bug/1871514/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

Tracking in:

https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

** Description changed:

  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
+ https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: 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/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Description changed:

+ https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: 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/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: 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/libaccountsservice.so.0
   g_closure_invoke () fr

[Desktop-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

2020-04-07 Thread Yosep Perez

The attachments in the comments (not in the bug itself) where taken
using the latest stable kernel 5.6.2, this is because I wanted to see if
the issue was fixed in the meantime. But the behavior is exactly the
same, sadly

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

  It seems

[Desktop-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

2020-04-07 Thread Yosep Perez

After some debugging, I ended up doing strace on the pulseaudio server
to see if I could spot the issue and I think this is the closest I got
(in the attachment there's a bit more info):

write(5, "W", 1)= 1
read(16, "\0\0\0\0\1\0\0\0(\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0Front He"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114f40) = 0
write(5, "W", 1)= 1
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = 0
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = 0
read(16, "\0\0\0\0\1\0\0\0\v\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Headphon"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\n\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Headphon"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\5\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Surround"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\10\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Center P"..., 72) = 
72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\t\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0LFE Play"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\4\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Surround"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\6\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Center P"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\7\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0LFE Play"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, 0x7fff1d115520, 72)= -1 EAGAIN (Resource temporarily 
unavailable)
read(4, "WW", 10)   = 2
write(5, "W", 1)= 1
write(5, "W", 1)= 1
read(4, "WW", 10)   = 2
write(46, "\1\0\0\0\0\0\0\0", 8)= 8

Note that the FD 16 is "16u CHR 116,16 0t0 20030 /dev/snd/controlC1",
basically the control interface of the card I really want to be
listening to: card 1; the other card (0) is the one in the video card
which I don't really care

** Attachment added: "lsof+strace.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871414/+attachment/5349096/+files/lsof+strace.tar.gz

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack

[Desktop-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

2020-04-07 Thread Yosep Perez

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871414/+attachment/5349075/+files/alsa-info.txt

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

  It seems basically the same bug as this: 
https://bbs.archlinux.org/viewtopic.php?i

[Desktop-packages] [Bug 1868319] Re: PCI/internal sound card not detected

2020-04-07 Thread Hui Wang

@David,

Please upload the dmesg of -46 kernel.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Any time now, the sound card was deactivated, and it appears as a
  "Dummy device". I searched many forums about it, but nothing works.
  I'll be grateful if a program exists that I could install for sound
  card recognition.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 16:13:53 2020
  InstallationDate: Installed on 2020-03-19 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 054J60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1871023] Autopkgtest regression report (json-glib/1.4.4-2ubuntu0.19.10.1)

2020-04-07 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted json-glib (1.4.4-2ubuntu0.19.10.1) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

libgdata/0.17.11-3build1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#json-glib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1848919] Re: [snap] Permission denied on Private encrypted folder

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

** Changed in: apparmor (Ubuntu)
   Status: In Progress => 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/1848919

Title:
  [snap] Permission denied on Private encrypted folder

Status in AppArmor:
  Fix Released
Status in snapd:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1848919/+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 1871148] Re: services start before apparmor profiles are loaded

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

** Changed in: apparmor (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Released
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1871477] Re: Ubuntu 18.04 freezes when using Zoom

2020-04-07 Thread Chris Guiver

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 1871477

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.

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

Title:
  Ubuntu 18.04 freezes when using Zoom

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use two monitors.
  I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

  I use : 
  Ubuntu 18.04.4 LTS
  5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  I believe that the error is due to what is displayed in :

  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 
i   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 
10)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 
I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 
i   resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 
i   resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

  Any hint?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871477/+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()

2020-04-07 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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 1871503] [NEW] Samsung M2026 doesn't work (patch available)

2020-04-07 Thread Till W.

Public bug reported:

Splix is a free (libre) and open-source alternative to Samsung's closed-
source ULD driver. Next to being free, Splix also offers better
grayscale rendering than Samsung's ULD driver. Splix mainly provides a
raster-to-QPDL filter (QPDL is Samsung's proprietary printer command
language) and PPD files for respective printers.

In the past, I successfully used Splix to print with a Samsung M2022.
When I had to replace the printer with an almost identical M2026 (same
features, same enclosure, just younger) I noticed that the M2026 does
not work with Splix as supplied by Ubuntu. (Printer accepts print jobs
but does only produce empty pages or does not emit a page at all.)

I recently came across a patch (to Splix) from 2019 that makes the M2026
work by adjusting some details in the generated QPDL stream. The patch
was committed here: https://gitlab.com/ScumCoder/splix (looks like a
fork of the SourceForge repository where Splix was available in the
past). Using the code from the Gitlab repo, I was able to successfully
use the M2026 with Ubuntu 18.04.

Is there any way to get this modification into the Ubuntu splix
(printer-driver-splix) package? I'm willing to help by creating a patch
that can be applied against the package's source if needed/desired.

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

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

Title:
  Samsung M2026 doesn't work (patch available)

Status in splix package in Ubuntu:
  New

Bug description:
  Splix is a free (libre) and open-source alternative to Samsung's
  closed-source ULD driver. Next to being free, Splix also offers better
  grayscale rendering than Samsung's ULD driver. Splix mainly provides a
  raster-to-QPDL filter (QPDL is Samsung's proprietary printer command
  language) and PPD files for respective printers.

  In the past, I successfully used Splix to print with a Samsung M2022.
  When I had to replace the printer with an almost identical M2026 (same
  features, same enclosure, just younger) I noticed that the M2026 does
  not work with Splix as supplied by Ubuntu. (Printer accepts print jobs
  but does only produce empty pages or does not emit a page at all.)

  I recently came across a patch (to Splix) from 2019 that makes the
  M2026 work by adjusting some details in the generated QPDL stream. The
  patch was committed here: https://gitlab.com/ScumCoder/splix (looks
  like a fork of the SourceForge repository where Splix was available in
  the past). Using the code from the Gitlab repo, I was able to
  successfully use the M2026 with Ubuntu 18.04.

  Is there any way to get this modification into the Ubuntu splix
  (printer-driver-splix) package? I'm willing to help by creating a
  patch that can be applied against the package's source if
  needed/desired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1871503/+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 1871501] [NEW] Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

2020-04-07 Thread Seija Kijin

Public bug reported:

Ubuntu registers the USB Headset as a speaker too, as one an see when
the volume button is pushed and the volume is modified.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Tue Apr  7 18:01:01 2020
InstallationDate: Installed on 2020-04-04 (3 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of Settings"
   
https://bugs.launchpad.net/bugs/1871501/+attachment/5349044/+files/Screenshot%20from%202020-04-07%2017-57-03.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/1871501

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

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

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Tue Apr  7 18:01:01 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  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/1871501/+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 1871497] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

2020-04-07 Thread Seija Kijin

** Attachment added: "Settings screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871497/+attachment/5349040/+files/Screenshot%20from%202020-04-07%2017-57-03.png

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

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871497/+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 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

2020-04-07 Thread Gunnar Hjalmarsson

@Sebastien: Takao Fujiwara provided some hints about this and other
similar crash reports at the upstream issue I submitted. I'm thinking
that this may be something to look into post-release.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  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/ibus/+bug/1870747/+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 1871497] [NEW] Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

2020-04-07 Thread Seija Kijin

Public bug reported:

Ubuntu registers the USB Headset as a speaker too, as one an see when
the volume button is pushed and the volume is modified.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.4
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  seija  3751 F pulseaudio
 /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
 /dev/snd/controlC0:  gdm1130 F pulseaudio
  seija  3751 F pulseaudio
Date: Tue Apr  7 17:53:12 2020
InstallationDate: Installed on 2020-04-04 (3 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871497

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871497/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

2020-04-07 Thread Brian Murray

Hello Robert, or anyone else affected,

Accepted json-glib into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/json-
glib/1.4.4-2ubuntu0.19.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: json-glib (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: json-glib (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1871023] Please test proposed package

2020-04-07 Thread Brian Murray

Hello Robert, or anyone else affected,

Accepted json-glib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/json-
glib/1.4.2-3ubuntu0.18.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1871488] [NEW] gnome-online-accounts doesn't sync nextcloud calendar

2020-04-07 Thread Jeffrey Bouter

Public bug reported:

gnome-online-accounts does not synchronise calendars into the evolution
data server. Therefore, calendars are not displayed in the gnome-
calendar application or the time/calendar of gnome shell (when the clock
in the centre of the top bar is clicked)

Manually adding all CalDAV calendars in Evolution resolves the issue,
which makes me think the issue lies between gnome-online-accounts and
the evolution data server.

This may be related to bug #1866999

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr  7 22:48:37 2020
InstallationDate: Installed on 2020-03-17 (21 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

- gnome-online-accounts does not synchronise accounts into the evolution
+ gnome-online-accounts does not synchronise calendars into the evolution
  data server. Therefore, calendars are not displayed in the gnome-
  calendar application or the time/calendar of gnome shell (when the clock
  in the centre of the top bar is clicked)
  
  Manually adding all CalDAV calendars in Evolution resolves the issue,
  which makes me think the issue lies between gnome-online-accounts and
  the evolution data server.
  
  This may be related to bug #1866999
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  7 22:48:37 2020
  InstallationDate: Installed on 2020-03-17 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-online-accounts doesn't sync nextcloud calendar

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  gnome-online-accounts does not synchronise calendars into the
  evolution data server. Therefore, calendars are not displayed in the
  gnome-calendar application or the time/calendar of gnome shell (when
  the clock in the centre of the top bar is clicked)

  Manually adding all CalDAV calendars in Evolution resolves the issue,
  which makes me think the issue lies between gnome-online-accounts and
  the evolution data server.

  This may be related to bug #1866999

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  7 22:48:37 2020
  InstallationDate: Installed on 2020-03-17 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871488/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

The attachment "dual-jacks.patch" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1871456] Re: Files on desktop don't use custom icon

2020-04-07 Thread Sebastien Bacher

There is a similar report upstream on
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/92

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

Title:
  Files on desktop don't use custom icon

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Create a new file in the folder "~/Desktop".
  2. Right-click -> Properties -> change the icon to some other icon from 
/usr/share/icons/Yaru/48x48.
  3. Close the "Properties" dialogue.

  When viewing the Desktop folder in Nautilus directly, the icon is
  displayed correctly. However on the desktop itself, the file still
  uses the default icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 19:33:47 2020
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 
'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 
'starred', 'detailed_type']"
  InstallationDate: Installed on 2020-04-06 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1871456/+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 1871456] Re: Files on desktop don't use custom icon

2020-04-07 Thread Sebastien Bacher

Thank you for your bug report. The desktop view is handled by gnome-
shell-extension-desktop-icons, reassigning

** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-
icons (Ubuntu)

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

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

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

Title:
  Files on desktop don't use custom icon

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Create a new file in the folder "~/Desktop".
  2. Right-click -> Properties -> change the icon to some other icon from 
/usr/share/icons/Yaru/48x48.
  3. Close the "Properties" dialogue.

  When viewing the Desktop folder in Nautilus directly, the icon is
  displayed correctly. However on the desktop itself, the file still
  uses the default icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 19:33:47 2020
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 
'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 
'starred', 'detailed_type']"
  InstallationDate: Installed on 2020-04-06 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1871456/+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 1871422] Re: Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

** 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/1871422

Title:
  Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1870637

  The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 
2600.
  Still running a zotac nvidia GT1030 graphics card.
  I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

  I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
  If this would have fixed the issue i would have ordered a 3700X for my 
windows system and would have kept the ryzen 5 2600 for my ubuntu system, but 
since this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

  Before i do so; I'll try to enable wayland, as asked, but if i
  remember correctly i read on a post on omgunbuntu that wayland is
  currently disabled on the beta? Anyway, i'll have a look and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29: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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 17:05:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  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.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871422/+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 1871470] Re: Synaptics Trackpoint on Thinkpad T495 not precisely as in Windows

2020-04-07 Thread Sebastien Bacher

** Package changed: gnome-control-center (Ubuntu) => libinput (Ubuntu)

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

Title:
  Synaptics Trackpoint on Thinkpad T495 not precisely as in Windows

Status in libinput package in Ubuntu:
  New

Bug description:
  I have a Thinkpad T495 and run on it Windows 10 and Ubuntu 20.04. When
  I use the trackpoint in Windows it is working very smooth. It
  responses to the finger touch in a "lighter and smoother way". When I
  use the Trackpoint in Ubuntu 20.04 (or even 18.04) it generally works
  but the movement especially when you start pressing it is to slow, as
  there would be to much resistance.The finger gets tired after a while
  of working with the Trackpoint and work with it is a bit painful (yes,
  it hurts the finger top with the time really!)

  The feeling using it is by far not that good as in Windows. And in the
  Ubuntu settings there is no separate option to set the Trackpoint
  speed and sensivity separately.

  By other words the driver for the synaptics driver is not optimal. As
  I only use Trackpoint, it is for me a real criterium to use or not use
  Ubuntu.

  ProblemType: Bug
  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
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:11:04 2020
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1871470/+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 1871403] Re: wifi won't connect

** 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/1871403

Title:
  wifi won't connect

Status in xorg package in Ubuntu:
  New

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-i

[Desktop-packages] [Bug 1871475] Re: Black screen after screen lock

** 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/1871475

Title:
  Black screen after screen lock

Status in xorg package in Ubuntu:
  New

Bug description:
  When I lock the screen with "Windows" + "L" key combination the screen
  gets locked, but I expect it to stay on and be locked. In Ubuntu
  20.04. when I do it the screen gets locked but get immediately black a
  sit would be in standby. The screen should stay on and show locked
  screen.

  This black screen happens often, but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:51:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871475/+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 1871403] [NEW] wifi won't connect

You have been subscribed to a public bug:

My wifi adapter won't connect under Kubuntu.  It works fine when I boot
the same laptop under Ubuntu 18.04, but when I boot under Kubuntu 20.04,
I get "Configuring Interface" followed by "Wireless interface (wlp1s0)
The wifi network could not be found."

It worked fine up until today.  Ethernet connection works fine.

I tried restarting NetworkManager.service in systemctl and I get this:

NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
   Docs: man:NetworkManager(8)
   Main PID: 4231 (NetworkManager)
  Tasks: 3 (limit: 16627)
 Memory: 5.0M
 CGroup: /system.slice/NetworkManager.service
 └─4231 /usr/sbin/NetworkManager --no-daemon

Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] device 
(wlp1s0): supplicant interface state: scanning -> authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] device 
(p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] device 
(wlp1s0): supplicant interface state: authenticating -> disconnected
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] device 
(p2p-dev-wlp1s0): supplicant management interface state: authenticating -> 
disconnected
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] device 
(wlp1s0): Activation: (wifi) association took too long, failing activation
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] device 
(wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] device 
(wlp1s0): Activation: failed for connection 'BoulderNET'
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] device 
(wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 
'managed')
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] device 
(wlp1s0): supplicant interface state: disconnected -> inactive
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] device 
(p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
dennis@ZenBook:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.6.1-050601-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Apr  7 10:14:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
InstallationDate: Installed on 2020-03-06 (31 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434DA_UM433DA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434DA
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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434DA_UM433DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal kubuntu ubuntu
-- 
wifi won't connect
https://bugs.launchpad.net/bugs/1871403
You received this bug notification because you are a member of Desktop 
Packages, which is sub

[Desktop-packages] [Bug 1871422] [NEW] Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

You have been subscribed to a public bug:

This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1870637

The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 2600.
Still running a zotac nvidia GT1030 graphics card.
I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
If this would have fixed the issue i would have ordered a 3700X for my windows 
system and would have kept the ryzen 5 2600 for my ubuntu system, but since 
this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

Before i do so; I'll try to enable wayland, as asked, but if i remember
correctly i read on a post on omgunbuntu that wayland is currently
disabled on the beta? Anyway, i'll have a look and report back

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29: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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 17:05:52 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
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.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
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.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu
-- 
Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600
https://bugs.launchpad.net/bugs/1871422
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 1871475] [NEW] Black screen after screen lock

You have been subscribed to a public bug:

When I lock the screen with "Windows" + "L" key combination the screen
gets locked, but I expect it to stay on and be locked. In Ubuntu 20.04.
when I do it the screen gets locked but get immediately black a sit
would be in standby. The screen should stay on and show locked screen.

This black screen happens often, but sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 20:51:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Picasso [17aa:5125]
InstallationDate: Installed on 2020-04-02 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: LENOVO 20NKS01Y00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R12ET46W(1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NKS01Y00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T495
dmi.product.name: 20NKS01Y00
dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
dmi.product.version: ThinkPad T495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
Black screen after screen lock
https://bugs.launchpad.net/bugs/1871475
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 1848836] Re: Unmounted drive shortcut is on the dock

2020-04-07 Thread Andrey Kotlyar

Oh, i encountered this bug today, found out that it was fixed upstream
several months ago and apparently is fixed in 20.04. What should i do in
this situation?

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

Title:
  Unmounted drive shortcut is on the dock

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  On ubuntu 19.10,when the google account is set, there is a shortcut in
  nautilus.

  This shortcut, even when if it's not mounted, is visible in the dock
  when show-mounts option is actived.

  If i'm not wrong, it should be visible only when it's mounted

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1848836/+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 1870795] Re: Appindicator not showing under wayland

2020-04-07 Thread Paul Broadhead

That formatting is bad, here and attachment.

** Attachment added: "journalctl-output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+attachment/5348988/+files/journalctl-output.txt

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

Title:
  Appindicator not showing under wayland

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  $ apt-cache policy gnome-session-wayland
  gnome-session-wayland:
Installed: (none)
Candidate: 3.36.0-2ubuntu1
Version table:
   3.36.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages

  An app-indicator icon does not show when I login using the default
  gnome session (wayland).  If I choose the xorg session, the icon shows
  as normal.  Under wayland, the icon does appear if I lock my session
  then log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  4 15:30:40 2020
  InstallationDate: Installed on 2019-12-15 (111 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+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 1870795] Re: Appindicator not showing under wayland

2020-04-07 Thread Paul Broadhead

The journalctl output is very verbose and contains all my system information, 
do you really want and need all that or is there a particular section?  Below 
is a portion that mentions app indicator.  If I lock my screen, then unlock, 
the output includes a few additional lines but nothing about app-indicator. My 
only indicator is one I wrote myself:
https://launchpad.net/el-time-applet/appindicator
If there is another indicator you want me to test to rule out an error my part 
then please let me know.
Thanks,
Paul


Apr 07 20:06:22 padfoot colord[1774]: failed to get session [pid 20630]: No 
data available
Apr 07 20:06:22 padfoot gnome-shell[20125]: Failed to set CRTC gamma: 
drmModeCrtcSetGamma on CRTC 48 failed: Permission denied
Apr 07 20:06:22 padfoot gnome-shell[20478]: gtk_icon_theme_get_for_screen: 
assertion 'GDK_IS_SCREEN (screen)' failed
Apr 07 20:06:22 padfoot gnome-shell[20478]: JS ERROR: TypeError: src is null

connectSmart4A@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:189:21

connectSmart@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:214:31

_init@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:325:14

_init@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:42:25

_registerItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:95:22

_ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:123:14

RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:169:14

_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371:35

_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
Apr 07 20:06:22 padfoot systemd[20398]: GNOME session X11 services is not 
active.
Apr 07 20:06:22 padfoot systemd[20398]: Dependency failed for GNOME XSettings.
Apr 07 20:06:22 padfoot systemd[20398]: gsd-xsettings.target: Job 
gsd-xsettings.target/start failed with result 'dependency'.
Apr 07 20:06:22 padfoot gnome-shell[20478]: GNOME Shell started at Tue Apr 07 
2020 20:06:20 GMT+0100 (BST)
Apr 07 20:06:22 padfoot gnome-shell[20478]: Registering session with GDM
Apr 07 20:06:22 padfoot systemd[20398]: Starting GNOME XSettings...
Apr 07 20:06:22 padfoot systemd[20031]: Stopped target GNOME Wayland Session 
(session: gnome-login).
Apr 07 20:06:22 padfoot systemd[20031]: Stopped target Current graphical user 
session.

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

Title:
  Appindicator not showing under wayland

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  $ apt-cache policy gnome-session-wayland
  gnome-session-wayland:
Installed: (none)
Candidate: 3.36.0-2ubuntu1
Version table:
   3.36.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages

  An app-indicator icon does not show when I login using the default
  gnome session (wayland).  If I choose the xorg session, the icon shows
  as normal.  Under wayland, the icon does appear if I lock my session
  then log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  4 15:30:40 2020
  InstallationDate: Installed on 2019-12-15 (111 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+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 1868319] Re: PCI/internal sound card not detected

2020-04-07 Thread David

I know that If I say that there is still no sound on kernel 5.3.0-46, you will 
ask me to try 5.3.0-47...and so on and so on...
But nonetheless, here we go

user@G3:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
user@G3:~$ uname -r
5.3.0-46-generic


Someone should really start working on it. Google suggests there is a handful 
of users affected by this bug with no obvious solution.


** Attachment added: "Screenshot from 2020-04-07 20-18-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+attachment/5348986/+files/Screenshot%20from%202020-04-07%2020-18-41.png

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Any time now, the sound card was deactivated, and it appears as a
  "Dummy device". I searched many forums about it, but nothing works.
  I'll be grateful if a program exists that I could install for sound
  card recognition.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 16:13:53 2020
  InstallationDate: Installed on 2020-03-19 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 054J60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

2020-04-07 Thread Michael Weimann

Present on current 20.04 dev release with vanilla GNOME.

While this bug doesn't affect any functionality is shows me every day a
broken UI. That reduces the fun using Ubuntu / snaps.

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1871009] Re: Firefox doesn't restart after update

2020-04-07 Thread fabtagon

Installation happened about 02:29:09, as atp log tells:

Start-Date: 2020-04-06  02:29:09
Commandline: apt-get upgrade -y
Requested-By: USERNAME (1001)
Upgrade: firefox-locale-de:amd64 (74.0+build3-0ubuntu0.18.04.1, 
74.0.1+build1-0ubuntu0.18.04.1), firefox-locale-en:amd64 
(74.0+build3-0ubuntu0.18.04.1, 74.0.1+build1-0ubuntu0.18.04.1), 
firefox-locale-sv:amd64 (74.0+build3-0ubuntu0.18.04.1, 
74.0.1+build1-0ubuntu0.18.04.1), firefox:amd64 (74.0+build3-0ubuntu0.18.04.1, 
74.0.1+build1-0ubuntu0.18.04.1)
End-Date: 2020-04-06  02:29:35


** Attachment added: "journal.firefox"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871009/+attachment/5348987/+files/journal.firefox

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

Title:
  Firefox doesn't restart after update

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to firefox amd64 74.0.1+build1-0ubuntu0.18.04.1 (using
  apt-get), a message appeared in the running Firefox session: 'Firefox
  needs to be restarted' (as usual, nothing wrong with that). After
  clicking ok (or 'do it now' or what the exact message was), Firefox
  terminates.

  Expected behaviour: Firefox actually restarts

  Experienced behaviour: Nothing seemed to happen. Firefox terminated
  but never came back. (Starting Firefox again by hand worked
  flawlessly.)

  I have no profiles defined. I don't usually pass any options when
  starting Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 74.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab3616 F pulseaudio
   /dev/snd/controlC1:  fab3616 F pulseaudio
  BrokenPermissions:
   saved-telemetry-pings/a1103722-309c-47da-b9da-2bc9411237b9 (0o600, wrong 
owner)
   saved-telemetry-pings/e1cac187-9dd1-48b9-bb99-8c67374c7212 (0o600, wrong 
owner)
   saved-telemetry-pings/fbf7331c-39a9-4539-97fa-280e7d343563 (0o600, wrong 
owner)
  BuildID: 20200403064753
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 03:13:58 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-04-27 (1805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.23.1 dev eth0 proto dhcp metric 100 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.136 metric 
100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-f8832267-2764-4f52-b9df-136771180712
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=74.0.1/20200403064753 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-f8832267-2764-4f52-b9df-136771180712
   bp-f03b7d3e-1a66-441d-be5d-cedc11180201
   bp-610fb53c-4664-4692-8e37-62c501180107
   bp-708689c3-ba2d-427e-a43b-605df2141112
   bp-b2e12bb9-63b8-494d-9390-f5d722140521
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (596 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871009/+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.n

[Desktop-packages] [Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

2020-04-07 Thread Michael

** Attachment added: "The monitors.xml with 100% scaling"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870779/+attachment/5348985/+files/monitors.xml

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

2020-04-07 Thread Michael

Now, I switched back to Nvidia 440, scale 100% and I'm able to use the
system again. (Of course, I can hardly read anything, because it is so
small)

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1871477] [NEW] Ubuntu 18.04 freezes when using Zoom

2020-04-07 Thread TASSOS PANAGIOTOPOULOS

Public bug reported:

I use two monitors.
I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

I use : 
Ubuntu 18.04.4 LTS
5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

I believe that the error is due to what is displayed in :

Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 i 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 10)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 I 
  resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 i 
  resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 I 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 i 
  resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

Any hint?

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

** Attachment added: "Output of journalctl -b -1"
   
https://bugs.launchpad.net/bugs/1871477/+attachment/5348984/+files/journal.txt

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

Title:
  Ubuntu 18.04 freezes when using Zoom

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use two monitors.
  I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

  I use : 
  Ubuntu 18.04.4 LTS
  5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  I believe that the error is due to what is displayed in :

  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 
i   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 
10)
  Απρ 07 20:37:57 igor-MS-7A72

[Desktop-packages] [Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

2020-04-07 Thread Michael

I did some additional testing. If I set the scale in .config/monitors.xml back 
to 1, I am able to login again. So the problem is caused by the scaling. If I 
set the scaling is set to 200% everything works well until the next reboot.
It tried the nvidia driver 435 and had the same effect. 
I switched to the Nouveau driver and now the system does not boot anymore. I do 
not even reach the login screen.

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09: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:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1867491] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1867491/+attachment/5348964/+files/Stacktrace.txt

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

Title:
  info assert failure: free(): double free detected in tcache 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  Program did not open

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CurrentDesktop: KDE
  Date: Sat Mar 14 18:49:03 2020
  ExecutablePath: /usr/bin/info
  ProcCmdline: /usr/bin/info
  Signal: 6
  SourcePackage: texinfo
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected 
in tcache 2") at malloc.c:5347
   _int_free (av=av@entry=0x7f239f8c5b80 , 
p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201
   _int_realloc (av=av@entry=0x7f239f8c5b80 , 
oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at 
malloc.c:4618
   __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226
  Title: info assert failure: free(): double free detected in tcache 2
  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/texinfo/+bug/1867491/+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 1867491] Re: info assert failure: free(): double free detected in tcache 2

2020-04-07 Thread Brian Murray

** Tags removed: apport-failed-retrace

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

Title:
  info assert failure: free(): double free detected in tcache 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  Program did not open

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CurrentDesktop: KDE
  Date: Sat Mar 14 18:49:03 2020
  ExecutablePath: /usr/bin/info
  ProcCmdline: /usr/bin/info
  Signal: 6
  SourcePackage: texinfo
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected 
in tcache 2") at malloc.c:5347
   _int_free (av=av@entry=0x7f239f8c5b80 , 
p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201
   _int_realloc (av=av@entry=0x7f239f8c5b80 , 
oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at 
malloc.c:4618
   __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226
  Title: info assert failure: free(): double free detected in tcache 2
  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/texinfo/+bug/1867491/+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 1867491] info assert failure: free(): double free detected in tcache 2

StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in 
tcache 2") at malloc.c:5347
 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, 
have_lock=have_lock@entry=1) at malloc.c:4201
 _int_realloc (av=av@entry=0x7f239f8c5b80 , 
oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at 
malloc.c:4618
 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=bytes@entry=488) at 
malloc.c:3226

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

Title:
  info assert failure: free(): double free detected in tcache 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  Program did not open

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CurrentDesktop: KDE
  Date: Sat Mar 14 18:49:03 2020
  ExecutablePath: /usr/bin/info
  ProcCmdline: /usr/bin/info
  Signal: 6
  SourcePackage: texinfo
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected 
in tcache 2") at malloc.c:5347
   _int_free (av=av@entry=0x7f239f8c5b80 , 
p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201
   _int_realloc (av=av@entry=0x7f239f8c5b80 , 
oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at 
malloc.c:4618
   __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226
  Title: info assert failure: free(): double free detected in tcache 2
  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/texinfo/+bug/1867491/+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 1867491] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1867491/+attachment/5348966/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1867491/+attachment/5337096/+files/CoreDump.gz

** Changed in: texinfo (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  info assert failure: free(): double free detected in tcache 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  Program did not open

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CurrentDesktop: KDE
  Date: Sat Mar 14 18:49:03 2020
  ExecutablePath: /usr/bin/info
  ProcCmdline: /usr/bin/info
  Signal: 6
  SourcePackage: texinfo
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected 
in tcache 2") at malloc.c:5347
   _int_free (av=av@entry=0x7f239f8c5b80 , 
p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201
   _int_realloc (av=av@entry=0x7f239f8c5b80 , 
oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at 
malloc.c:4618
   __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226
  Title: info assert failure: free(): double free detected in tcache 2
  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/texinfo/+bug/1867491/+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 1867491] StacktraceSource.txt