[Desktop-packages] [Bug 1919955] [NEW] weird graphics artifacts in Firefox on Xorg after upgrade

2021-03-17 Thread rue
Public bug reported:

Hi, just updated today and after restart I logged in under Xorg and when 
opening Firefox you get blue and black pixelated static across the screen. this 
only happens running Xorg, not under Wayland. A bit hard to explain the issue, 
so added a screenshot
Also this could be an Xorg issue 
It only seems to affect Firefox. 
Thanks 
Rue

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: firefox 86.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rue5652 F pulseaudio
BuildID: 20210222142601
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 18 18:12:48 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2021-03-16 (1 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
IpRoute:
 default via 192.168.1.254 dev enp0s25 proto dhcp metric 100 
 169.254.0.0/16 dev enp0s25 scope link metric 1000 
 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.70 metric 100
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=86.0/20210222142601
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2010
dmi.bios.release: 1.5
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786H1 v01.05
dmi.board.name: 304Ah
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786H1v01.05:bd06/09/2010:br1.5:svnHewlett-Packard:pnHPCompaq8100EliteSFFPC:pvr:rvnHewlett-Packard:rn304Ah:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq 8100 Elite SFF PC
dmi.product.sku: LE093PA#ABG
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Screenshot of graphics issue on Firefox"
   
https://bugs.launchpad.net/bugs/1919955/+attachment/5477724/+files/Screenshot%20from%202021-03-18%2018-27-33.png

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

Title:
  weird graphics artifacts in Firefox on Xorg after upgrade

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi, just updated today and after restart I logged in under Xorg and when 
opening Firefox you get blue and black pixelated static across the screen. this 
only happens running Xorg, not under Wayland. A bit hard to explain the issue, 
so added a screenshot
  Also this could be an Xorg issue 
  It only seems to affect Firefox. 
  Thanks 
  Rue

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 86.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rue5652 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 18 18:12:48 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-03-16 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 

[Desktop-packages] [Bug 1918186] Re: tracker-store crashed with signal 5 in g_printerr()

2021-03-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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


[Desktop-packages] [Bug 1175914] Re: Sound Settings is showing HDMI audio settings for internal speakers after HDMI cable is removed

2021-03-17 Thread Po-Hsu Lin
Precise EOL.


** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Sound Settings is showing HDMI audio settings for internal speakers
  after HDMI cable is removed

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 12.04.2 precise

  Steps:
  1. Plug the HDMI cable to the laptop, and open the Sound Settings
  2. Switch the output device form built-in speakers to HDMI output
  3. Close the Sound Settings and play sound, make sure it's coming from the 
HDMI device
  4. Unplug the HDMI cable, play sound again.

  Expected Results:
  It should be played through the built-in speaker on the laptop.

  Actual Results:
  Nothing happened, and if you open the Sound Settings, the HDMI device is 
removed from the devices list, but still can be seen in the "Setting for 
Speakers" part on the right-hand-side (please find attachment for screen shot)
  You have select the internal speaker manually to make it back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.9
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Thu May  2 23:53:00 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: gnome-control-center 1:3.4.2-0ubuntu0.9
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Tags:  precise running-unity
  Uname: Linux 3.5.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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


[Desktop-packages] [Bug 1919951] [NEW] snap install seemed to crash the machine, reboot now put package management in a bad state

2021-03-17 Thread Doug Jacobs
Public bug reported:

Related to bug #1886414

Ubuntu 20.04 LTE desktop VirtualBox VM

Tried installing chromium-browser.

Seemed to hang at "installing chromium snap".
Terminal and desktop were no longer responsive, so I had to reboot the VM, 
which apparently left the package manager in an inconsistent state.


doug@ubuntudesktop:~$ sudo apt remove chromium-browser
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  chromium-browser
0 upgraded, 0 newly installed, 1 to remove and 65 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
dpkg: error processing package chromium-browser (--remove):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting a removal
dpkg: too many errors, stopping
Errors were encountered while processing:
 chromium-browser
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.163-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 chromium-browser:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 18 12:02:11 2021
Dependencies:
 
DpkgTerminalLog:
 dpkg: error processing package chromium-browser (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2021-03-17 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: chromium-browser
Title: package chromium-browser 80.0.3987.163-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  snap install seemed to crash the machine, reboot now put package
  management in a bad state

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Related to bug #1886414

  Ubuntu 20.04 LTE desktop VirtualBox VM

  Tried installing chromium-browser.

  Seemed to hang at "installing chromium snap".
  Terminal and desktop were no longer responsive, so I had to reboot the VM, 
which apparently left the package manager in an inconsistent state.

  
  doug@ubuntudesktop:~$ sudo apt remove chromium-browser
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
chromium-browser
  0 upgraded, 0 newly installed, 1 to remove and 65 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  dpkg: error processing package chromium-browser (--remove):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting a removal
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   chromium-browser
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.163-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   chromium-browser:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 18 12:02:11 2021
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2021-03-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: 

[Desktop-packages] [Bug 1250400] Re: Sometime the last desktop session will flash back on restart with AMD Radeon HD 8410G[1002:999a] and radeon driver

2021-03-17 Thread Po-Hsu Lin
EOL, closing it.

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Sometime the last desktop session will flash back on restart with AMD
  Radeon HD 8410G[1002:999a] and radeon driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Won't Fix

Bug description:
  CID: 201303-13027 Dell Inspiron 5535

  When rebooting the laptop, sometimes you will see the last window / programs 
that you opened before you reboot the laptop.
  It seems that it doesn't matter if you did close them before rebooting the 
system or not.
  This may raise some security concern.

  Steps:
  1. Install 12.04.3 + update, boot to desktop
  2. Open your home folder
  3. Leave it there and reboot

  Expected result:
  You won't see that home folder shows up during the boot session.

  Actual result:
  The home folder will flash back after the logo screen, 

  Not only the file manager, I also saw terminal / Firefox browser / movie 
player flash back before on this system.
  And this won't happen if the proprietary driver was installed.

  Video attached, you could forward to 00:55 to see the flash back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-33-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic [HD-Audio Generic], device 0: ALC283 Analog [ALC283 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1748 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1748 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0444000 irq 52'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100300'
 Controls  : 7
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xf044 irq 16'
 Mixer name : 'Realtek ALC283'
 Components : 'HDA:10ec0283,102805c9,0013'
 Controls  : 16
 Simple ctrls  : 7
  Date: Tue Nov 12 04:21:56 2013
  HibernationDevice: RESUME=UUID=1b4b40a0-94db-4ba3-8760-ad504ab607ec
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Inspiron 5535
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic 
root=UUID=d9afb8c3-ca77-4a23-9d60-a19f45ab2f8d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-33-generic N/A
   linux-backports-modules-3.8.0-33-generic  N/A
   linux-firmware1.79.7
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-lts-raring
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X18
  dmi.board.name: 0MN77T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X18
  dmi.modalias: 
dmi:bvnDellInc.:bvrX18:bd03/15/2013:svnDellInc.:pnInspiron5535:pvr1747:rvnDellInc.:rn0MN77T:rvrX01:cvnDellInc.:ct8:cvrX18:
  dmi.product.name: Inspiron 5535
  dmi.product.version: 1747
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1250400/+subscriptions

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


[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2021-03-17 Thread Daniel van Vugt
Continued in bug 1811023.

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

Title:
  Desktop fails to boot in vbox:  Xorg assert failure: Xorg:
  ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
  `!global_keys[type].created' failed.

Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280
  https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80

  ---

  Test Case:
  Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box

  Actual Result
  Black screen or dropped to the login screen if the user skips ubiquity-dm

  Workaround:
  Add nomodeset on the kernel command line or from the boot menu, press F6 then 
select nomodeset

  Possibly a duplicate of bug 1432137

  Fix:
  Backport a patch from 1.20.2

  Regression potential:
  None really, we've had this xserver version since 18.10 and in the HWE 
backport, this patch backport is for 18.04 stock xserver but should work the 
same. It just skips initializing glamor if the system is using software 
fallback.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  CasperVersion: 1.395
  CompositorRunning: None
  Date: Mon Sep 17 12:42:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:

  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd ---  keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92
   __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, 
function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101
   dixRegisterPrivateKey ()
  Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1792932/+subscriptions

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

[Desktop-packages] [Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2021-03-17 Thread Daniel van Vugt
** Tags added: groovy hirsute

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

Title:
  Xorg aborts with ../../../../dix/privates.c:384:
  dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 
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/xorg-server/+bug/1811023/+subscriptions

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


[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`

2021-03-17 Thread Daniel van Vugt
Indeed comment #13 is bug 1905519, but I don't think that's related to
this 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/1915481

Title:
  [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg)
  after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-17 Thread Jalansh Munshi
Interesting, I do not get the issue now. However, I did check multiple
times and in different directories before opening this bug. And since it
has already been reported before, means there may have been a problem
with my system or something else.

Nevertheless, it is working fine now. I checked it with the same .zip
file I used to report this bug.

If this happens again, then I will make sure to report it.

Thanks, Sebastien!

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1919008/+subscriptions

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


[Desktop-packages] [Bug 1919927] [NEW] Wrong (or no) signals are emitted when icons are added / removed

2021-03-17 Thread Treviño
Public bug reported:

[ Impact ]

When adding and removing signals the indicators extension should emit signals 
following the protocol
  
https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierWatcher/

So we should emit the service name by default when known

[ Test case ]

Run
 dbus-monitor --session "interface='org.kde.StatusNotifierWatcher'"

When an indicator is added, signals such as should be emitted:

signal time=1616029764.911986 sender=:1.34490 -> destination=(null destination) 
serial=3905 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
   string ":1.109/org/ayatana/NotificationItem/psensor"
signal time=1616029764.928864 sender=:1.34490 -> destination=(null destination) 
serial=3991 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
   string ":1.34459/StatusNotifierItem"
 
When removed:
signal time=1616033768.529066 sender=:1.34490 -> destination=(null destination) 
serial=8711 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered
   string ":1.34649/StatusNotifierItem"

Removed events should be also emitted when the extension is disabled via
gnome-shell-extension-prefs

[ Regression potential ]

Some clients won't interpret the events correctly causing the indicator
not to work as expected

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Affects: gnome-shell-extension-appindicator (Ubuntu Focal)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Wrong (or no) signals are emitted when icons are added / removed

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  When adding and removing signals the indicators extension should emit signals 
following the protocol

https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierWatcher/

  So we should emit the service name by default when known

  [ Test case ]

  Run
   dbus-monitor --session "interface='org.kde.StatusNotifierWatcher'"

  When an indicator is added, signals such as should be emitted:

  signal time=1616029764.911986 sender=:1.34490 -> destination=(null 
destination) serial=3905 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.109/org/ayatana/NotificationItem/psensor"
  signal time=1616029764.928864 sender=:1.34490 -> destination=(null 
destination) serial=3991 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.34459/StatusNotifierItem"
   
  When removed:
  signal time=1616033768.529066 sender=:1.34490 -> destination=(null 
destination) serial=8711 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered
 string ":1.34649/StatusNotifierItem"

  Removed events should be also emitted when the extension is disabled
  via gnome-shell-extension-prefs

  [ Regression potential ]

  Some clients won't interpret the events correctly causing the
  indicator not to work as expected

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

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


[Desktop-packages] [Bug 1919476] Re: Document Viewer window overlaps ubuntu-dock

2021-03-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1917939 ***
https://bugs.launchpad.net/bugs/1917939

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 1917939, 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 1917939
   windows maximise underneath dock

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

Title:
  Document Viewer window overlaps ubuntu-dock

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

Bug description:
  I maximized the Document Viewer window which was minimized and the window 
overlaps the ubuntu-dock.
  see attached image

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 16:39:50 2021
  InstallationDate: Installed on 2021-02-28 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  PackageArchitecture: all
  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/1919476/+subscriptions

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


[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`

2021-03-17 Thread Walt Mankowski
To be clear, comment #13 appears to be a duplicate of the bug report in
comment #14.

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

Title:
  [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg)
  after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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


[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`

2021-03-17 Thread Walt Mankowski
This appears to be a duplicate of
https://bugs.launchpad.net/bugs/1905519

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

Title:
  [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg)
  after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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


[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade`

2021-03-17 Thread Walt Mankowski
Something different happened tonight, but it feels related so I'm going
to post it with this bug report.

Tonight I did an apt upgrade for a single package -- containerd. Gnome
didn't crash this time, but a short time later I noticed that
/var/log/syslog was filling up with the following messages:

Mar 17 20:35:29 scruffy gnome-shell[9529]: Object St.Bin (0x5558975eac80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Mar 17 20:35:29 scruffy gnome-shell[9529]: == Stack trace for context 
0x555888e95220 ==
Mar 17 20:35:29 scruffy gnome-shell[9529]: #0   7ffddf081900 I   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1ee0192a1240 @ 208)

These 3 lines were being repeated dozens of times a second, and started
at the same time I did the upgrade. I didn't know how else to stop them
so I rebooted. After rebooting the system seems fine again.

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

Title:
  [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg)
  after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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


[Desktop-packages] [Bug 1919924] [NEW] Scrolling on label doesn't work

2021-03-17 Thread Treviño
Public bug reported:

[ Impact ]

Scrolling on indicator label doesn't cause the scroll appindicator event
to be emitted

[ Test case ]

Using the appindicator test tool:
 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js

1. Run it with gjs
2. Show a label
3. Ensure that scroll events are printed in the terminal and that the icon is 
changed

[ Regression potential ]

Scroll events on icon doesn't work anymore

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Committed

** Affects: gnome-shell-extension-appindicator (Ubuntu Focal)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

Title:
  Scrolling on label doesn't work

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  Scrolling on indicator label doesn't cause the scroll appindicator
  event to be emitted

  [ Test case ]

  Using the appindicator test tool:
   
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js

  1. Run it with gjs
  2. Show a label
  3. Ensure that scroll events are printed in the terminal and that the icon is 
changed

  [ Regression potential ]

  Scroll events on icon doesn't work anymore

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

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


[Desktop-packages] [Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s

2021-03-17 Thread Hasan Mahmood
Hello,

Still have this issue ... could anyone help/investigate please?

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

Title:
  Bad sound quality (no bass) on Thinkpad T490s

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works on with 20.04 on the Thinkpad T490s, but sound quality is
  noticeably worse than on Windows. It looks like the same bug here:
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hmahmood   1360 F pulseaudio
   /dev/snd/pcmC0D0p:   hmahmood   1360 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 19:14:57 2021
  InstallationDate: Installed on 2021-01-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2020
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET92W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NYS83800
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490s
  dmi.product.name: 20NYS83800
  dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s
  dmi.product.version: ThinkPad T490s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions

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


[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2021-03-17 Thread Joel Rogers
It is happening in 20.04 after an update earlier in the week for me.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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


[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-03-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Triaged
Status in gnome-shell-extension-appindicator source package in Focal:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Groovy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Triaged

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions

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


[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-03-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Triaged
Status in gnome-shell-extension-appindicator source package in Focal:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Groovy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Triaged

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions

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


[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray

2021-03-17 Thread Treviño
*** This bug is a duplicate of bug 1905370 ***
https://bugs.launchpad.net/bugs/1905370

** This bug has been marked a duplicate of bug 1905370
   Qt-based tray icons not displayed on start-up

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

Title:
  No system tray detected by hp-systray

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

Bug description:
  I have hp-systray -x as one of the startup applications when I login.
  This app exits with the following error:

  HPLIP Status service
  No system tray detected on this system.
  Unable to start, exiting.

  Once logged in, if I start hp-systray -x from the terminal it works
  fine. This started happening after updating gnome-shell-extension-
  appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 11:41:23 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-10 (1655 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1902601] Re: gnome-shell, after a while, uses large CPU%, everything is SLOW

2021-03-17 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405

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

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

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

Title:
  gnome-shell, after a while, uses large CPU%, everything is SLOW

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3347
  They wanted me to file this with YOU.

  My bug description is too long for this area, so I'm attaching the 
description as
  a file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  2 17:02:12 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (228 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1919146] Re: Missing runtime dependency on libx11-xcb1

2021-03-17 Thread Olivier Tilloy
** Summary changed:

- Dependency removed on chromium-browser
+ Missing runtime dependency on libx11-xcb1

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

Title:
  Missing runtime dependency on libx11-xcb1

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  This morning we noticed that in the latest version of chromium-browser on 
18.04 (89.0.4389.82-0ubuntu0.18.04.1) the dependency on libx11-xcb1 was removed.
  This caused our use-case with chromium-browser to break.
  For now we install libx11-xcb1 separately, but this seems like a breaking 
change.

  $ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  Thanks and best regards,

  
  Alexander Deruwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1919146/+subscriptions

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


[Desktop-packages] [Bug 1919146] Re: Dependency removed on chromium-browser

2021-03-17 Thread Alexander Deruwe
Thanks for the investigation Olivier.

In case it helps, I was very much in a hurry so I just installed
whatever other version of chromium-browser I found with apt which
happened to be 65.0.3325.181-0ubuntu1 and not the previous. That version
somehow had the dependency. Then I made the wrong assumption that it was
a recently added one.

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

Title:
  Dependency removed on chromium-browser

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  This morning we noticed that in the latest version of chromium-browser on 
18.04 (89.0.4389.82-0ubuntu0.18.04.1) the dependency on libx11-xcb1 was removed.
  This caused our use-case with chromium-browser to break.
  For now we install libx11-xcb1 separately, but this seems like a breaking 
change.

  $ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  Thanks and best regards,

  
  Alexander Deruwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1919146/+subscriptions

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


[Desktop-packages] [Bug 1918578] Re: Chromium Crashes When Triggering File Dialog

2021-03-17 Thread Olivier Tilloy
Huh, there's something wrong with the connections, all the plugs appear
to be disconnected. I don't think the app should even start in this
situation.

Can you try removing and re-installing the snap, then check whether the
"snap connections chromium" command lists plugs as being connected to
slots? At the very least the following plugs should be connected:

  chromium:browser-sandbox
  chromium:gnome-3-28-1804
  chromium:desktop
  chromium:network
  chromium:x11

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

Title:
  Chromium Crashes When Triggering File Dialog

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've installed Chromium via Snap. Chromium seems to crash any time it
  triggers a native file dialog. This can be replicated by doing "Save
  file as", "Save image as" or simply doing CTRL+O to open a local web
  page.

  I've launched it from the terminal to see if it has any prints. Here's
  what I've got *before* the crash:

  ```plain
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so
  /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so: 
cannot open shared object file: No such file or directory
  Failed to load module: 
/home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so
  Gtk-Message: 08:07:49.139: Failed to load module "appmenu-gtk-module"

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: /snap/chromium/1514
  /gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-
  ibus.so: cannot open shared object file: No such file or directory

  (chrome:6811): Gtk-WARNING **: 08:07:52.019: Loading IM context type
  'ibus' failed

  (chrome:6811): Gtk-WARNING **: 08:07:57.896: Could not load a pixbuf from 
icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  ```

  Here's what I've got *when* it crashed:

  ```plain
  Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/snap/chromium/1506/data-dir/icons/Adwaita/16x16/status/image-missing.png: 
Unable to load image-loading module: 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 
/snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so:
 cannot open shared object file: No such file or directory 
(gdk-pixbuf-error-quark, 5)
  Aborted (core dumped)
  ```

  What is the issue here? How can I resolve this?

  ***

  # Environment

   - Kubuntu 20.04.2
   - Chromium 89.0.4389.72 (Official Build) snap (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918578/+subscriptions

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


[Desktop-packages] [Bug 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490

2021-03-17 Thread Dan Streetman
> Kernel says: x [1266..5678], y [1162..4694]
> Touchpad sends: x [1266..5678], y [1161..4694] -^C

unless I'm reading that wrong, the kernel reports exactly the same range
as the touchpad sends, so there should be no need for the hwdb to carry
x/y values overridding the kernel-reported ranges

In upstream systemd, this commit was added for your system's touchpad:
https://github.com/systemd/systemd/commit/2ceefe45873d0265fb99bc5757593e5bbb2c732b

That commit is included in focal. If that isn't working right for you,
I'd suggest opening a merge request, or at least a bug, upstream so they
can review/accept any further changes, and if accepted we can consider
backporting the change.


** Changed in: libinput (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Incorrectly specified Touchpad size for Lenovo T490

Status in libinput package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The vertical sensitivity of the touchpad on my laptop Lenovo T490
  seemed significantly higher than the horizontal sensitivity. After
  doing some research I found out that the touchpad size is incorrectly
  listed by the kernel.

  Touchpad size listed by the kernel: 77x107mm
  The real size of the touchpad: 68x100mm

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Systemd version: 245.4-4ubuntu3.2

  Output from the touchpad-edge-detector:

  miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 
/dev/input/event5
  Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5
  Move one finger around the touchpad to detect the actual edges
  Kernel says:  x [1266..5678], y [1162..4694]
  Touchpad sends:   x [1266..5678], y [1161..4694] -^C

  Touchpad size as listed by the kernel: 77x107mm
  User-specified touchpad size: 68x100mm
  Calculated ranges: 4412/3533

  Suggested udev rule:
  # 
  evdev:name:SynPS/2 Synaptics 
TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:*
   EVDEV_ABS_00=1266:5678:65
   EVDEV_ABS_01=1161:4694:35
   EVDEV_ABS_35=1266:5678:65
   EVDEV_ABS_36=1161:4694:35

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

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


[Desktop-packages] [Bug 1919146] Re: Dependency removed on chromium-browser

2021-03-17 Thread Olivier Tilloy
I think this might have been caused by this upstream change:
https://chromium.googlesource.com/chromium/src/+/b43825d5319658f1f01b2b487d8c453c582175db,
which dlopens libX11-xcb.so.1.

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

Title:
  Dependency removed on chromium-browser

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  This morning we noticed that in the latest version of chromium-browser on 
18.04 (89.0.4389.82-0ubuntu0.18.04.1) the dependency on libx11-xcb1 was removed.
  This caused our use-case with chromium-browser to break.
  For now we install libx11-xcb1 separately, but this seems like a breaking 
change.

  $ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  Thanks and best regards,

  
  Alexander Deruwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1919146/+subscriptions

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


[Desktop-packages] [Bug 1919146] Re: Dependency removed on chromium-browser

2021-03-17 Thread Olivier Tilloy
I can confirm the problem: in a bionic chroot, I install chromium-
browser and make sure libx11-xcb1 isn't installed (in a minimal chroot
without a desktop environment it isn't), then I start chromium in
headless mode and this is what I'm seeing:

$ chromium-browser --headless http://example.org
[0317/172148.363045:WARNING:headless_content_main_delegate.cc(530)] Cannot 
create Pref Service with no user data dir.
[0317/172148.365133:ERROR:bus.cc(393)] Failed to connect to the bus: Failed 
to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0317/172148.516024:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 1 time(s)
[0317/172148.94:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 2 time(s)
[0317/172148.821606:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 3 time(s)
[0317/172148.978707:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 4 time(s)
[0317/172149.134791:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 5 time(s)
[0317/172149.288921:WARNING:gpu_process_host.cc(1282)] The GPU process has 
crashed 6 time(s)
[0317/172149.292690:WARNING:gpu_process_host.cc(1002)] Reinitialized the 
GPU process after a crash. The reported initialization time was 0 ms

and the chromium process never returns.

After installing libx11-xcb1, this is what I'm seeing:

$ chromium-browser --headless http://example.org
[0317/172211.239945:WARNING:headless_content_main_delegate.cc(530)] Cannot 
create Pref Service with no user data dir.
[0317/172211.242524:ERROR:bus.cc(393)] Failed to connect to the bus: Failed 
to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

and the process exits successfully. If I add the --dump-dom parameter I
can confirm that the page that was requested was correctly fetched and
parsed.

Now the problem isn't that the dependency was removed, in fact chromium
88 didn't depend on libx11-xcb1 and I just confirmed in the same chroot
that it worked well in headless mode without it. It's the opposite
indeed: this is a new requirement, and I'm investigating to figure out
why the dependency wasn't automatically added.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

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

Title:
  Dependency removed on chromium-browser

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  This morning we noticed that in the latest version of chromium-browser on 
18.04 (89.0.4389.82-0ubuntu0.18.04.1) the dependency on libx11-xcb1 was removed.
  This caused our use-case with chromium-browser to break.
  For now we install libx11-xcb1 separately, but this seems like a breaking 
change.

  $ lsb_release -rd
  Description:Ubuntu 18.04.5 LTS
  Release:18.04

  Thanks and best regards,

  
  Alexander Deruwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1919146/+subscriptions

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


[Desktop-packages] [Bug 1919320] Re: Active Directory users unable to change expired password on logon

2021-03-17 Thread ibmthinkpad770x
advised by the bot to change the effected package

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

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

Title:
  Active Directory users unable to change expired password on logon

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I have Ubuntu 20.04 domain joined in a test-lab environment. The
  problem is even if a user is set to change their password upon logon
  via Windows active directory the user is never prompted to do so. I
  have tried multiple domain join methods with the same result including
  the official Ubuntu "Integration of Ubuntu Desktop with Microsoft
  Active Directory" white paper

  https://ubuntu.com/engage/microsoft-active-directory

  Using this SSSD and Realmd AD joined method the user is denied logon
  and receives a "Sorry, that did'nt work. Please try again" message.

  When using a Winbind and Samba joined AD system the user receives an
  "expired password" warning but is allowed to logon to the system
  without being forced to change the password.

  
  Below are the WinBind steps with comments on each step:

  #hostname rename

  #!/bin/bash
  echo Please enter new hostname
  read hostrename
  sudo hostnamectl set-hostname $hostrename &&
  sudo rm -f /etc/hosts
  sudo cat > /etc/hosts << EOF
  127.0.0.1 localhost
  127.0.1.1 $hostrename.TESTDOMAIN.INC $hostrename

  # The following lines are desirable for IPv6 capable hosts
  ::1 ip6-localhost ip6-loopback
  fe00::0 ip6-localnet
  ff00::0 ip6-mcastprefix
  ff02::1 ip6-allnodes
  ff02::2 ip6-allrouters

  EOF

  #install needed packages

  sudo apt-get install bind9-dnsutils &&
  sudo apt-get install ntpdate &&
  sudo apt-get install samba krb5-config krb5-user winbind libpam-winbind 
libnss-winbind &&

  #remove and create krb5.conf with specific variables
  sudo rm -f /etc/krb5.conf
  sudo cat > /etc/krb5.conf << EOF
  [libdefaults]
  default_realm = TESTDOMAIN.INC

  kdc_timesync = 1
  ccache_type = 4
  forwardable = true
  proxiable = true

  [realms]
  TESTDOMAIN.INC = {
  kdc = DC01.TESTDOMAIN.INC
  admin_server = DC01.TESTDOMAIN.INC
  }

  [domain_realm]
  TESTDOMAIN = TESTDOMAIN.INC
  .testdomain.inc = TESTDOMAIN.INC

  EOF

  #remove and create samba files with specific variables

  sudo rm -f /etc/samba/smb.conf &&
  sudo cat > /etc/samba/smb.conf << EOF
  [global]
  workgroup = TESTDOMAIN
  realm = TESTDOMAIN.INC
  security = ADS
  dns forwarder = 10.0.0.218
  winbind refresh tickets = Yes
  vfs objects = acl_xattr
  map acl inherit = Yes
  store dos attributes = Yes
  dedicated keytab file = /etc/krb5.keytab
  kerberos method = secrets and keytab
  idmap config * : backend = tdb
  idmap config *:range = 5-100
  template homedir = /home/%U
  template shell = /bin/bash
  winbind use default domain = true
  winbind offline logon = true
  winbind nss info = rfc2307
  winbind enum users = yes
  winbind enum groups = yes
  EOF
  break

  #restart services

  sudo systemctl restart winbind smbd nmbd

  #home directory enablement

  pam-auth-update --enable mkhomedir

  #nssswitch removal and modification to enable domain accounts

  sudo rm -f /etc/nsswitch.conf
  sudo cat > /etc/nsswitch.conf 

[Desktop-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12

2021-03-17 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 21.0.0-1

---
mesa (21.0.0-1) experimental; urgency=medium

  * New upstream release. (LP: #1917763)
  * control: Add directx-headers-dev to build-depends for amd64 and arm64
on Linux, which is what WSL2 currently supports.

 -- Timo Aaltonen   Mon, 15 Mar 2021 19:22:33 +0200

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFE: new upstream release 21.0 and migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's
  been in Debian experimental since rc1. The packaging also migrates it
  to use llvm 12.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before hirsute is
  frozen, and then push more as an SRU.

  I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too
  with some games, all good.

  packages for hirsute are available on ppa:canonical-x/x-staging

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

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


[Desktop-packages] [Bug 1919320] [NEW] Active Directory users unable to change expired password on logon

2021-03-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have Ubuntu 20.04 domain joined in a test-lab environment. The problem
is even if a user is set to change their password upon logon via Windows
active directory the user is never prompted to do so. I have tried
multiple domain join methods with the same result including the official
Ubuntu "Integration of Ubuntu Desktop with Microsoft Active Directory"
white paper

https://ubuntu.com/engage/microsoft-active-directory

Using this SSSD and Realmd AD joined method the user is denied logon and
receives a "Sorry, that did'nt work. Please try again" message.

When using a Winbind and Samba joined AD system the user receives an
"expired password" warning but is allowed to logon to the system without
being forced to change the password.


Below are the WinBind steps with comments on each step:

#hostname rename

#!/bin/bash
echo Please enter new hostname
read hostrename
sudo hostnamectl set-hostname $hostrename &&
sudo rm -f /etc/hosts
sudo cat > /etc/hosts << EOF
127.0.0.1 localhost
127.0.1.1 $hostrename.TESTDOMAIN.INC $hostrename

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

EOF

#install needed packages

sudo apt-get install bind9-dnsutils &&
sudo apt-get install ntpdate &&
sudo apt-get install samba krb5-config krb5-user winbind libpam-winbind 
libnss-winbind &&

#remove and create krb5.conf with specific variables
sudo rm -f /etc/krb5.conf
sudo cat > /etc/krb5.conf << EOF
[libdefaults]
default_realm = TESTDOMAIN.INC

kdc_timesync = 1
ccache_type = 4
forwardable = true
proxiable = true

[realms]
TESTDOMAIN.INC = {
kdc = DC01.TESTDOMAIN.INC
admin_server = DC01.TESTDOMAIN.INC
}

[domain_realm]
TESTDOMAIN = TESTDOMAIN.INC
.testdomain.inc = TESTDOMAIN.INC

EOF

#remove and create samba files with specific variables

sudo rm -f /etc/samba/smb.conf &&
sudo cat > /etc/samba/smb.conf << EOF
[global]
workgroup = TESTDOMAIN
realm = TESTDOMAIN.INC
security = ADS
dns forwarder = 10.0.0.218
winbind refresh tickets = Yes
vfs objects = acl_xattr
map acl inherit = Yes
store dos attributes = Yes
dedicated keytab file = /etc/krb5.keytab
kerberos method = secrets and keytab
idmap config * : backend = tdb
idmap config *:range = 5-100
template homedir = /home/%U
template shell = /bin/bash
winbind use default domain = true
winbind offline logon = true
winbind nss info = rfc2307
winbind enum users = yes
winbind enum groups = yes
EOF
break

#restart services

sudo systemctl restart winbind smbd nmbd

#home directory enablement

pam-auth-update --enable mkhomedir

#nssswitch removal and modification to enable domain accounts

sudo rm -f /etc/nsswitch.conf
sudo cat > /etc/nsswitch.conf 

[Desktop-packages] [Bug 1919358] Re: changes display settings on startup when 2 screens

2021-03-17 Thread Olivier Tilloy
Just launching the chromium snap triggers this setting change?
Can you reliably reproduce the problem after reverting the setting back to its 
original value?

If so, could you please attach a screencast demonstrating the problem?
Thanks!

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

** Summary changed:

- changes display settings on startup when 2 screens
+ [snap] changes display settings on startup when 2 screens

** Tags added: snap

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

Title:
  [snap] changes display settings on startup when 2 screens

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  when starting chromium 89.0.4389.90 (Official Build) snap (64-bit) on ubuntu 
18.04.5 LTS, the display settings for my 2 screens is changed.
  For example from Joint Display to Single Display, or just something else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1919358/+subscriptions

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


[Desktop-packages] [Bug 1874120] Re: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

2021-03-17 Thread Olivier Tilloy
Priscila, this is a different problem altogether. It appears you are
running Ubuntu 20.04 (focal) and trying to install chromium-browser for
18.04 (bionic). This isn't supported.

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

Title:
  package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  error appeared when opening chrome

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI=
   modes: 1920x1080
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Tue Apr 21 23:33:33 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-03-28 (1851 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Load-Avg-1min: 3.38
  Load-Processes-Running-Percent:   0.2%
  MachineType: ASUSTeK COMPUTER INC. ET2221I-B85
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago)
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2221I-B85
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: All-In-One
  dmi.product.name: ET2221I-B85
  dmi.product.version: 0503
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874120/+subscriptions

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


[Desktop-packages] [Bug 1874120] Re: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

2021-03-17 Thread Priscila Tavares Figueredo
O meu aparece isso :

chromium-browser: Depends: libgcc1 (>= 1:3.0) mas a 1:10.2.0-5ubuntu1~20.04 
está instalada
  Depends: libnspr4 (>= 2:4.9-2~) mas a 2:4.25-1 está instalada
  Depends: libnss3 (>= 2:3.22) mas a 2:3.49.1-1ubuntu1.5 está 
instalada
  Depends: libx11-6 (>= 2:1.4.99.1) mas a 2:1.6.9-2ubuntu1.1 
está instalada
  Depends: libxcomposite1 (>= 1:0.3-1) mas a 1:0.4.5-1 está 
instalada
  Depends: libxdamage1 (>= 1:1.1) mas a 1:1.1.5-2 está instalada
  Depends: chromium-codecs-ffmpeg (= 
89.0.4389.82-0ubuntu0.18.04.1) mas não está instalado
chromium-browser-l10n: Depends: chromium-browser (>= 
1:85.0.4183.83-0ubuntu0.20.04.2) mas a 89.0.4389.82-0ubuntu0.18.04.1 está 
instalada

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

Title:
  package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  error appeared when opening chrome

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI=
   modes: 1920x1080
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Tue Apr 21 23:33:33 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-03-28 (1851 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Load-Avg-1min: 3.38
  Load-Processes-Running-Percent:   0.2%
  MachineType: ASUSTeK COMPUTER INC. ET2221I-B85
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago)
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2221I-B85
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: All-In-One
  dmi.product.name: ET2221I-B85
  dmi.product.version: 0503
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874120/+subscriptions

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


[Desktop-packages] [Bug 1919476] [NEW] Document Viewer window overlaps ubuntu-dock

2021-03-17 Thread corrado venturini
Public bug reported:

I maximized the Document Viewer window which was minimized and the window 
overlaps the ubuntu-dock.
see attached image

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 17 16:39:50 2021
InstallationDate: Installed on 2021-02-28 (16 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
PackageArchitecture: all
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 hirsute wayland-session

** Attachment added: "Screenshot from 2021-03-17 15-50-59.png"
   
https://bugs.launchpad.net/bugs/1919476/+attachment/5477593/+files/Screenshot%20from%202021-03-17%2015-50-59.png

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

Title:
  Document Viewer window overlaps ubuntu-dock

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

Bug description:
  I maximized the Document Viewer window which was minimized and the window 
overlaps the ubuntu-dock.
  see attached image

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 16:39:50 2021
  InstallationDate: Installed on 2021-02-28 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  PackageArchitecture: all
  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/1919476/+subscriptions

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


[Desktop-packages] [Bug 1577198] Re: Imported gpg keys do not show up in Seahorse 3.18.0

2021-03-17 Thread Ro
Confirmed that on Ubuntu 20.04, neither private nor public GPG keys
exported by Seahorse on Ubuntu 18.04 show up, regardless of a restart.

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

Title:
  Imported gpg keys do not show up in Seahorse 3.18.0

Status in seahorse:
  New
Status in seahorse package in Ubuntu:
  Triaged

Bug description:
  After clean install of Ubuntu-Gnome 16.04 LTS I tried to import all my
  previous exported gpg keys. Although it seems the keys are imported,
  they do not show up in seahorse (Passwords and Keys). Also Evolution
  did not find to proper keys to decrypt messages.

  It seems however that the keys have been imported under gpg1 in stead
  of gpg2. This can also be confirmed with the list command (gpg --list-
  key and gpg2 -- list-keys).

  Importing all keys by command (gpg2 --import Multiple_Keys.asc) seems
  to work.

  See also the same problem already reported by Andreas Happe on:
  https://www.snikt.net/blog/2016/02/27/evolution-seahorse-gpg-gpg2-woes/

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

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


[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-03-17 Thread Olivier Tilloy
** Changed in: thunderbird (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: jsunit (Ubuntu Bionic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: jsunit (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in enigmail package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in jsunit source package in Bionic:
  In Progress
Status in thunderbird source package in Bionic:
  In Progress
Status in enigmail source package in Focal:
  Fix Released
Status in jsunit source package in Focal:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in tinyjsd source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

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

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


[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2021-03-17 Thread Alexander Fedulov
I can confirm the same behaviour on nvidia-450.120.04-0ubuntu0.18.04.1
with Linux Mint (Cinnamon).

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions

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


[Desktop-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10

2021-03-17 Thread Mark Fraser
*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965

** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  IntelHD audio not detected after upgrading to Ubuntu 20.10

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

Bug description:
  After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn
  my computer on the sound card doesn't work. If I load Pulse Audio
  Volume Control and disable and then re-enable the audio controller
  (Family 17h (Models 00h-0fh) HD Audio Controller it will work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Nov 30 15:19:50 2020
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  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.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4: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.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-29-generic N/A
   linux-backports-modules-5.8.0-29-generic  N/A
   linux-firmware1.190.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  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.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4: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.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

2021-03-17 Thread Simon
Ubuntu 20.04 still has this bug with mutter 3.36.7+git20201123-0.20.04.1 amd64 
and nvidia-340.
The workaround to set the wallpaper resolution to the screen resolution does 
work though! Thanx for that!

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

2021-03-17 Thread Launchpad Bug Tracker
This bug was fixed in the package ubiquity - 21.04.11

---
ubiquity (21.04.11) hirsute; urgency=medium

  [ Didier Roche ]
  [ Jean-Baptiste Lallement ]
  * Configure krb5 client so access to AD with GPO enabled works out of the
box after installation.
  * Keep packages required for AD installed. When AD installation is selected
we want to keep all the packages used to make it work and remove them
otherwise.

  [ Dimitri John Ledkov ]
  * install_misc: refuse to install packages that have been marked for removal.
This should generally fix issues we've been seeing with installations using
the OEM metapackages.  (LP: #1914374)
  * Merge netcfg 171 from Debian into ~ubuntu-installer repo, and subtree
pull it in.
  * Automatic update of included source packages: netcfg 171ubuntu1
  * Build udebs with !noudeb profile set, to actually build with udebs.
  * Delete KeyboardNames.pl becuase it is annoying.
  * Automatic update of included source packages.
  * Properly drop dh-systemd build-dep from the d-i/update-control script.
  * Add symlink in netcfg mock_paths with and without _fn suffix, cause
check in hirsute-release & hirsute-proposed want one or the other.

 -- Dimitri John Ledkov   Wed, 17 Mar 2021 02:22:11
+

** Changed in: ubiquity (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubiquity source package in Groovy:
  Won't Fix
Status in ubuntu-drivers-common source package in Groovy:
  Won't Fix

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions

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


[Desktop-packages] [Bug 1919440] Re: Mouse cursor gets stuck in "drag and drop" mode

2021-03-17 Thread Sebastien Bacher
Thank you for your bug report, could you take a screencast or video
showing the issue?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
Mouse cursor gets stuck in "drag and drop" mode

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.2 LTS

  3) I just expect to open a folder in my files.

  4)
  This only happens when I try to open specific folders. 
  First I open the files menu. 
  Then I click on one of my 'saved favorites' on the left side in the displayed 
vertical list. they are between 'trash' and 'other locations'. 
  Whenever I click on these directories, which I put there to have fast access 
to them, the cursor just makes a drag and drop. So I cannot really use them 
anymore.
  Only happens to these folders I put there, does not happen when I click on 
home or downloads etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 10:44:17 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'161'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(893, 411)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
  InstallationDate: Installed on 2020-07-10 (249 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1919440] [NEW] Mouse cursor gets stuck in "drag and drop" mode

2021-03-17 Thread Konstantin Hebenstreit
Public bug reported:

1) Ubuntu 20.04.2 LTS

3) I just expect to open a folder in my files.

4)
This only happens when I try to open specific folders. 
First I open the files menu. 
Then I click on one of my 'saved favorites' on the left side in the displayed 
vertical list. they are between 'trash' and 'other locations'. 
Whenever I click on these directories, which I put there to have fast access to 
them, the cursor just makes a drag and drop. So I cannot really use them 
anymore.
Only happens to these folders I put there, does not happen when I click on home 
or downloads etc.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 17 10:44:17 2021
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'161'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(893, 411)'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
InstallationDate: Installed on 2020-07-10 (249 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

Title:
Mouse cursor gets stuck in "drag and drop" mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  1) Ubuntu 20.04.2 LTS

  3) I just expect to open a folder in my files.

  4)
  This only happens when I try to open specific folders. 
  First I open the files menu. 
  Then I click on one of my 'saved favorites' on the left side in the displayed 
vertical list. they are between 'trash' and 'other locations'. 
  Whenever I click on these directories, which I put there to have fast access 
to them, the cursor just makes a drag and drop. So I cannot really use them 
anymore.
  Only happens to these folders I put there, does not happen when I click on 
home or downloads etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 10:44:17 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'161'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(893, 411)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
  InstallationDate: Installed on 2020-07-10 (249 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1919425] Re: System freeze

2021-03-17 Thread Daniel van Vugt
** Summary changed:

- Xorg freeze
+ System freeze

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

** Package changed: linux (Ubuntu) => linux-oem-5.6 (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/1919425

Title:
  System freeze

Status in linux-oem-5.6 package in Ubuntu:
  New

Bug description:
  I've been getting freezes on Ubuntu 20.04 on my Dell Latitude 7420
  laptop with a secondary display connected through a WD19 Dell dock.
  I'm on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8
  and 5.10 without much success (other types of freezes). Some freezes
  lock up the machine hard with no way to ssh in or check anything and
  no logs. The one below I was able to ssh in and dump dmesg, rebooting
  via ssh froze and I had to do a hard reboot.

  [ 7557.306199] BUG: unable to handle page fault for address: 8ceca8900758
  [ 7557.306206] #PF: supervisor write access in kernel mode
  [ 7557.306209] #PF: error_code(0x0002) - not-present page
  [ 7557.306211] PGD 39601067 P4D 39601067 PUD 0
  [ 7557.306217] Oops: 0002 [#1] SMP NOPTI
  [ 7557.306221] CPU: 4 PID: 6181 Comm: chrome Tainted: GW  O  
5.6.0-1048-oem #52-Ubuntu
  [ 7557.306223] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 
01/18/2021
  [ 7557.306231] RIP: 0010:remove_wait_queue+0x25/0x50
  [ 7557.306235] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc 
53 48 89 f3 e8 f9 e2 a1 00 48 8b 53 18 4c 89 e7 48 89 c6 48 8b 43 20 <48> 89 42 
08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 43 18 48
  [ 7557.306237] RSP: 0018:b14e015cba78 EFLAGS: 00010046
  [ 7557.306240] RAX: 8caca8900750 RBX: b14e015cbc80 RCX: 
0001
  [ 7557.306242] RDX: 8ceca8900750 RSI: 0282 RDI: 
8caca8900748
  [ 7557.306244] RBP: b14e015cba88 R08: 8cac52a2c000 R09: 
0003
  [ 7557.306245] R10: 0084 R11: fffb159a R12: 
8caca8900748
  [ 7557.306247] R13:  R14: b14e015cbc70 R15: 
0001
  [ 7557.306250] FS:  7f137ff04d80() GS:8cacaf70() 
knlGS:
  [ 7557.306252] CS:  0010 DS:  ES:  CR0: 80050033
  [ 7557.306254] CR2: 8ceca8900758 CR3: 0007ee554005 CR4: 
00760ee0
  [ 7557.306255] PKRU: 5554
  [ 7557.306257] Call Trace:
  [ 7557.306265]  poll_freewait+0x42/0xa0
  [ 7557.306268]  do_sys_poll+0x480/0x520
  [ 7557.306275]  ? poll_select_finish+0x210/0x210
  [ 7557.306278]  ? poll_select_finish+0x210/0x210
  [ 7557.306282]  ? poll_select_finish+0x210/0x210
  [ 7557.306284]  ? poll_select_finish+0x210/0x210
  [ 7557.306287]  ? poll_select_finish+0x210/0x210
  [ 7557.306292]  ? fput+0x13/0x15
  [ 7557.306296]  ? __sys_sendto+0x153/0x190
  [ 7557.306300]  ? __fget_light+0x62/0x80
  [ 7557.306303]  ? fput+0x13/0x15
  [ 7557.306306]  ? __sys_recvmsg+0x88/0xa0
  [ 7557.306310]  ? ktime_get_ts64+0x4c/0xe0
  [ 7557.306313]  __x64_sys_poll+0xa5/0x140
  [ 7557.306319]  do_syscall_64+0x57/0x1b0
  [ 7557.306324]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 7557.306328] RIP: 0033:0x7f1381360aff
  [ 7557.306330] Code: 54 24 1c 48 89 74 24 10 48 89 7c 24 08 e8 79 1c f8 ff 8b 
54 24 1c 48 8b 74 24 10 41 89 c0 48 8b 7c 24 08 b8 07 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2b 44 89 c7 89 44 24 08 e8 ad 1c f8 ff 8b 44
  [ 7557.306332] RSP: 002b:7fff0cd693d0 EFLAGS: 0293 ORIG_RAX: 
0007
  [ 7557.306335] RAX: ffda RBX: 7f13828e60d0 RCX: 
7f1381360aff
  [ 7557.306336] RDX: 0ea1 RSI: 0005 RDI: 
377ea82ca210
  [ 7557.306338] RBP: 377ea82ca210 R08:  R09: 
0001
  [ 7557.306339] R10: 377ea8b40460 R11: 0293 R12: 
0005
  [ 7557.306341] R13: 7fff0cd69414 R14: 0ea1 R15: 
377ea6d9bd10
  [ 7557.306346] Modules linked in: rfcomm vboxnetadp(O) vboxnetflt(O) 
vboxdrv(O) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda 
snd_sof snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek 
snd_hda_codec_generic snd_soc_acpi dell_laptop mei_hdcp intel_rapl_msr 
ledtrig_audio snd_hda_intel snd_intel_dspcfg x86_pkg_temp_thermal 
intel_powerclamp soundwire_intel soundwire_generic_allocation coretemp 
soundwire_cadence snd_hda_codec kvm_intel kvm snd_hda_core soundwire_bus 
dell_wmi intel_cstate snd_soc_core snd_compress dell_smbios ac97_bus serio_raw 
snd_pcm_dmaengine dcdbas snd_usb_audio dell_wmi_descriptor snd_usbmidi_lib 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event wmi_bmof uvcvideo snd_rawmidi 
videobuf2_vmalloc snd_seq videobuf2_memops snd_seq_device snd_timer 
videobuf2_v4l2 joydev btusb cdc_ether snd input_leds videobuf2_common
  [ 7557.306386]  btrtl usbnet 

[Desktop-packages] [Bug 1913940] Re: Wifi keeps disconnecting and reconnecting all the time

2021-03-17 Thread Adrian
Hi, any sign that this issue is being looked at?

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

Title:
  Wifi keeps disconnecting and reconnecting all the time

Status in wpa package in Ubuntu:
  New

Bug description:
  I have a problem with WIFI not being stable, and disconnecting ->
  reconnecting, all the time (I have PC next to the router). It happens
  like every 10 seconds average (one time it happened twice in a row,
  and another time I got 30 seconds without disconnect).

  Specs:
  OS: Ubuntu 20.04.1 LTS (On 20.10 same issue)
  Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k)
  Motherboard: MSI X470 Gaming Plus Max
  CPU: AMD Ryzen 5 3600
  wpasupplicant: 2:2.9-1ubuntu4.1

  I've tried so far: disabling IPV6, disabling powersave mode, creating
  ath9k.conf and adding parameters, setting manually BSSID and MAC
  adress, installing backport-iwlwifi-dkms, installing firmware-ath9k-
  htc, using 2,4G network.

  What I expect:
  Wifi network stable without single drop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 12:09:00 2021
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-17 Thread Sebastien Bacher
Yes, as it's a security update it probably got autoinstalled. Do you
still get the issue? Could you attach an example of problematic file to
the bug?

The dpkg -s command you are using is invalid, the argument is a package
name not a version, so it would be

$ dpkg -s libgnome-autoar-0-0

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1919008/+subscriptions

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


[Desktop-packages] [Bug 1919425] [NEW] Xorg freeze

2021-03-17 Thread kailoran
Public bug reported:

I've been getting freezes on Ubunyu 20.04 on my Dell Latitude 7420
laptop with a secondary display connected through a WD19 Dell dock. I'm
on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8 and
5.10 without much success (other types of freezes). Some freezes lock up
the machine hard with no way to ssh in or check anything and no logs.
The one below I was able to ssh in and dump dmesg, rebooting via ssh
froze and I had to do a hard reboot.

[ 7557.306199] BUG: unable to handle page fault for address: 8ceca8900758
[ 7557.306206] #PF: supervisor write access in kernel mode
[ 7557.306209] #PF: error_code(0x0002) - not-present page
[ 7557.306211] PGD 39601067 P4D 39601067 PUD 0 
[ 7557.306217] Oops: 0002 [#1] SMP NOPTI
[ 7557.306221] CPU: 4 PID: 6181 Comm: chrome Tainted: GW  O  
5.6.0-1048-oem #52-Ubuntu
[ 7557.306223] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 
01/18/2021
[ 7557.306231] RIP: 0010:remove_wait_queue+0x25/0x50
[ 7557.306235] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc 
53 48 89 f3 e8 f9 e2 a1 00 48 8b 53 18 4c 89 e7 48 89 c6 48 8b 43 20 <48> 89 42 
08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 43 18 48
[ 7557.306237] RSP: 0018:b14e015cba78 EFLAGS: 00010046
[ 7557.306240] RAX: 8caca8900750 RBX: b14e015cbc80 RCX: 0001
[ 7557.306242] RDX: 8ceca8900750 RSI: 0282 RDI: 8caca8900748
[ 7557.306244] RBP: b14e015cba88 R08: 8cac52a2c000 R09: 0003
[ 7557.306245] R10: 0084 R11: fffb159a R12: 8caca8900748
[ 7557.306247] R13:  R14: b14e015cbc70 R15: 0001
[ 7557.306250] FS:  7f137ff04d80() GS:8cacaf70() 
knlGS:
[ 7557.306252] CS:  0010 DS:  ES:  CR0: 80050033
[ 7557.306254] CR2: 8ceca8900758 CR3: 0007ee554005 CR4: 00760ee0
[ 7557.306255] PKRU: 5554
[ 7557.306257] Call Trace:
[ 7557.306265]  poll_freewait+0x42/0xa0
[ 7557.306268]  do_sys_poll+0x480/0x520
[ 7557.306275]  ? poll_select_finish+0x210/0x210
[ 7557.306278]  ? poll_select_finish+0x210/0x210
[ 7557.306282]  ? poll_select_finish+0x210/0x210
[ 7557.306284]  ? poll_select_finish+0x210/0x210
[ 7557.306287]  ? poll_select_finish+0x210/0x210
[ 7557.306292]  ? fput+0x13/0x15
[ 7557.306296]  ? __sys_sendto+0x153/0x190
[ 7557.306300]  ? __fget_light+0x62/0x80
[ 7557.306303]  ? fput+0x13/0x15
[ 7557.306306]  ? __sys_recvmsg+0x88/0xa0
[ 7557.306310]  ? ktime_get_ts64+0x4c/0xe0
[ 7557.306313]  __x64_sys_poll+0xa5/0x140
[ 7557.306319]  do_syscall_64+0x57/0x1b0
[ 7557.306324]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 7557.306328] RIP: 0033:0x7f1381360aff
[ 7557.306330] Code: 54 24 1c 48 89 74 24 10 48 89 7c 24 08 e8 79 1c f8 ff 8b 
54 24 1c 48 8b 74 24 10 41 89 c0 48 8b 7c 24 08 b8 07 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2b 44 89 c7 89 44 24 08 e8 ad 1c f8 ff 8b 44
[ 7557.306332] RSP: 002b:7fff0cd693d0 EFLAGS: 0293 ORIG_RAX: 
0007
[ 7557.306335] RAX: ffda RBX: 7f13828e60d0 RCX: 7f1381360aff
[ 7557.306336] RDX: 0ea1 RSI: 0005 RDI: 377ea82ca210
[ 7557.306338] RBP: 377ea82ca210 R08:  R09: 0001
[ 7557.306339] R10: 377ea8b40460 R11: 0293 R12: 0005
[ 7557.306341] R13: 7fff0cd69414 R14: 0ea1 R15: 377ea6d9bd10
[ 7557.306346] Modules linked in: rfcomm vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc 
nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common 
snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core 
snd_soc_acpi_intel_match snd_hda_codec_realtek snd_hda_codec_generic 
snd_soc_acpi dell_laptop mei_hdcp intel_rapl_msr ledtrig_audio snd_hda_intel 
snd_intel_dspcfg x86_pkg_temp_thermal intel_powerclamp soundwire_intel 
soundwire_generic_allocation coretemp soundwire_cadence snd_hda_codec kvm_intel 
kvm snd_hda_core soundwire_bus dell_wmi intel_cstate snd_soc_core snd_compress 
dell_smbios ac97_bus serio_raw snd_pcm_dmaengine dcdbas snd_usb_audio 
dell_wmi_descriptor snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event wmi_bmof uvcvideo snd_rawmidi videobuf2_vmalloc snd_seq 
videobuf2_memops snd_seq_device snd_timer videobuf2_v4l2 joydev btusb cdc_ether 
snd input_leds videobuf2_common
[ 7557.306386]  btrtl usbnet soundcore btbcm iwlmvm videodev btintel mac80211 
r8152 mc libarc4 mii bluetooth ecdh_generic ecc iwlwifi hid_sensor_accel_3d 
hid_sensor_gyro_3d hid_sensor_als hid_sensor_trigger cfg80211 
industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common 
industrialio ucsi_acpi mei hid_multitouch processor_thermal_device 
intel_rapl_common cros_ec_ishtp typec_ucsi cros_ec intel_soc_dts_iosf typec 
soc_button_array int3403_thermal int340x_thermal_zone mac_hid int3400_thermal 
acpi_tad acpi_thermal_rel acpi_pad 

[Desktop-packages] [Bug 1919407] Re: display bug, incorrect resolution

2021-03-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1919285 ***
https://bugs.launchpad.net/bugs/1919285

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 1919285, 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 1919285
   Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51

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

Title:
  display bug, incorrect resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  I made a total reinstallation of ubuntu 20.04 thinking that this would solve 
the problem, but it came back as soon as I applied all the updates.
  I, then reinstalled again but with ubuntu 20.10 and the problem is still 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 01:20:20 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2872]
  InstallationDate: Installed on 2021-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=158e70e5-f39d-43c5-9e14-1af532a5b9ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1919407/+subscriptions

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


[Desktop-packages] [Bug 1919412] Re: display, resolution bug

2021-03-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1919285 ***
https://bugs.launchpad.net/bugs/1919285

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 1919285, 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 1919285
   Nvidia resolution is stuck at 640x480 or 800x600 since kernel 5.8.0-45.51

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

Title:
  display, resolution bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Since last update the screen resolution is as it it was without
  graphic acceleration

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 02:25:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2872]
  InstallationDate: Installed on 2021-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=9215bf81-3d3a-4dd5-9a7c-acc1e8bf480e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1919407] Re: display bug, incorrect resolution

2021-03-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  display bug, incorrect resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  I made a total reinstallation of ubuntu 20.04 thinking that this would solve 
the problem, but it came back as soon as I applied all the updates.
  I, then reinstalled again but with ubuntu 20.10 and the problem is still 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 01:20:20 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2872]
  InstallationDate: Installed on 2021-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=158e70e5-f39d-43c5-9e14-1af532a5b9ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1919407/+subscriptions

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


[Desktop-packages] [Bug 1919412] Re: display, resolution bug

2021-03-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  display, resolution bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Since last update the screen resolution is as it it was without
  graphic acceleration

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 17 02:25:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2872]
  InstallationDate: Installed on 2021-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=9215bf81-3d3a-4dd5-9a7c-acc1e8bf480e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1919407] [NEW] display bug, incorrect resolution

2021-03-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I made a total reinstallation of ubuntu 20.04 thinking that this would solve 
the problem, but it came back as soon as I applied all the updates.
I, then reinstalled again but with ubuntu 20.10 and the problem is still there.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 17 01:20:20 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] 
[1462:2872]
InstallationDate: Installed on 2021-03-17 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=158e70e5-f39d-43c5-9e14-1af532a5b9ae ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4601
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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 groovy resolution ubuntu
-- 
display bug, incorrect resolution
https://bugs.launchpad.net/bugs/1919407
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 1919412] [NEW] display, resolution bug

2021-03-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since last update the screen resolution is as it it was without graphic
acceleration

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 17 02:25:27 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] 
[1462:2872]
InstallationDate: Installed on 2021-03-17 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=9215bf81-3d3a-4dd5-9a7c-acc1e8bf480e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4601
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4601:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXPLUS:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu
-- 
display, resolution bug
https://bugs.launchpad.net/bugs/1919412
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 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-17 Thread Jalansh Munshi
Here it is -

ii  libgnome-autoar-0-0:amd64  0.2.3-2ubuntu0.2
amd64Archives integration support for GNOME

Does this mean it is already installed? I executed 'dpkg -s
0.2.3-2ubuntu0.2 | grep version' yesterday and it said - "dpkg-query:
package '0.2.3-2ubuntu0.2' is not installed and no information is
available"

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1919008/+subscriptions

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


[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-17 Thread Christian Ehrhardt 
open-vm-tools fixed in

open-vm-tools (2:11.2.5-2ubuntu1) hirsute; urgency=medium   
 

  
   * d/p/fix-FTFBS-glib2.0-2.66.3.patch: fix FTBFS with glib2.0 >=2.66.3 

-- Christian Ehrhardt   Mon, 08 Mar
2021 12:12:35 +0100


** Changed in: open-vm-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged
Status in wireshark package in Ubuntu:
  Fix Released

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It must be something else.

  The difference were ~340 packages I was upgrading them to spot what broke it.
  I eventually found glib 2.66 -> 2.67 to break it.

  libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable 

[Desktop-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

2021-03-17 Thread Daniel van Vugt
** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #119
   https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/119

** Also affects: gnome-shell-extension-desktop-icons-ng via
   https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/119
   Importance: Unknown
   Status: Unknown

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Triaged

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions

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


[Desktop-packages] [Bug 1919408] Re: Xorg freeze

2021-03-17 Thread Daniel van Vugt
Thanks for the bug report.

Firstly, you seem to have an AMD Radeon GPU, but the Nvidia driver is
installed. Please uninstall the Nvidia driver in case that is causing
problems.

Secondly, next time a crash happens please:

  1. Wait 10 seconds
  2. Reboot
  3. Run this command:  journalctl -b-1 > prevboot.txt
  4. Attach the resulting text file here.

Finally, please check the system for crashes by following all of the
steps listed in:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** Changed in: 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/1919408

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  After copied (dd copy) old disk /home to bigger one then  reboot xorg start 
to freeze it seems kernel crash rather than only Xorg, because all input 
devices (keyboard, mouse) turned off completely. only option is hard reboot.
  I upgrade distro from 20.04 to 20.10, the situation remain the same after 
every login to desktop the system freeze completely and need it to do hard 
reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18
  Uname: Linux 5.8.0-45-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Wed Mar 17 01:11:19 2021
  DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit()
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570]
  InstallationDate: Installed on 2018-05-05 (1046 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency 
root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=512M-:192M
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1708:bd04/10/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx: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: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: