from:"pierre"

[Desktop-packages] [Bug 2053296] Re: UnboundLocalError Python error when running `ubuntu-drivers autoinstall`

2024-02-15 Thread Pierre Equoy

This looks very similar to lp:1995158, but I wanted to complete the
`ubuntu-bug` process in order to capture the logs for that machine.

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

Title:
  UnboundLocalError Python error when running `ubuntu-drivers
  autoinstall`

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  As part of the Certification regression testing process, we
  automatically provision devices in our Certification lab with
  different versions of Ubuntu to make sure no regressions are
  introduced during the SRU process.

  Recently, we got an issue when trying to provision Ubuntu 22.04 on a
  device with a Nvidia GPU. The Nvidia drivers should be installed with
  the ubuntu-drivers autoinstall command, however when run, the
  following exception is thrown:

  ubuntu@10.102.163.75 sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.1/:01:00.0 ==
  modalias : pci:v10DEd2571sv103Csd1611bc03sc00i00
  vendor   : NVIDIA Corporation
  driver   : nvidia-driver-525-open - distro non-free
  driver   : nvidia-driver-470-server - distro non-free
  driver   : nvidia-driver-535-server-open - distro non-free
  driver   : nvidia-driver-535 - distro non-free
  driver   : nvidia-driver-545-open - distro non-free recommended
  driver   : nvidia-driver-535-server - distro non-free
  driver   : nvidia-driver-470 - distro non-free
  driver   : nvidia-driver-535-open - distro non-free
  driver   : nvidia-driver-525-server - distro non-free
  driver   : nvidia-driver-545 - distro non-free
  driver   : nvidia-driver-525 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  == /sys/devices/pci:00/:00:1f.4 ==
  modalias : pci:v8086d7AA3sv103Csd895Ebc0Csc05i00
  vendor   : Intel Corporation
  driver   : oem-stella-asobo-meta - distro free

  + _run sudo ubuntu-drivers autoinstall
  + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.163.75 sudo ubuntu-drivers autoinstall
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-drivers-common 1:0.9.6.2~0.22.04.6
  ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
  Uname: Linux 5.15.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
  Date: Thu Feb 15 21:53:15 2024
  InstallationDate: Installed on 2022-05-10 (646 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2053296/+subscriptions


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

[Desktop-packages] [Bug 1995158] Re: "ubuntu-drivers autoinstall" fails with Python UnboundLocaError

2024-02-15 Thread Pierre Equoy

** Tags added: cert-sru

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

Title:
  "ubuntu-drivers autoinstall" fails with Python UnboundLocaError

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  I'm having problems with an external monitor on my laptop, so I wanted
  to update the NVIDA drivers.

  I first tried this in the "Additional Drivers" tab of "Software &
  Updates". I selected a newer driver, clicked "Apply Changes", and
  entered my password to install updates. This showed a progress bar and
  seemed to be working, but after a few seconds I got a blank error
  dialogue, with only an X button. I tried a few other driver versions
  with the same result.

  Next, I tried running `ubuntu-drivers autoinstall` from the command
  line. I expected this would install some drivers. Instead, I got this
  error trace:

  ```
  $ sudo ubuntu-drivers autoinstall
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment
  ```

  
  Looking at the code I believe the 'finally' block is trying to use the 
'version' variable set in the `try`, which can only work if the try succeeds. 
Seeing this, I modified the script to set a default value for 'version':

  ```
  *** /home/edward/detect.py.original   2022-10-29 15:40:49.515765835 +1100
  --- /home/edward/detect.py.fixed  2022-10-29 15:39:55.383555776 +1100
  ***
  *** 828,839 
  --- 828,840 
'''Applies changes that need to happen before installing the NVIDIA 
drivers'''
with_nvidia_kms = False

# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
  + version = -1
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
  ```

  With this change `ubuntu-drivers autoinstall` ran successfully and
  installed a bunch of packages. I can now see in Software & Updates
  that I am updated to the latest NVIDIA driver versions. (However my
  monitor isn't working yet so there may be another underlying issue.)

  
  

  Version information:

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
   *** 1:0.9.6.1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-drivers-common 1:0.9.6.1 [modified: 
usr/lib/python3/dist-packages/UbuntuDrivers/detect.py]
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 15:31:57 2022
  InstallationDate: Installed on 2021-04-01 (575 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1995158/+subscriptions


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

[Desktop-packages] [Bug 2053296] [NEW] UnboundLocalError Python error when running `ubuntu-drivers autoinstall`

2024-02-15 Thread Pierre Equoy

Public bug reported:

As part of the Certification regression testing process, we
automatically provision devices in our Certification lab with different
versions of Ubuntu to make sure no regressions are introduced during the
SRU process.

Recently, we got an issue when trying to provision Ubuntu 22.04 on a
device with a Nvidia GPU. The Nvidia drivers should be installed with
the ubuntu-drivers autoinstall command, however when run, the following
exception is thrown:

ubuntu@10.102.163.75 sudo ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.1/:01:00.0 ==
modalias : pci:v10DEd2571sv103Csd1611bc03sc00i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : nvidia-driver-545-open - distro non-free recommended
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-545 - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

== /sys/devices/pci:00/:00:1f.4 ==
modalias : pci:v8086d7AA3sv103Csd895Ebc0Csc05i00
vendor   : Intel Corporation
driver   : oem-stella-asobo-meta - distro free

+ _run sudo ubuntu-drivers autoinstall
+ ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.163.75 sudo ubuntu-drivers autoinstall
Traceback (most recent call last):
  File "/usr/bin/ubuntu-drivers", line 513, in 
greet()
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
  File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
  File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-drivers-common 1:0.9.6.2~0.22.04.6
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
Date: Thu Feb 15 21:53:15 2024
InstallationDate: Installed on 2022-05-10 (646 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  UnboundLocalError Python error when running `ubuntu-drivers
  autoinstall`

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  As part of the Certification regression testing process, we
  automatically provision devices in our Certification lab with
  different versions of Ubuntu to make sure no regressions are
  introduced during the SRU process.

  Recently, we got an issue when trying to provision Ubuntu 22.04 on a
  device with a Nvidia GPU. The Nvidia drivers should be installed with
  the ubuntu-drivers autoinstall command, however when run, the
  following exception is thrown:

  ubuntu@10.102.163.75 sudo ubuntu-drivers devices
  == /sys/devices/pci:00/:00:01.1/:01:00.0 ==
  modalias : pci:v10DEd2571sv1

[Desktop-packages] [Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)

2024-02-09 Thread Pierre A

I have the error

meta_monitor_manager_get_logical_monitor_from_number: assertion
'(unsigned int) number < g_list_length (manager->logical_monitors)'
failed

with GNOME Shell 45.3 in Manjaro after suspend and only with external
monitor connected to laptop.

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

Title:
  Disconnecting monitor crashes shell (wayland, gnome)

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

Bug description:
  This bug has been persisting since I've bought an external monitor for
  my laptop and started using Wayland (first on Ubuntu 20.04) until
  today (Ubuntu 21.10).

  It isn't consistent, but it occurs about 90% of the time when I'm on
  Wayland. On Xorg, this has never occurred.

  When I unplug my USB-C monitor from my laptop, the laptop screen
  freezes for a while before presenting me with the login screen. When I
  log back in, all my open applications have been shut down.

  I assume Mutter crashes, taking the entire session with it.

  Dmesg doesn't seem to contain anything useful.

  A lot of other people seem to have this problem (see 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but all 
have been asked to file their own bug reports, so here I am.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-04-01 (613 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags: wayland-session impish third-party-packages
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-05 (61 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-12-01T17:24:37.722144

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


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

[Desktop-packages] [Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)

2024-02-09 Thread Pierre A

X11 not Wayland

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

Title:
  Disconnecting monitor crashes shell (wayland, gnome)

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

Bug description:
  This bug has been persisting since I've bought an external monitor for
  my laptop and started using Wayland (first on Ubuntu 20.04) until
  today (Ubuntu 21.10).

  It isn't consistent, but it occurs about 90% of the time when I'm on
  Wayland. On Xorg, this has never occurred.

  When I unplug my USB-C monitor from my laptop, the laptop screen
  freezes for a while before presenting me with the login screen. When I
  log back in, all my open applications have been shut down.

  I assume Mutter crashes, taking the entire session with it.

  Dmesg doesn't seem to contain anything useful.

  A lot of other people seem to have this problem (see 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but all 
have been asked to file their own bug reports, so here I am.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-04-01 (613 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags: wayland-session impish third-party-packages
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-05 (61 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-12-01T17:24:37.722144

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


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

[Desktop-packages] [Bug 1754687] Re: gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed

2024-02-09 Thread Pierre A

I have this error also in GNOME Shell 45.3.

I often occurs after suspend while 4K external monitor is connected.

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

Title:
  gnome-shell crashes with
  meta_monitor_manager_get_logical_monitor_from_number: assertion
  '(unsigned int) number < g_list_length (manager->logical_monitors)'
  failed

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

Bug description:
  I have a kaby lake nuc (NUC7i5BNK) connected to a Samsung 4K tv over
  hdmi. If i turn the TV off, when i switch it back on, the session is
  killed and I'm sent back to the login screen.

  Occurs on 17.10 and 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.27.92-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Mar  9 15:02:50 2018
  InstallationDate: Installed on 2017-12-01 (98 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)

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


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

[Desktop-packages] [Bug 1967632]

2024-01-10 Thread Pierre Ossman (Cendio AB)

It would be a big limitation if the solution to this focuses entirely on
pcsc-lite:

a) /var/run/pcscd/pcscd.comm is internal and varies between
distributions and pcsc-lite versions. I.e. any pcsc-lite library
embedded in the snap package is not guaranteed to be able to talk to the
system pcscd

b) Remote desktop solutions such as ThinLinc or FreeRDP tend to override
the pcsc library so that smart card access can be tunneled.

I would suggest having a more generic tunnel between the snap and the
session the snap is running in. Either on the PC/SC layer, or on the
PKCS#11 layer. The session side of that tunnel would then hopefully
respect the session environment fully.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

2023-10-25 Thread Pierre-Alexandre Defresne

It's fixed in ubuntu 23.10, thanks to kernel 6.5 I guess.

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

Title:
  Dell XPS 9730 no sound, I have tried the 22.04 lts same issue

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've tried various fixes without success, I did manage to get the
  NVIDA HDMI in the sound options but I've never had the inbuilt Intel
  Media Hardware working for sound.  22.04 LTS had the same issue and
  I've upgraded to the new version 23.04 which looks good.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 2245 F wireplumber
   /dev/snd/seq:daniel 2241 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 22 17:30:27 2023
  InstallationDate: Installed on 2023-06-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 067X4F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9730
  dmi.product.sku: 0BDB
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1653351]

2023-10-11 Thread Pierre Ossman (Cendio AB)

Great. :)

Unfortunately, in my case I'm a user of the deselect addon, so that's
what I was referring to. I don't know if that developer is following
this bug?

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

Title:
  Have option to not automatically open next email

Status in Mozilla Thunderbird:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  I have found that with Thunderbird if I open an email and then press a
  button such as the "Junk" or "Delete" button, it will automatically
  move on and open the next email. Now as I get a lot of spam on this
  email in the inbox with the spam filter not properly configured yet,
  it would be very useful if there were an option to disable this
  automatically opening the next email feature. So that it would just go
  to the blank screen in the email display section. Quite a few people I
  know for similar reasons say they would like an option like this so
  that malicious emails don't accidentally get opened.

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


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

[Desktop-packages] [Bug 1653351]

2023-10-11 Thread Pierre Ossman (Cendio AB)

The new overhaul of Thunderbird unfortunately broke the workaround addon
again. :/

I don't suppose anyone has had time to look at implementing this in
Thunderbird directly?

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

Title:
  Have option to not automatically open next email

Status in Mozilla Thunderbird:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  I have found that with Thunderbird if I open an email and then press a
  button such as the "Junk" or "Delete" button, it will automatically
  move on and open the next email. Now as I get a lot of spam on this
  email in the inbox with the spam filter not properly configured yet,
  it would be very useful if there were an option to disable this
  automatically opening the next email feature. So that it would just go
  to the blank screen in the email display section. Quite a few people I
  know for similar reasons say they would like an option like this so
  that malicious emails don't accidentally get opened.

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


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

[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update

2023-07-08 Thread Pierre C. Dussault

This kernel creates problems for me as well, with rootless podman
commands. See Bug #2026620

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

Title:
  Unrequested kernel update

Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions


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

[Desktop-packages] [Bug 1897456] Re: [Z390 M, Realtek ALC892, Green Line Out, Rear] No sound at all

2023-05-13 Thread Jean-Pierre van Riel

I have the same issue after a recent kernel update. Not sure if the
cause is the same, but after about 5 hours looking to the issue, the
mostly likely cause seems well explained on this bug comment:
https://bugzilla.kernel.org/show_bug.cgi?id=208061#c5

In my case.

Distro v: 20.04.6 LTS
Kernel v: 5.15.0-71-generic

I'm hoping the upstream kernel will have the regression with jack
sensing fixed. Via the CLI, I can use alas directly and the sound card
works fine, but with pulseaudio, it claims the ports are not available /
connected and refuses to default sound output to the analogue line out
port because jack sensing fails and even in gnome audio settings it
won't list analogue audio as an option.


** Bug watch added: Linux Kernel Bug Tracker #208061
   https://bugzilla.kernel.org/show_bug.cgi?id=208061

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

Title:
  [Z390 M, Realtek ALC892, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The desktop speakers not working. No sound at all. However the same
  setup of sound port and speakers work fine on Windows. I am using the
  Green port for the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  suds   1634 F pulseaudio
   /dev/snd/controlC0:  suds   1634 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 27 18:38:58 2020
  InstallationDate: Installed on 2020-07-04 (84 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1132 F pulseaudio
suds   1634 F pulseaudio
   /dev/snd/controlC0:  gdm1132 F pulseaudio
suds   1634 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Z390 M, Realtek ALC892, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390 M-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd10/15/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390M:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390M-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z390 M
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-07 Thread Pierre BLONDEAU

** Information type changed from Public to Public Security

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-14 Thread Pierre Equoy

Just to clarify, my webcam is a very simple (and old, like 10 years
old!) USB webcam: 046d:0802 Logitech, Inc. Webcam C200.

Attached output from v4l-info.

** Attachment added: "v4linfo.log"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635648/+files/v4linfo.log

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

Title:
Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

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

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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-13 Thread Pierre Equoy

And this is the logs from Chromium when running the steps in the
previous comment.

** Attachment added: "chromium_hwacc_no_webcam.log"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635526/+files/chromium_hwacc_no_webcam.log

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

Title:
Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
New

Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-13 Thread Pierre Equoy

1. The Pipewire flag was set to "Default", but even when set to "Enabled", the
webcam does not work.
2. journalctl.log attached when accessing framatalk.org and creating a room.

** Attachment added: "journalctl.log"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635525/+files/journalctl.log

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

Title:
Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
New

Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-13 Thread Pierre Equoy

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-12 Thread Pierre Equoy

** Attachment added: "chromium_hwacc_no_webcam_google_meet.log"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635474/+files/chromium_hwacc_no_webcam_google_meet.log

** Description changed:

With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc
branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

- One retrieved by launching Chromium with `chromium
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a
room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr`
and accessing a Google Meet event.
+
+
+ Configuration information
+ =
+
+ - Desktop with AMD GPU RX580
+ - Ubuntu 20.04 (kernel 5.15.0-56-generic)
+ - Webcam: 046d:0802 Logitech, Inc. Webcam C200
+ - Headset: 046d:0a38 Logitech, Inc. Headset H340

** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
New

Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

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

[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc

2022-12-12 Thread Pierre Equoy

** Attachment added: "chromium_hwacc_no_webcam_framatalk.log"

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+attachment/5635473/+files/chromium_hwacc_no_webcam_framatalk.log

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

Title:
Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
New

Bug description:
With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from
latest/candidate/hwacc branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

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

[Desktop-packages] [Bug 1999487] [NEW] Webcam does not work with v107.0.5304.121-hwacc

2022-12-12 Thread Pierre Equoy

Public bug reported:

With the latest version of Chromium in the stable channel
(108.0.5359.94), I can access the webcam and the microphone in Google
Meet and Jitsi (using a framatalk.org instance).

However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc
branch), the same test does not work.

The only difference between the two in `snap connections chromium` is

content   chromium:va-driver-non-free -
-

Test:

1. Install Chromium from the given channel
2. Go to https://framatalk.org/ and click on "Create a room"
3. Accept the permissions to access Microphone and Camera

Expected result:

Image from camera is displayed on screen

Actual result:

The webcam is turned on (the LED turns on), but no image is captured,
and after a few seconds, an error message is displayed ("We are unable
to access your camera").

In the settings, I can see the camera name ("UVC Camera (046d:0802)").

Attached are two logs:

- One retrieved by launching Chromium with `chromium --enable-logging=stderr`, 
accessing framatalk.org and clicking on "Create a room".
- One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


Configuration information
=

- Desktop with AMD GPU RX580
- Ubuntu 20.04 (kernel 5.15.0-56-generic)
- Webcam: 046d:0802 Logitech, Inc. Webcam C200
- Headset: 046d:0a38 Logitech, Inc. Headset H340

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Assignee: Nathan Teodosio (nteodosio)
 Status: New

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

Title:
  Webcam does not work with v107.0.5304.121-hwacc

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of Chromium in the stable channel
  (108.0.5359.94), I can access the webcam and the microphone in Google
  Meet and Jitsi (using a framatalk.org instance).

  However, with version 107.0.5304.121-hwacc (from
  latest/candidate/hwacc branch), the same test does not work.

  The only difference between the two in `snap connections chromium` is

  content   chromium:va-driver-non-free -
  -

  Test:

  1. Install Chromium from the given channel
  2. Go to https://framatalk.org/ and click on "Create a room"
  3. Accept the permissions to access Microphone and Camera

  Expected result:

  Image from camera is displayed on screen

  Actual result:

  The webcam is turned on (the LED turns on), but no image is captured,
  and after a few seconds, an error message is displayed ("We are unable
  to access your camera").

  In the settings, I can see the camera name ("UVC Camera (046d:0802)").

  Attached are two logs:

  - One retrieved by launching Chromium with `chromium 
--enable-logging=stderr`, accessing framatalk.org and clicking on "Create a 
room".
  - One retrieved by launching Chromium with `chromium --enable-logging=stderr` 
and accessing a Google Meet event.


  Configuration information
  =

  - Desktop with AMD GPU RX580
  - Ubuntu 20.04 (kernel 5.15.0-56-generic)
  - Webcam: 046d:0802 Logitech, Inc. Webcam C200
  - Headset: 046d:0a38 Logitech, Inc. Headset H340

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


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

[Desktop-packages] [Bug 1998050] [NEW] package firefox 107.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-11-27 Thread Jean-Pierre Stierlin

Public bug reported:

Here's the apt upgrade output:

me@host:~$ sudo apt install firefox
[sudo] password for me: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf2.0-0 xul-ext-ubufox
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  firefox
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/72.3 kB of archives.
After this operation, 210 MB disk space will be freed.
Preconfiguring packages ...
(Reading database ... 221702 files and directories currently installed.)
Preparing to unpack .../firefox_1%3a1snap1-0ubuntu2_arm64.deb ...
=> Installing the firefox snap
==> Checking connectivity with the snap store
==> Installing the firefox snap
error: cannot perform the following tasks:
- Run hook connect-plug-host-hunspell of snap "firefox" (run hook 
"connect-plug-host-hunspell": cannot perform operation: mount --bind 
/snap/core20/current/etc/nsswitch.conf /tmp/s
nap.rootfs_yMyxE3/etc/nsswitch.conf: Permission denied)
dpkg: error processing archive 
/var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu2_arm64.deb (--unpack):
 new firefox package pre-installation script subprocess returned error exit 
status 1
Please restart all running instances of firefox, or you will experience 
problems.
Errors were encountered while processing:
 /var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu2_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 107.0+build2-0ubuntu0.20.04.1
Uname: Linux 4.9.333-86 aarch64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm3473 F pulseaudio
  chombier   3649 F pulseaudio
BuildID: 20221110173214
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Sun Nov 27 13:34:58 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
IfupdownConfig:
 # ifupdown has been replaced by netplan(5) on this system.  See
 # /etc/netplan for current configuration.
 # To re-enable ifupdown on this system, you can run:
 #sudo apt install ifupdown
IpRoute:
 default via 192.168.1.1 dev eth0 proto dhcp metric 100 
 169.254.0.0/16 dev eth0 scope link metric 1000 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.49 metric 100
Lspci:
 
NoProfiles: True
PciNetwork:
 
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 107.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-11-27 (0 days ago)

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


** Tags: apport-package arm64 jammy need-duplicate-check

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

Title:
  package firefox 107.0+build2-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  Here's the apt upgrade output:

  me@host:~$ sudo apt install firefox
  [sudo] password for me: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf2.0-0 xul-ext-ubufox
  Use 'sudo apt autoremove' to remove them.
  The following packages will be upgraded:
firefox
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/72.3 kB of archives.
  After this operation, 210 MB disk space will be freed.
  Preconfiguring packages ...
  (Reading database ... 221702 files and directories currently installed.)
  Preparing to unpack .../firefox_1%3a1snap1-0ubuntu2_arm64.deb ...
  => Installing the firefox snap
  ==> Checking connectivity with the snap store
  ==> Installing the firefox snap
  error: cannot perform the following tasks:
  - Run hook connect-plug-host-hunspell of snap "firefox" (run hook 
"connect-plug-host-hunspell": cannot perform operation: mount --bind 
/snap/core20/current/etc/nsswitch.conf /tmp/s
  nap.rootfs_yMyxE3/etc/nsswitch.conf: Permission denied)
  dpkg: error processing archive 
/var/cache/apt/archives

[Desktop-packages] [Bug 1978098] [NEW] python3-gi doesn't depend on python3-cairo

2022-06-09 Thread Pierre Ossman (Cendio AB)

Public bug reported:

There is a missing dependency that makes using GTK/GDK from Python a bit
brittle.

GTK/GDK uses cairo for drawing, so having GTK/GDK means that cairo is
available and can be used.

However, having the Python bindings for GTK/GDK currently doesn't
guarantee that the Python bindings for cairo are installed. Hence,
drawing functions can explode when Python GTK applications try to use
them. In the Red Hat world, this dependency is on pygobject, hence I'm
filing a bug to add the same thing here.

Upstream report for the same thing on Debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995784

(also includes a simple example)

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

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

Title:
  python3-gi doesn't depend on python3-cairo

Status in pygobject package in Ubuntu:
  New

Bug description:
  There is a missing dependency that makes using GTK/GDK from Python a
  bit brittle.

  GTK/GDK uses cairo for drawing, so having GTK/GDK means that cairo is
  available and can be used.

  However, having the Python bindings for GTK/GDK currently doesn't
  guarantee that the Python bindings for cairo are installed. Hence,
  drawing functions can explode when Python GTK applications try to use
  them. In the Red Hat world, this dependency is on pygobject, hence I'm
  filing a bug to add the same thing here.

  Upstream report for the same thing on Debian:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995784

  (also includes a simple example)

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


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

[Desktop-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox

2022-04-01 Thread Pierre Equoy

I just filed lp:1967478 before finding this issue... There might be
additional information there.

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

Title:
  Jammy didn't use nvidia driver when executing firefox

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

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


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

[Desktop-packages] [Bug 1967478] Re: Discrete GPU is not used even when using "Launch using dedicated graphics card" option

2022-04-01 Thread Pierre Equoy

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


** Summary changed:

- Dsicrete GPU is not used even when using "Launch using dedicated graphics 
card" option
+ Discrete GPU is not used even when using "Launch using dedicated graphics 
card" option

** This bug has been marked a duplicate of bug 1967456
   Jammy didn't use nvidia driver when executing firefox

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

Title:
  Discrete GPU is not used even when using "Launch using dedicated
  graphics card" option

Status in firefox package in Ubuntu:
  New

Bug description:
  Image: 22.04 beta
  Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000 
Mobile] GPU)
  Desktop: GNOME running Wayland
  Firefox snap: 98.0.2-1 (1154) 

  Summary
  ===

  Firefox, a snap application, does not see the Discrete GPU, even when
  run using the appropriate option ("Launch using Discrete Graphics
  Card"). The problem does not seem to happen with non-snap
  applications.

  
  Steps to reproduce
  ==

  1. Install 22.04 beta image using third party software (nvidia proprietary 
drivers)
  2. Launch Firefox by left-clicking on the icon
  3. Go to about:support, and check the GPU information
  4. Close Firefox
  5. Right click on Firefox icon, and select "Launch using Discrete Graphics 
Card"
  6. Repeat step 3

  Expected result
  ===

  In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
  In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).

  Actual result
  =

  In both step 3 and step 6, the active GPU is the integrated one:

  
  Graphics
  

  GPU #1
  Active: Yes
  Description: Mesa Intel(R) UHD Graphics (TGL GT1)
  Vendor ID: 0x8086
  Device ID: 0x9a70
  Driver Vendor: mesa/iris
  Driver Version: 21.0.3.0
  RAM: 0
  GPU #2
  Active: No
  Vendor ID: 0x10de
  Device ID: 0x24b6

  
  It might be a snap problem, because if I run the same test with a non-snap 
application (e.g. Terminal), it works as expected:

  1. Open the terminal application, and run (you may have to install
  mesa-utils package):

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: Intel

  2. Close the terminal, right click on its icon, select  "Launch using
  Discrete Graphics Card" and repeat step 1:

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: NVIDIA Corporation

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 15:46:39 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967478] Re: Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option

2022-04-01 Thread Pierre Equoy

More logs coming from sosreport.

** Attachment added: "sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967478/+attachment/5575550/+files/sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz

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

Title:
  Dsicrete GPU is not used even when using "Launch using dedicated
  graphics card" option

Status in firefox package in Ubuntu:
  New

Bug description:
  Image: 22.04 beta
  Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000 
Mobile] GPU)
  Desktop: GNOME running Wayland
  Firefox snap: 98.0.2-1 (1154) 

  Summary
  ===

  Firefox, a snap application, does not see the Discrete GPU, even when
  run using the appropriate option ("Launch using Discrete Graphics
  Card"). The problem does not seem to happen with non-snap
  applications.

  
  Steps to reproduce
  ==

  1. Install 22.04 beta image using third party software (nvidia proprietary 
drivers)
  2. Launch Firefox by left-clicking on the icon
  3. Go to about:support, and check the GPU information
  4. Close Firefox
  5. Right click on Firefox icon, and select "Launch using Discrete Graphics 
Card"
  6. Repeat step 3

  Expected result
  ===

  In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
  In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).

  Actual result
  =

  In both step 3 and step 6, the active GPU is the integrated one:

  
  Graphics
  

  GPU #1
  Active: Yes
  Description: Mesa Intel(R) UHD Graphics (TGL GT1)
  Vendor ID: 0x8086
  Device ID: 0x9a70
  Driver Vendor: mesa/iris
  Driver Version: 21.0.3.0
  RAM: 0
  GPU #2
  Active: No
  Vendor ID: 0x10de
  Device ID: 0x24b6

  
  It might be a snap problem, because if I run the same test with a non-snap 
application (e.g. Terminal), it works as expected:

  1. Open the terminal application, and run (you may have to install
  mesa-utils package):

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: Intel

  2. Close the terminal, right click on its icon, select  "Launch using
  Discrete Graphics Card" and repeat step 1:

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: NVIDIA Corporation

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 15:46:39 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967478] [NEW] Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option

2022-04-01 Thread Pierre Equoy

Public bug reported:

Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000 
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154) 

Summary
===

Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap applications.


Steps to reproduce
==

1. Install 22.04 beta image using third party software (nvidia proprietary 
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics Card"
6. Repeat step 3

Expected result
===

In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).

Actual result
=

In both step 3 and step 6, the active GPU is the integrated one:


Graphics


GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6


It might be a snap problem, because if I run the same test with a non-snap 
application (e.g. Terminal), it works as expected:

1. Open the terminal application, and run (you may have to install mesa-
utils package):

$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel

2. Close the terminal, right click on its icon, select  "Launch using
Discrete Graphics Card" and repeat step 1:

$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 15:46:39 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Dsicrete GPU is not used even when using "Launch using dedicated
  graphics card" option

Status in firefox package in Ubuntu:
  New

Bug description:
  Image: 22.04 beta
  Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000 
Mobile] GPU)
  Desktop: GNOME running Wayland
  Firefox snap: 98.0.2-1 (1154) 

  Summary
  ===

  Firefox, a snap application, does not see the Discrete GPU, even when
  run using the appropriate option ("Launch using Discrete Graphics
  Card"). The problem does not seem to happen with non-snap
  applications.

  
  Steps to reproduce
  ==

  1. Install 22.04 beta image using third party software (nvidia proprietary 
drivers)
  2. Launch Firefox by left-clicking on the icon
  3. Go to about:support, and check the GPU information
  4. Close Firefox
  5. Right click on Firefox icon, and select "Launch using Discrete Graphics 
Card"
  6. Repeat step 3

  Expected result
  ===

  In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
  In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).

  Actual result
  =

  In both step 3 and step 6, the active GPU is the integrated one:

  
  Graphics
  

  GPU #1
  Active: Yes
  Description: Mesa Intel(R) UHD Graphics (TGL GT1)
  Vendor ID: 0x8086
  Device ID: 0x9a70
  Driver Vendor: mesa/iris
  Driver Version: 21.0.3.0
  RAM: 0
  GPU #2
  Active: No
  Vendor ID: 0x10de
  Device ID: 0x24b6

  
  It might be a snap problem, because if I run the same test with a non-snap 
application (e.g. Terminal), it works as expected:

  1. Open the terminal application, and run (you may have to install
  mesa-utils package):

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: Intel

  2. Close the terminal, right click on its icon, select  "Launch using
  Discrete Graphics Card" and repeat step 1:

  $ glxinfo | grep "OpenGL vendor"
  OpenGL vendor string: NVIDIA Corporation

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri

[Desktop-packages] [Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

2022-03-31 Thread Pierre Equoy

Just for the record, I see the same issue with a Dell Precision 7760
(CID 202103-28858) when running 22.04 beta on Wayland. I was told the
HDMI connector was wired directly to the Nvidia GPU, so gnome-shell
crashes when I connect an external monitor there, but even after logging
back in, the monitor cannot be used.

Plugging the same monitor to the USB-C connector (which is wired to
Intel GPU apparently) works like a charm...

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

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  This is on my weird desktop setup, with one monitor plugged into an
  AMD card and one into an NVIDIA card.

  When using the Wayland session, by default Shell will come up on the
  monitor connected to the AMD card, and the second (NVIDIA) monitor
  will be blank. Attempting to enable the second monitor in Display
  Settings will immediately and reproducibly crash gnome-shell.

  This is trivial for me to reproduce, so if you need patches tested I
  can easily do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 
5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2
  Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 09:37:51 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-11-02 (125 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

2022-03-31 Thread Pierre Equoy

The video shows what happens when user is using 175% fractional scaling
and then deactivate Fractional Scaling:

- only the upper left part of the screen is used
- a popup asks if user wants to keep or revert the changes
- if user clicks Revert, it doesn't actually revert back to Fractional Scaling, 
but it remains in integer scaling, and the whole screen is being used.

** Attachment added: "lp1967450_fractional_scaling.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+attachment/5575453/+files/lp1967450_fractional_scaling.mp4

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

Title:
  When switching from 175% fractional scaling back to integer scaling,
  only a quarter of the screen is used

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps
  =

  - In Settings > Display, activate Fractional Scaling, and set it to 175%.
  - Deactivate fractional scaling and press Apply

  Expected results
  

  The screen goes back to 200% integer scaling

  
  Actual results
  ==

  Only the upper left quarter of the screen is being used.

  Workaround
  ==

  After pressing Apply, a popup asks if we want to keep changes or
  revert them.

  Pressing "Revert" does not revert anything, but actually updates the
  screen to use the full screen instead of just the upper left section,
  while remaining in 200% integer scaling!

  
  Information
  ===

  Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release: 22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel 
and headers
  ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux 
kernel version 5.15.0
  ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers 
for version 5.15.0 on 64 bit x86 SMP
  ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel 
headers
  ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image 
generic
  ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
  ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra 
modules for version 5.15.0 on 64 bit x86 SMP
  ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel 
extra modules for version 5.15.0 on 64 bit x86 SMP
  ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux 
kernel nvidia modules for version 5.15.0-23
  ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra 
drivers for nvidia-510 for the generic-hwe-20.04 flavour
  ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux 
kernel nvidia modules for version 5.15.0-23 (objects)
  ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux 
kernel signatures for nvidia modules for version 5.15.0-23-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 10:51:09 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
   b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967450] [NEW] When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used

2022-03-31 Thread Pierre Equoy

Public bug reported:

Steps
=

- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply

Expected results


The screen goes back to 200% integer scaling


Actual results
==

Only the upper left quarter of the screen is being used.

Workaround
==

After pressing Apply, a popup asks if we want to keep changes or revert
them.

Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!


Information
===

Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04

Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858

Third party software installed during installation

Wayland in use.

ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel and 
headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux 
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers for 
version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel 
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra 
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra 
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra 
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel 
signatures for nvidia modules for version 5.15.0-23-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
 b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  When switching from 175% fractional scaling back to integer scaling,
  only a quarter of the screen is used

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps
  =

  - In Settings > Display, activate Fractional Scaling, and set it to 175%.
  - Deactivate fractional scaling and press Apply

  Expected results
  

  The screen goes back to 200% integer scaling

  
  Actual results
  ==

  Only the upper left quarter of the screen is being used.

  Workaround
  ==

  After pressing Apply, a popup asks if we want to keep changes or
  revert them.

  Pressing "Revert" does not revert anything, but actually updates the
  screen to use the full screen instead of just the upper left section,
  while remaining in 200% integer scaling!

  
  Information
  ===

  Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release: 22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel 
and headers
  ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux 
kernel version 5.15.0
  ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers 
for version 5.15.0 on 64 bit x86 SMP
  ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel 
headers
  ii linux-image-5.15.0-23-generic 5.15.

[Desktop-packages] [Bug 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-03-31 Thread Pierre Equoy

You can clearly see what's going on in the attached video.

** Attachment added: "lp1967448_scaling300.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967448/+attachment/5575424/+files/lp1967448_scaling300.mp4

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

Title:
  All the windows and the desktop icons disappear constantly after
  setting Scaling to 300%

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Summary
  ===

  Device with nvidia GPU, using proprietary drivers, wayland activated
  by default.

  By default, the scaling is set to 200% (the screen is UHD). If
  selecting 300%, all the windows close down, as well as the desktop
  icons (Home) as long as the mouse cursor is in the way.

  To fix the issue, one has to open the Display Settings (while making
  sure the mouse cursor is never above any of the Settings windows!),
  then set Scaling back to 200% using the keyboard.

  This problem does not happen in X11, and does not happen in Wayland if
  I select 100%, 200% or even 400% scaling!

  Steps to reproduce
  ==

  - Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
  - After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
  - Go to Settings > Display, select 300% scaling, then press Apply

  Expected result
  ===

  The scaling is set to 300% and user can keep using the device.

  Actual result
  =

  The scaling is set to 300% and all the windows are shut down. If user
  tries to reopen a window (e.g. Terminal), it is shut down immediately
  if the mouse cursor is hovering it. The desktop icons keep
  disappearing and reappearing for as long as the mouse cursor is
  hovering the background.

  The only way to stop this is to go back to Settings > Display, and,
  using the keyboard, set the scaling back to 200%.

  Information
  ===

  Version:  Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release:  22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii  linux-generic-hwe-20.045.15.0.23.25   
 amd64Complete Generic Linux kernel and headers
  ii  linux-headers-5.15.0-235.15.0-23.23   
 all  Header files related to Linux kernel version 5.15.0
  ii  linux-headers-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
  ii  linux-headers-generic-hwe-20.045.15.0.23.25   
 amd64Generic Linux kernel headers
  ii  linux-image-5.15.0-23-generic  5.15.0-23.23   
 amd64Signed kernel image generic
  ii  linux-image-generic-hwe-20.04  5.15.0.23.25   
 amd64Generic Linux kernel image
  ii  linux-modules-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23
  ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 
 amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
  ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23 
(objects)
  ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1 
 amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 10:24:25 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-

[Desktop-packages] [Bug 1967448] [NEW] All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-03-31 Thread Pierre Equoy

Public bug reported:

Summary
===

Device with nvidia GPU, using proprietary drivers, wayland activated by
default.

By default, the scaling is set to 200% (the screen is UHD). If selecting
300%, all the windows close down, as well as the desktop icons (Home) as
long as the mouse cursor is in the way.

To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!), then
set Scaling back to 200% using the keyboard.

This problem does not happen in X11, and does not happen in Wayland if I
select 100%, 200% or even 400% scaling!

Steps to reproduce
==

- Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply

Expected result
===

The scaling is set to 300% and user can keep using the device.

Actual result
=

The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately if
the mouse cursor is hovering it. The desktop icons keep disappearing and
reappearing for as long as the mouse cursor is hovering the background.

The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.

Information
===

Version:Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release:22.04

Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858

Third party software installed during installation

Wayland in use.

ii  linux-generic-hwe-20.045.15.0.23.25 
   amd64Complete Generic Linux kernel and headers
ii  linux-headers-5.15.0-235.15.0-23.23 
   all  Header files related to Linux kernel version 5.15.0
ii  linux-headers-5.15.0-23-generic5.15.0-23.23 
   amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-20.045.15.0.23.25 
   amd64Generic Linux kernel headers
ii  linux-image-5.15.0-23-generic  5.15.0-23.23 
   amd64Signed kernel image generic
ii  linux-image-generic-hwe-20.04  5.15.0.23.25 
   amd64Generic Linux kernel image
ii  linux-modules-5.15.0-23-generic5.15.0-23.23 
   amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 
SMP
ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23 
   amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 
SMP
ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1   
   amd64Linux kernel nvidia modules for version 5.15.0-23
ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1   
   amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1   
   amd64Linux kernel nvidia modules for version 5.15.0-23 (objects)
ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1   
   amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-bug fixed-in-42.1 fixed-upstream jammy wayland-session

** Description changed:

  Summary
  ===
  
  Device with nvidia GPU, using proprietary drivers, wayland activated by
  default.
  
  By defa

[Desktop-packages] [Bug 1959604] Re: Thunderbird 91.5.0 regression: writes attachments to /tmp readable to everyone

2022-02-02 Thread Pierre Sauter

Done

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

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1753242
   Importance: Unknown
   Status: Unknown

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

Title:
  Thunderbird 91.5.0 regression: writes attachments to /tmp readable to
  everyone

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  thunderbird saves opened attachments to /tmp with permissions
  according to umask setting. This was fixed a long time ago with a
  protected folder /tmp/mozilla_${USER}0 and was still working correctly
  as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
  1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.

  Ubuntu 20.04.3 LTS
  Kernel release:5.13.0-25-generic
  Architecture:  x86_64

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


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

[Desktop-packages] [Bug 1959604] [NEW] Thunderbird 91.5.0 regression: writes attachments to /tmp readable to everyone

2022-01-31 Thread Pierre Sauter

Public bug reported:

thunderbird saves opened attachments to /tmp with permissions according
to umask setting. This was fixed a long time ago with a protected folder
/tmp/mozilla_${USER}0 and was still working correctly as of version
78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.

Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture:  x86_64

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

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

Title:
  Thunderbird 91.5.0 regression: writes attachments to /tmp readable to
  everyone

Status in thunderbird package in Ubuntu:
  New

Bug description:
  thunderbird saves opened attachments to /tmp with permissions
  according to umask setting. This was fixed a long time ago with a
  protected folder /tmp/mozilla_${USER}0 and was still working correctly
  as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
  1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.

  Ubuntu 20.04.3 LTS
  Kernel release:5.13.0-25-generic
  Architecture:  x86_64

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


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

[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy

After upgrading to the last version of the packages:

gnome-shell41.3-1ubuntu1
mutter-common  41.3-1ubuntu1

the issue is gone and I can see the option when right-clicking on a
desktop launcher.

** Changed in: oem-priority
   Status: New => Invalid

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

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

Status in OEM Priority Project:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
  Image: Jammy daily (20220126 build)

  Test steps
  ==

  Secure Boot enabled

  Installation options:

  - used ubiquity (not the new flutter installer)
  - normal installation
  - checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
  - left "Configure Secure Boot" checked
  - Setup a password for Secure Boot MOK enrollment
  - Used "Erase disk and install Ubuntu" option

  After installation completes, the device reboots and I enroll the MOK
  in the UEFI BIOS.

  At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
  Wayland"), which seems to be expected given that I am using NVidia
  proprietary drivers.

  Once logged in, nvidia-settings and GNOME Settings About screen both
  show that the GPU is available. It is set in "On-Demand" in nvidia-
  settings.

  
  $ switcherooctl 
  Device: 0
Name:Intel® UHD Graphics
Default: yes
Environment: DRI_PRIME=pci-_00_02_0

  Device: 1
Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
Default: no
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
  

  Expected result
  ===

  When right-clicking on an icon in the launcher (for instance Firefox
  or Files), a "Launch using dedicated graphics card" option is
  available and launches the selected software using Nvidia GPU.

  Actual result
  =

  However, there is no "Launch using dedicated graphics card" option
  available when right-clicking on an application launcher on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 28 14:00:33 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy

** Attachment added: "lspci-k.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557896/+files/lspci-k.log

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
  Image: Jammy daily (20220126 build)

  Test steps
  ==

  Secure Boot enabled

  Installation options:

  - used ubiquity (not the new flutter installer)
  - normal installation
  - checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
  - left "Configure Secure Boot" checked
  - Setup a password for Secure Boot MOK enrollment
  - Used "Erase disk and install Ubuntu" option

  After installation completes, the device reboots and I enroll the MOK
  in the UEFI BIOS.

  At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
  Wayland"), which seems to be expected given that I am using NVidia
  proprietary drivers.

  Once logged in, nvidia-settings and GNOME Settings About screen both
  show that the GPU is available. It is set in "On-Demand" in nvidia-
  settings.

  
  $ switcherooctl 
  Device: 0
Name:Intel® UHD Graphics
Default: yes
Environment: DRI_PRIME=pci-_00_02_0

  Device: 1
Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
Default: no
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
  

  Expected result
  ===

  When right-clicking on an icon in the launcher (for instance Firefox
  or Files), a "Launch using dedicated graphics card" option is
  available and launches the selected software using Nvidia GPU.

  Actual result
  =

  However, there is no "Launch using dedicated graphics card" option
  available when right-clicking on an application launcher on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 28 14:00:33 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy

** Attachment added: "journalctl_lastboot.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557897/+files/journalctl_lastboot.log

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
  Image: Jammy daily (20220126 build)

  Test steps
  ==

  Secure Boot enabled

  Installation options:

  - used ubiquity (not the new flutter installer)
  - normal installation
  - checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
  - left "Configure Secure Boot" checked
  - Setup a password for Secure Boot MOK enrollment
  - Used "Erase disk and install Ubuntu" option

  After installation completes, the device reboots and I enroll the MOK
  in the UEFI BIOS.

  At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
  Wayland"), which seems to be expected given that I am using NVidia
  proprietary drivers.

  Once logged in, nvidia-settings and GNOME Settings About screen both
  show that the GPU is available. It is set in "On-Demand" in nvidia-
  settings.

  
  $ switcherooctl 
  Device: 0
Name:Intel® UHD Graphics
Default: yes
Environment: DRI_PRIME=pci-_00_02_0

  Device: 1
Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
Default: no
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
  

  Expected result
  ===

  When right-clicking on an icon in the launcher (for instance Firefox
  or Files), a "Launch using dedicated graphics card" option is
  available and launches the selected software using Nvidia GPU.

  Actual result
  =

  However, there is no "Launch using dedicated graphics card" option
  available when right-clicking on an application launcher on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 28 14:00:33 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1959362] [NEW] "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-27 Thread Pierre Equoy

Public bug reported:

Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
Image: Jammy daily (20220126 build)

Test steps
==

Secure Boot enabled

Installation options:

- used ubiquity (not the new flutter installer)
- normal installation
- checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
- left "Configure Secure Boot" checked
- Setup a password for Secure Boot MOK enrollment
- Used "Erase disk and install Ubuntu" option

After installation completes, the device reboots and I enroll the MOK in
the UEFI BIOS.

At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
Wayland"), which seems to be expected given that I am using NVidia
proprietary drivers.

Once logged in, nvidia-settings and GNOME Settings About screen both
show that the GPU is available. It is set in "On-Demand" in nvidia-
settings.


$ switcherooctl 
Device: 0
  Name:Intel® UHD Graphics
  Default: yes
  Environment: DRI_PRIME=pci-_00_02_0

Device: 1
  Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
  Default: no
  Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1


Expected result
===

When right-clicking on an icon in the launcher (for instance Firefox or
Files), a "Launch using dedicated graphics card" option is available and
launches the selected software using Nvidia GPU.

Actual result
=

However, there is no "Launch using dedicated graphics card" option
available when right-clicking on an application launcher on the left.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 28 14:00:33 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-01-28 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: oem-priority
 Importance: High
 Assignee: jeremyszu (os369510)
 Status: New

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


** Tags: amd64 apport-bug jammy oem-priority third-party-packages

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
  Image: Jammy daily (20220126 build)

  Test steps
  ==

  Secure Boot enabled

  Installation options:

  - used ubiquity (not the new flutter installer)
  - normal installation
  - checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
  - left "Configure Secure Boot" checked
  - Setup a password for Secure Boot MOK enrollment
  - Used "Erase disk and install Ubuntu" option

  After installation completes, the device reboots and I enroll the MOK
  in the UEFI BIOS.

  At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
  Wayland"), which seems to be expected given that I am using NVidia
  proprietary drivers.

  Once logged in, nvidia-settings and GNOME Settings About screen both
  show that the GPU is available. It is set in "On-Demand" in nvidia-
  settings.

  
  $ switcherooctl 
  Device: 0
Name:Intel® UHD Graphics
Default: yes
Environment: DRI_PRIME=pci-_00_02_0

  Device: 1
Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
Default: no
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
  

  Expected result
  ===

  When right-clicking on an icon in the launcher (for instance Firefox
  or Files), a "Launch using dedicated graphics card" option is
  available and launches the selected software using Nvidia GPU.

  Actual result
  =

  However, there is no "Launch using dedicated graphics card" option
  available when right-clicking on an application launcher on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 28

[Desktop-packages] [Bug 1932328]

2021-12-12 Thread PANTALÉON Pierre

hi.
I am in France with an Ubuntu 21.10 with Wayland
I get the same problem with my Thunderbird 94.3.1
If I write an email, and I send it, I have a phantom window and my ALT-TAB 
doesn't work.

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 446641] Re: [Gamila/Giovani/Neon motherboard] ACPI error prevents drm from loading

2021-11-30 Thread Pierre-Emmanuel Novac

Yes this is a 12 years old bug but here is fix:
Either add "acpi_rsdp=0xf7f70 acpi=rsdt" to your kernel command line parameters
OR flash the patched BIOS at https://badcaps.net/forum/showthread.php?p=1088210 
for a permanent fix.

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

Title:
  [Gamila/Giovani/Neon motherboard] ACPI error prevents drm from loading

Status in module-init-tools:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  From dmesg:
  [0.00] ACPI Error: A valid RSDP was not found 20090521 tbxfroot-219

  It seems this ACPI error leads the acpi/video.ko driver to fail to
  load, which causes the drm driver to fail to load.

  Original description:
  I'm currently posting this using the vesa driver since -intel is too 
excruciatingly slow. The /var/log/Xorg.0.log.old contains the Xorg log from 
when I used -intel last X session.

  Anyways, the symptoms while using -intel are that everything becomes 
excruciatingly slow while Xorg eats up all available CPU.
  Looking at the log I believe this to be the cause of failure:

  drmOpenDevice: node name is /dev/dri/card0
  [drm] failed to load kernel module "i915"
  (EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
  (EE) intel(0): Failed to become DRM master.

  This happens on a beta live CD as well as with a fully-updated 9.10.

  I believe that the DRM errors lead to the driver falling back to an
  extremely slow (slower than vesa) software rasterizer.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 15:43:34 2009
  DistroRelease: Ubuntu 9.10
  MachineType: Hewlett-Packard PP-ABA M
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu1
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-12-generic 
root=UUID=f729410d-6864-4a78-9833-a9f7781fd469 ro quiet splash i915.modeset=0
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.4+3ubuntu5
   libgl1-mesa-glx 7.6.0-1ubuntu1
   libdrm2 2.4.14-1ubuntu1
   xserver-xorg-video-intel 2:2.9.0-1ubuntu1
   xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu3
  SourcePackage: xserver-xorg-video-intel
  Uname: Linux 2.6.31-12-generic i686
  XorgConf: Error: [Errno 13] Permission denied: '/etc/X11/xorg.conf'
  dmi.bios.date: 05/09/2005
  dmi.bios.version: 3.26
  dmi.board.name: Gamila/Giovani/Neon series
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 030
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvn&oenixTechnologies,LTD:bvr3.26:bd05/09/2005:svnHewlett-Packard:pnPP-ABAM:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnGamila/Giovani/Neonseries:rvr030:cvn:ct3:cvr:
  dmi.product.name: PP-ABA M
  dmi.sys.vendor: Hewlett-Packard
  fglrx: Not loaded
  system:
   distro: Ubuntu
   architecture:   i686kernel: 2.6.31-12-generic

  [lspci]
  00:02.0 VGA compatible controller [0300]: Intel Corporation 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 
03)
   Subsystem: Micro-Star International Co., Ltd. Device [1462:5778]
  01:0a.0 VGA compatible controller [0300]: nVidia Corporation NV18 [GeForce4 
MX 440 AGP 8x] [10de:0181] (rev a4)
   Subsystem: eVga.com. Corp. Device [3842:b089]

To manage notifications about this bug go to:
https://bugs.launchpad.net/module-init-tools/+bug/446641/+subscriptions


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-24 Thread paquin pierre

I can confirm crash on latest 20.04 is still there.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-24 Thread paquin pierre

Hello,

Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.

"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to know if this problem will be still there in next Ubuntu LTS
release.

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-22 Thread paquin pierre

Hello,

You spoke about a fixed in your comment on 2021-06-22
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30
. Is that to say that no fix will be part of Ubuntu next LTS version
22.04?

I see your link on mesa. No reponse since 8 months. In your comment on
2021-03-05 you sid "The fix isn't in the 21.0 branch yet. Only on master
(22)." => is that to say that Ubuntu 22.04 will have the fix ?

Thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-22 Thread paquin pierre

Hello Daniel,

So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if
the patch will be in next 22.04 LTS ? Or maybe there's a way to patch
20.04?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1947971] [NEW] Zsys fails in update-grub after disk is restored with Acronis True Image

2021-10-21 Thread Julien Pierre

Public bug reported:

For years, I have been backing up my Ubuntu OS using Acronis True Image
under Windows 10, and restoring it as needed. This has worked well.

Recently, I started experimenting with Ubuntu 20.04 and zfs on root. I
did a full reinstall of Ubuntu on my SSD for this. I naturally backed it
up with Acronis under Windows.

At some point, I decided to restore that backup using Acronis.

At that point, zsys started reporting problems when creating snapshots
during operations such as "apt install" and "apt remove". A simpler test
case is to create a manual snapshot :

root@server10g:/home/madbrain/Desktop# zsysctl save test-snapshot -s
ZSys is adding automatic system snapshot to GRUB menu
ERROR "update-grub" returned an error: exit status 2 
root@server10g:/home/madbrain/Desktop# 

Is there a workaround for this problem ?

I realize that this is not a common situation, and I should be backing
up and restoring zfs snapshots rather than using Acronis, but Acronis
has the advantage of having a GUI, and zsys is still experimental. So, I
would expect a True Image restore of Ubuntu to still work.
Unfortunately, that's not the case. My guess is that there was some sort
of partition identifier that was changed during the backup/restore
process in Acronis, but I'm not sure what.

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

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

Title:
  Zsys fails in update-grub after disk is restored with Acronis True
  Image

Status in zsys package in Ubuntu:
  New

Bug description:
  For years, I have been backing up my Ubuntu OS using Acronis True
  Image under Windows 10, and restoring it as needed. This has worked
  well.

  Recently, I started experimenting with Ubuntu 20.04 and zfs on root. I
  did a full reinstall of Ubuntu on my SSD for this. I naturally backed
  it up with Acronis under Windows.

  At some point, I decided to restore that backup using Acronis.

  At that point, zsys started reporting problems when creating snapshots
  during operations such as "apt install" and "apt remove". A simpler
  test case is to create a manual snapshot :

  root@server10g:/home/madbrain/Desktop# zsysctl save test-snapshot -s
  ZSys is adding automatic system snapshot to GRUB menu
  ERROR "update-grub" returned an error: exit status 2 
  root@server10g:/home/madbrain/Desktop# 

  Is there a workaround for this problem ?

  I realize that this is not a common situation, and I should be backing
  up and restoring zfs snapshots rather than using Acronis, but Acronis
  has the advantage of having a GUI, and zsys is still experimental. So,
  I would expect a True Image restore of Ubuntu to still work.
  Unfortunately, that's not the case. My guess is that there was some
  sort of partition identifier that was changed during the
  backup/restore process in Acronis, but I'm not sure what.

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


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

[Desktop-packages] [Bug 1940836] Re: Libreoffice Calc rendering very slow on GTK3

2021-10-14 Thread Jean-Pierre van Riel

Same issue for me using latest stable NVidia drivers on 20.04 with
latest 7.2 Libre office snap.

I've noticed that only Calc is affected. Impress and Writer are not
affected.

So there must be some calc specific graphics acceleration method causing
high CPU rendering load.

Unlike the orig bug report, what worked for me was removing the snap and
reverting to old deb `sudo apt install libreoffice` back to 6.4.7.2 non-
snap version. No rendering performance issues with the older deb
package.

https://ask.libreoffice.org/t/calc-and-writer-ver-7-0-are-extremely-
slow/58522/8 mentions trying this which I tried with the 7.2 snap
version:

SAL_USE_VCLPLUGIN=gen libreoffice

It seemed to work better but still somewhat slow and not nearly as
responsive as the 6.4 deb package.

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

Title:
  Libreoffice Calc rendering very slow on GTK3

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I'm on a MATE 20.04 machine, with Nvidia proprietary drivers (for
  reference, can't use Nouveau, since my machine doesn't boot with it).

  Libreoffice Calc renders slow. The delay is very noticeable, even when
  just typing characters.

  If I remove the GTK3 styling (`libreoffice-gtk3` package), then the
  rendering speed is fine (but of course, the program is unstyled, with
  some workflow consequences).

  I've tried to run on GTK2 (`libreoffice-gtk2` package installed), but
  I see Calc as unstyled, so it seems it's not actually running on GTK2.

  I've also tried to disable HW acceleration, but there is no
  improvement.

  I don't experience this slowness on any other program on my
  installation.

  I've noticed that when there's a delay, the Xorg process CPU
  occupation skyrockets (depending on how fast I type, it may go even to
  100% (single thread)).

  I've reproduced the same problem on all the LO versions, from the
  default (6.4.7) to the latest (7.2).

  The kernel version doesn't affect the problem as well (experienced on
  different 5.x versions).

  I've tried a packaged LO (from https://libreoffice.soluzioniopen.com),
  and it has the same behavior.

  I'd be perfectly happy to run on GTK2 as workaround, if that allowed
  persistent copy/paste :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-calc 1:6.4.7-0ubuntu0.20.04.1
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Aug 23 15:21:08 2021
  InstallationDate: Installed on 2020-07-01 (418 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1609750]

2021-09-27 Thread pierre-louis.bossart

if patching the PulseAudio default.pa works, then the initial issue was
probably a problem with alsa-ucm-conf not being updated in your distros.
There's no reason to use asound.state these days, it's a much better
idea to use UCM. my 2 cents.

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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


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

[Desktop-packages] [Bug 1935722] [NEW] package libreoffice-common 1:4.2.8-0ubuntu5.5 failed to install/upgrade: cannot copy extracted data for './usr/share/icons/hicolor/scalable/apps/libreoffice-base

2021-07-09 Thread Pierre Michaud

Public bug reported:

mise a jour
installing new version
ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:4.2.8-0ubuntu5.5
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date: Fri Jul  9 21:07:03 2021
DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu5.5:cannot copy 
extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
InstallationDate: Installed on 2013-04-02 (3020 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: libreoffice
Title: package libreoffice-common 1:4.2.8-0ubuntu5.5 failed to install/upgrade: 
cannot copy extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: Upgraded to xenial on 2021-06-09 (30 days ago)

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


** Tags: apport-package i386 third-party-packages xenial

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu5.5 failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to
  '/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-
  new': unexpected end of file or stream

Status in libreoffice package in Ubuntu:
  New

Bug description:
  mise a jour
  installing new version
  ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:4.2.8-0ubuntu5.5
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Fri Jul  9 21:07:03 2021
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu5.5:cannot copy 
extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2013-04-02 (3020 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu5.5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg' to 
'/usr/share/icons/hicolor/scalable/apps/libreoffice-base.svg.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: Upgraded to xenial on 2021-06-09 (30 days ago)

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-06-23 Thread paquin pierre

Well, maybe or not but I don't understand how to install the patch

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-06-14 Thread paquin pierre

Hello,

Any news on when it will be solved ? No update solved it on my ubuntu
with officials updates.

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1924681] Re: black screen after boot system

2021-04-16 Thread Pierre Equoy

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

I have exactly the same issue with a Dell Precision 5750 laptop that was
previously enabled with 20.04:

https://ubuntu.com/certification/hardware/202002-27726


$ prime-select query
nvidia
$ nvidia-xconfig -v

nvidia-xconfig:  version 460.67
  The NVIDIA X Configuration Tool.

  This program is used to manipulate X configuration files, specifically
to enable NVIDIA X driver functionality.


01:00.0 VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX 3000 
Mobile / Max-Q] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell TU106GLM [Quadro RTX 3000 Mobile / Max-Q]
Flags: bus master, fast devsel, latency 0, IRQ 230, IOMMU group 1
Memory at 7200 (32-bit, non-prefetchable) [size=16M]
Memory at 6000 (64-bit, prefetchable) [size=256M]
Memory at 7000 (64-bit, prefetchable) [size=32M]
I/O ports at 3000 [size=128]
Expansion ROM at 7308 [virtual] [disabled] [size=512K]
Capabilities: 
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

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

Title:
  black screen after boot system

Status in xorg-server package in Ubuntu:
  New

Bug description:
  system shows black screen after cold boot / warm boot.

  [Steps to reproduce]
  1) power off system
  2) power on system

  [Actual result]
  system shows black screen after boot
  system can login after switch text-mode to tty3 (pressing Ctrl+Alt+F3) then 
switch back tty1.

  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  Codename: hirsute
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ uname -r
  5.11.0-14-generic
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ prime-select query
  nvidia
  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$ nvidia-xconfig -v

  nvidia-xconfig:  version 460.67
The NVIDIA X Configuration Tool.

This program is used to manipulate X configuration files, specifically to
enable NVIDIA X driver functionality.

  u@u-HP-ZBook-Studio-G7-Mobile-Workstation:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 14:17:03 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:8736]
   NVIDIA Corporation TU104M [GeForce RTX 2080 SUPER Mobile / Max-Q] 
[10de:1e93] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104M [GeForce RTX 2080 SUPER Mobile / 
Max-Q] [103c:8736]
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: HP HP ZBook Studio G7 Mobile Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=e0dae7fa-accc-4dd8-b69d-6f09b94df1a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: S91 Ver. 01.04.01
  dmi.board.name: 8736
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.41.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.65
  dmi.modalias: 
dmi:bvnHP:bvrS91Ver.01.04.01:bd01/05/2021:br4.1:efr20.65:svnHP:pnHPZBookStudioG7MobileWorkstation:pvr:rvnHP:rn8736:rvrKBCVersion14.41.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name:

[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-04-12 Thread Pierre-Antoine Champin

@Sebastien Sorry for the late reply.

I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.

How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file ./system/apt-daily.timer,
ensuring that it contained the RandomizedDelaySec directive.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-03-03 Thread paquin pierre

Hi,

Last message seems to indicate that a fix is found, good news! Anything
to do to get the fix?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-21 Thread paquin pierre

Hello,

I sent a mail to DisplayLink, here is their answer...
"
Thank you for bringing it to our attention but based on the log files and 
errors over there the best way would be to discuss it with Xorg engineers as 
the majority of problems comes from the OS itself and not from our driver here.
"

Do you have any news about the bug?

Thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hi, thanks,

can't I just do a sudo apt purge linux-generic-hwe-20.04 ?

For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the
subject you opened on
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have
some news. That's very technical, can you put here informations when you
have a piece of solution ?

Many thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hello,

This is why you have no report from kernel 5.8+ : 
"The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg 
version is 1.16 and minimum supported Mutter (Wayland) is 3.32."

https://support.displaylink.com/knowledgebase/articles/684649

Some people seems to have kernel 5.9 working, but I tried without success, 
still have the above message. Here's an entry on DisplayLink forum with the 
same problem : 
https://displaylink.org/forum/showthread.php?t=67561

I can't create an account on this forum, don't know why... The mail with
code never arrive. If anyone has my problem, he can reply on displaylink
forum to get help with kernel 5.8+

Here's a tuto for kernel 5.9, don't work for me, but seemed to help sometimes : 
https://displaylink.org/forum/showpost.php?p=90853&postcount=2

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hello,

Well I tried... and have some troubles :). After reboot, displaylink didn't 
work anymore. I tried to uninstall but when  I try to reinstall, here what I 
get : 
ERROR (dkms apport): binary package for evdi: 1.7.0 not found
Error! Bad return status for module build on kernel: 5.8.0-43-generic (x86_64)
Consult /var/lib/dkms/evdi/1.7.0/build/make.log for more information.
ERROR: Failed to install evdi/5.3.1.34 to the kernel tree.

I know this is ubuntu, not displaylink, but if you have any idea that
would be great.

Notice : If i run install twice, I got only 1 error : "Error! DKMS tree
already contains: evdi-1.7.0" and installation continue. But don't
work... Uninstall / reinstall will do same thing (1st fatal error that
stop installer, then this one)

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: h

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()

2021-02-10 Thread paquin pierre

Hi,

I created an account on mesa forum. I don't really know what to tell,
and which file send them. Can you help me and tell me what to say and
send?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  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
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

2021-02-10 Thread paquin pierre

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

Hi,

Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I
don't think I have installed myself this. If it cause the bug, is it
possible to remove it?

Thanks,

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/evdi/+bug/1907142/+subscriptions

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

[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

2021-02-10 Thread paquin pierre

Well if I couldn't use ubuntu bug, I could use that, hope it'll help : 
apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash

It then create this bug entry : 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/evdi/+bug/1907142/+subscriptions

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

[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

2021-02-10 Thread paquin pierre

Oh I forgot, Yes, i have installed dbgsym :

$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for 
libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for 
xserver-xorg-core

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/evdi/+bug/1907142/+subscriptions

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

[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

2021-02-10 Thread paquin pierre

Hi,

Ok, if there's nothing here about xorg crash, how may I provide you more 
information about that : 
ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt
.
-rw-r-  1 username  whoopsie  17322105 févr. 10 14:15 
_usr_lib_xorg_Xorg.1000.crash


It seems I have some informations on my system about crash. but the following 
command doesn't work. I have a message with some "internal error" : 
sudo ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

Thanks,

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/evdi/+bug/1907142/+subscriptions

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

[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

2021-02-10 Thread paquin pierre

Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142/+attachment/5462347/+files/prevboot.txt

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/evdi/+bug/1907142/+subscriptions

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

[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-02-10 Thread Pierre-Antoine Champin

Same problem with 20.04.

I believe this is related to this issue:
https://bbs.archlinux.org/viewtopic.php?id=255817 .

FTR, as `apt-daily.service` is running on startup, this was also
increasing my boot-time significantly (although I found a workaround for
this particular problem). Just to emphasize that this is a serious bug.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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

[Desktop-packages] [Bug 1914573] Re: kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes

2021-02-09 Thread paquin pierre

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

Ok, seems installed, I'll report on the other bug id next time :


$ dpkg -l| grep dbgsym
ii  libgl1-mesa-dri-dbgsym:amd64   20.2.6-0ubuntu0.20.04.1  
   amd64debug symbols for libgl1-mesa-dri
ii  xserver-xorg-core-dbgsym   2:1.20.9-2ubuntu1.2~20.04.1  
   amd64debug symbols for xserver-xorg-core

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

Title:
  kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 ... and
  then the display server crashes

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes

2021-02-09 Thread paquin pierre

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

Yes it seems to be the same thing.

What can i do  next to help?

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

Title:
  kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 ... and
  then the display server crashes

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes

2021-02-09 Thread paquin pierre

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

Hi,

I Have no idea for bu 1861398. Tell me if i can do anything.

Yes, i did #16 install when you asked it. I just did it again, seems I
can do it again with no warning. I expected something like "yet
installed". How may I check if it's already installed?

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

Title:
  kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 ... and
  then the display server crashes

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-09 Thread paquin pierre

Hello,

I just had the crash. I send you the new curboot file for investigation.

I have a new entry on /var/crash, but no "uploaded" and i can't ubuntu-bug the 
crash file. There's no entry on "Error reports" webpage. As the crash file is 
"_usr_lib_xorf_Xorg.1000.crash", i did a "ubuntu-bug xorg". That created this 
bug : 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915125

If it doesn't help, you can close 1915125 new bug.

** Attachment added: "curboot_1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461603/+files/curboot_1.txt

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1915125] [NEW] xorg crash

2021-02-09 Thread paquin pierre

Public bug reported:

follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1914573

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Feb  9 08:49:45 2021
DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509]
InstallationDate: Installed on 2017-11-08 (1188 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Notebook W65_W67RZ1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-07-01 (222 days ago)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.03
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65_W67RZ1
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2016:svnNotebook:pnW65_W67RZ1:pvrNotApplicable:rvnNotebook:rnW65_W67RZ1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W65_W67RZ1
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
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 20.2.6-0ubuntu0.20.04.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 1:2.10.6-1
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
xserver.bootTime: Thu Feb  4 18:39:51 2021
xserver.configfile: default
xserver.errors:
 modeset(G0): glamor initialization failed
 modeset(G1): glamor initialization failed
 modeset(G2): glamor initialization failed
 modeset(G3): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.9-2ubuntu1.2~20.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1914573

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Feb  9 08:49:45 2021
  DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509]
  InstallationDate: Installed on 2017-11-08 (1188 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook W65_W67RZ1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-01 (222 days ago)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dm

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

I opened my session in Xorg this morgning. I only want one of Wayland or
Xorg to work, which one you think we have a better chance? You already
see some logs and probably have some idea about Xorg. My suggest is to
continue for this day with Xorg, I'll send you logs each time I get the
crash (I used to send you only one or two) for you to get as much as
information I can.

After that, maybe you'll have a better idea if continue with Xorg is a
better solution, or switch to Wayland.

Many thanks for help,

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

Hello,

You're true, I changed to Wayland because it seems to be the next
default of ubuntu, and it's recommended to use with Displaylink (even if
in the past it had some troubles). Whatever, I'll use Xorg as you ask
and I'll send you next crash information.

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

Another time, another log :).

Thanks for help.

** Attachment added: "curboot2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461238/+files/curboot2.txt

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

Error tracker entry : 
https://errors.ubuntu.com/oops/3d57ee6e-69f3-11eb-8529-fa163e102db1

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

There's something new in /var/crash, I have a gnome-shell entry, with
uploaded file. Here is file

** Attachment added: "_usr_bin_gnome-shell.1000.uploaded"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461215/+files/_usr_bin_gnome-shell.1000.uploaded

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

same file, after reboot.

** Attachment added: "prevboot3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461212/+files/prevboot3.txt

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-08 Thread paquin pierre

Hello,

I had the bug just now. It was a bit different, the screen freeze in a
strange way before "gnome reboot", so maybe it's different...

Here are the 2 files, before and after reboot just in case you need
both. They may be the same file or nearly.

** Attachment added: "curboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461211/+files/curboot.txt

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

2021-02-05 Thread paquin pierre

I assume I had to rename "ddeb" to "deb" in extension. I did that and
redo the journalctl command line. Here's the file it outputs.

I don't see anything different, but I don't realy know what i'm
searching (debug symbols). Hope that help.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460519/+files/prevboot.txt

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-05 Thread paquin pierre

Just one more description, for information... My bug is a crash of gnome
that redirect me to login screen, not a full reboot. So the shutdown
information at the end of the "prevboot.txt" are not related to the bug.

Lines begin to be strange there : 
févr. 05 09:59:51 XX kernel: i915 :00:02.0: Resetting rcs0 for hang 
on rcs0
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) Backtrace:
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x564aeb43a59c]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f530a47e41f]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 2: 
/lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f530a2bb18b]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 3: 
/lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f530a29a859]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 
unw_get_proc_name failed: no unwind info found [-10]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f530840baec]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7f530915dc9c]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7f530846074d]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 7: 
/usr/lib/xorg/Xorg (present_register_complete_notify+0x673) [0x564aeb3b6cf3]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 8: 
/usr/lib/xorg/Xorg (present_register_complete_notify+0x1fd9) [0x564aeb3b9ee9]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 9: 
/usr/lib/xorg/Xorg (present_register_complete_notify+0x26bf) [0x564aeb3baa3f]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 10: 
/usr/lib/xorg/Xorg (present_register_complete_notify+0x1361) [0x564aeb3b8581]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 11: 
/usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x564aeb2d8f34]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 12: 
/usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x564aeb2dcfc4]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 13: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f530a29c0b3]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 14: 
/usr/lib/xorg/Xorg (_start+0x2e) [0x564aeb2c6a2e]
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: Fatal server 
error:
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE) Caught 
signal 6 (Aborted). Server aborting
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XX /usr/lib/gdm3/gdm-x-session[2728]: (EE)

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-05 Thread paquin pierre

I see that in /var/crash directory : 
-rw-r--r--  1 someone  whoopsie0 févr.  5 08:37 
_usr_lib_xorg_Xorg.1000.upload
-rw---  1 whoopsie whoopsie   37 févr.  5 08:37 
_usr_lib_xorg_Xorg.1000.uploaded
drwxrwsrwt  2 root whoopsie 4096 févr.  5 09:59 .
-rw-r-  1 someone  whoopsie 18861531 févr.  5 09:59 
_usr_lib_xorg_Xorg.1000.crash

Yes crash may have occured at 09:59. "uploaded" file is before. I can't
use ubuntu-bug on crash file.

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-05 Thread paquin pierre

about last Error tracker, the datetime is strange because crash occured
05/02 at about 10:0x

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-05 Thread paquin pierre

Here is the new entry on Error tracker :
https://errors.ubuntu.com/oops/00b2327a-6785-11eb-9850-fa163e983629

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-05 Thread paquin pierre

I just have the gnome crash to login now. I join the result of the command : 
journalctl -b-1 > prevboot.txt

Thanks for help

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460445/+files/prevboot.txt

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

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

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-04 Thread paquin pierre

there's no more uploaded file for xorg crash... I'll do what you ask on
next crash and reboot.

I found the origin of the gnome-shell entries in journalctl, they came
from chrome. I try to not use it today and we'll see if I have no more
gnome crash. I have no idea if it's related but it's not, I'll have the
crash even if I don't use chrome.

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

Status in evdi package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen

2021-02-04 Thread paquin pierre

the uploaded file.

** Attachment added: "_opt_displaylink_DisplayLinkManager.0.uploaded"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460225/+files/_opt_displaylink_DisplayLinkManager.0.uploaded

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

Title:
  [DisplayLink] Desktop crashes and return to login screen

Status in evdi package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: Gnome desktop crash and return to login screen

2021-02-04 Thread paquin pierre

By the way, my "journalctl" is full of this, maybe related, maybe not...

févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: Errors:
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: 
[4886:4886:0205/073611.340319:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: 

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

Title:
  Gnome desktop crash and return to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] Re: Gnome desktop crash and return to login screen

2021-02-04 Thread paquin pierre

Hello,

1. I have 3 crash files in /var/crash but the ubuntu-bug command fail.
Each one has a ".upload" and ".uploaded" file so I think they're already
uploaded. Shall I empty the folder to have a clean start point for next
time the bug appear?

2. Many files in this page. These are the 3 related with the crashs in my 
/var/crash, but there're many others : 
2021-02-04 07:02 (the day when I opened this bug) - 
https://errors.ubuntu.com/oops/b95f8166-66b4-11eb-84cc-fa163e102db1 
2021-01-27 09:01 : 
https://errors.ubuntu.com/oops/6b87b264-607b-11eb-83c4-fa163e102db1
2021-02-02 09:02 : 
https://errors.ubuntu.com/oops/46f3c61a-652e-11eb-90f7-fa163ee63de6

May I link the full url of https://errors.ubuntu.com/user/ID or is it
unsafe?

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

Title:
  Gnome desktop crash and return to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1914573] [NEW] Gnome desktop crash and return to login screen

2021-02-04 Thread paquin pierre

Public bug reported:

The bug is that all at a sudden gnome reset to login screen. When i log
again, the only "sound output" allowed is simulation, my devices are not
displayed.

I'm using 
- Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was 
present at that moment but i used less my ubuntu station). 
- Portable PC

The bug happen
- When I use my PC with screen pluged directly : some times
- When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
- When à Use my docking station and watch some full screen video : very 
frequently

It seems to be linked to displayLink use, but not only because it happen
too when i don't use the docking station. It seems to be frequently when
i "Stress" the screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  4 10:17:54 2021
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-08 (1183 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome desktop crash and return to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

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

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

[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

2021-01-12 Thread Pierre Wilch

I had the same problem.
- Since this bug only appeared by me by consulting the proprieties of the file 
with Nautilus, and did not occur with linux mint 20 and Nemo, I reported it as 
bug 1890958 in Nautilus.
- Since updates beginning of the year 2021 I can no longer reproduce it. It 
seems to be solved.
- Ubuntu team, can you confirm it here (or not?), so people who spent time to 
report this to help you could sleep on their two ears and use ubuntu 20.04 
again, with no fear of such dangerous bugs?

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1899172] [NEW] Cannot join an external screen and the screen of the labtop

2020-10-09 Thread DESBIOLLES Pierre

Public bug reported:

I can use either the labtop screen OR the DELL external screen but I
cannot join the two screens, as it was possible (and very easy) with
Ubuntu 16.04. It did not work with 18.04, it does not work with 20.04.
It is very frustrating since it works when I start the computer, I can
see the "Ubuntu" word on both the screens, but after I enter my password
I can use only one of the screen (I change from "parameters").

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-session-utils 7.7+4
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  9 15:20:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
InstallationDate: Installed on 2020-10-09 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Latitude E4300
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=bb032965-73b6-4d9f-b40a-5f7813dbb097 ro quiet splash
SourcePackage: x11-session-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0D201R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/22/2009:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D201R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4300
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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: x11-session-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Cannot join an external screen and the screen of the labtop

Status in x11-session-utils package in Ubuntu:
  New

Bug description:
  I can use either the labtop screen OR the DELL external screen but I
  cannot join the two screens, as it was possible (and very easy) with
  Ubuntu 16.04. It did not work with 18.04, it does not work with 20.04.
  It is very frustrating since it works when I start the computer, I can
  see the "Ubuntu" word on both the screens, but after I enter my
  password I can use only one of the screen (I change from
  "parameters").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-session-utils 7.7+4
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 15:20:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
  InstallationDate: Installed on 2020-10-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E4300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=bb032965-73b6-4d9f-b40a-5f7813dbb097 ro quiet splash
  SourcePackage: x11-session-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0D201R
  dmi.board.vendor: Dell

[Desktop-packages] [Bug 1890958] [NEW] exfat month modification time increasing by simple consulting with "properties"

2020-08-09 Thread Pierre Wilch

Public bug reported:

Ubuntu 20.04, every updates done.
Each time I insert the same SDXC (64 GB, exFAT) card in my PC and show the 
modification time of always the same file by right clicking on it and then 
selecting "properties" in nautilus I notice that the month modification time 
has increased with 1 month. And one year more when jumping from december to 
january.
So, after several times inserting this card, that video file made april 28th 
2020 shows now the modification time june 28th 2021, 14 months later.
The modification time is important. It must be hold right.

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

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

Title:
  exfat month modification time increasing by simple consulting with
  "properties"

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, every updates done.
  Each time I insert the same SDXC (64 GB, exFAT) card in my PC and show the 
modification time of always the same file by right clicking on it and then 
selecting "properties" in nautilus I notice that the month modification time 
has increased with 1 month. And one year more when jumping from december to 
january.
  So, after several times inserting this card, that video file made april 28th 
2020 shows now the modification time june 28th 2021, 14 months later.
  The modification time is important. It must be hold right.

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

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

[Desktop-packages] [Bug 1889975] [NEW] Xorg crash upon several conditions

2020-08-01 Thread Pierre

Public bug reported:

Ubuntu release :

Description:Ubuntu 20.04.1 LTS
Release:20.04

Version of package : gnome-control-center:
==
  Installed: 1:3.36.4-0ubuntu1
  Candidate: 1:3.36.4-0ubuntu1
  Version table:
 *** 1:3.36.4-0ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1-1ubuntu5 500
500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages

What happens:
=

1) My session crashes when I launch gnome-control-center or 
unity-control-center.
In case it can help, the Xorg.log file reports 2 errors
[ 13421.807] (EE) open /dev/fb0: Permission denied
[ 13421.853] (EE) modeset(0): glamor initialization failed

2) Another strange stuff, is that another user cannot log anymore on this 
Ubuntu box (3 users are defined, 2 manages to loggin, the 3rd one fails). When 
the 3rd user logs, the screen goes black, and after a while you see the login 
screen with the 3 usernames.
  2260.041] (EE) Backtrace:
[  2260.041] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x56545709ce0c]
[  2260.042] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7fb5021c441f]
[  2260.042] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7fb50200118b]
[  2260.042] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7fb501fe0859]
[  2260.043] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  2260.043] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fb501fe071a]
[  2260.043] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) 
[0x7fb501ff1f36]
[  2260.043] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) 
[0x565457067d85]
[  2260.044] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5654570693d2]
[  2260.044] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x56545706a794]
[  2260.044] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x565456f3bf44]
[  2260.044] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x565456f3ffd4]
[  2260.044] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7fb501fe20b3]
[  2260.044] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x565456f29a3e]
[  2260.044] (EE) 
[  2260.044] (EE) 
Fatal server error:
[  2260.044] (EE) Caught signal 6 (Aborted). Server aborting
[  2260.044] (EE) 
[  2260.044] (EE) 

Those weird behaviors happened after having used the openshot AppImage
(but not sure this is the root cause) https://github.com/OpenShot
/openshot-qt/releases/download/v2.5.1/OpenShot-v2.5.1-x86_64.AppImage.

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

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

Title:
  Xorg crash upon several conditions

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

Bug description:
  Ubuntu release :
  
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Version of package : gnome-control-center:
  ==
Installed: 1:3.36.4-0ubuntu1
Candidate: 1:3.36.4-0ubuntu1
Version table:
   *** 1:3.36.4-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  What happens:
  =

  1) My session crashes when I launch gnome-control-center or 
unity-control-center.
  In case it can help, the Xorg.log file reports 2 errors
  [ 13421.807] (EE) open /dev/fb0: Permission denied
  [ 13421.853] (EE) modeset(0): glamor initialization failed

  2) Another strange stuff, is that another user cannot log anymore on this 
Ubuntu box (3 users are defined, 2 manages to loggin, the 3rd one fails). When 
the 3rd user logs, the screen goes black, and after a while you see the login 
screen with the 3 usernames.
2260.041] (EE) Backtrace:
  [  2260.041] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x56545709ce0c]
  [  2260.042] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7fb5021c441f]
  [  2260.042] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7fb50200118b]
  [  2260.042] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7fb501fe0859]
  [  2260.043] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  2260.043] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fb501fe071a]
  [  2260.043] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) 
[0x7fb501ff1f36]
  [  2260.043] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) 
[0x565457067d85]
  [  2260.044] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) 
[0x5654570693d2]
  [  2260.044] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x56545706a794]
  [  2260.044] (EE)

[Desktop-packages] [Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

2020-06-02 Thread Jean-Pierre van Riel

Apologies, launchpad didn't keep the neatly tab separated column format,
but hopefully the script can help others to test.

Attached png of side-by-side comparison of script output.

Only the latency for accessing a single 4K block doesn't seem to differ
too much, but for every other mult-block sequential IO read, in terms of
latency, bandwidth and IOPS, GVFS is over 10 times slower than CIFS.

While I know fuse mounts (userspace filesystems) will be understandably
slower than kernel space mounts, more than 10 times slower is
significant and indicates there's inefficiencies / room for improvement.

** Attachment added: "GVFS-SMB vs CIFS"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+attachment/5379760/+files/gvfs-smb_vs_cifs_seq_read_benchmark_ubuntu_18.04.4.png

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Copying moderate-size files to a samba share using gvfs is
  ridiculously slow compared to doing the same via mount.cifs.  For
  example:

  $ ls -sh testfile
  1.2G testfile
  $ time cp testfile ~/mnt/share-gvfs/
  real  2m37.053s
  user  0m0.056s
  sys   0m5.120s
  $ time cp testfile ~/mnt/share/
  real  0m26.134s
  user  0m0.004s
  sys   0m1.724s

  I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1.

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

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

[Desktop-packages] [Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

2020-06-02 Thread Jean-Pierre van Riel

Hi, to report, also noticed gvfs smb mount being over 10x slower in many
cases depending on the read IO pattern. Seems GVFS alls a lot of
latency. Summary of benchmark via fio:

GVFS SMB:
=

name  type  size  block_size  latency_(ms) bandwidth_(kb)  IOPS
      --   --  
4k_4k_seq_readread  4k4k  7.597604 100 25
512k_4k_seq_read  read  512k  4k  12.608847148437  312 
78.001219
4m_64k_seq_read   read  4m64k 58.59852259375   1082
16.91779
8m_256k_seq_read  read  8m256k252.2923598125   1010
3.948667
16m_1m_seq_read   read  16m   1m  1079.9320893125  946 
0.924481

CIFS:
=

name  type  size  block_size  latency_(ms)bandwidth_(kb)  IOPS
      --  --  
4k_4k_seq_readread  4k4k  7.226365250 62.5
512k_4k_seq_read  read  512k  4k  0.35290271875   9481
2370.37037
4m_64k_seq_read   read  4m64k 4.14038503125   15003   
234.432234
8m_256k_seq_read  read  8m256k17.80018796875  14148   
55.267703
16m_1m_seq_read   read  16m   1m  83.7329983125   12145   
11.860638

Bash script to test this (depends on fio, jq and column)

#json_benchmark_result_summary=''
tempfile=$(mktemp /tmp/read_test..ndjson)
echo "# Using temp file: $tempfile"

function seq_read_benchmark() {
  local total_size="$1"
  local block_size="$2"
  echo "# Testing sequential read of $total_size size in $block_size."
  sleep 1
  fio --name="${total_size}_${block_size}_seq_read" 
--filename="${total_size}_${block_size}_seq_read_test.bin" --rw=read 
--iodepth=1 --max-jobs=1 --size="$total_size" --bs="$block_size" 
--output-format=json >> "$tempfile"
  rm "${total_size}_${block_size}_seq_read_test.bin"
}

seq_read_benchmark 4k 4k  # 1 block read
seq_read_benchmark 512k 4k  # 128 x 4k blocks read
seq_read_benchmark 4m 64k  # 64 x 64k blocks read
seq_read_benchmark 8m 256k  # 32 x 128k blocks read
seq_read_benchmark 16m 1m # 16 x 1m blocks read

# Reshaping JSON with jq: 
https://programminghistorian.org/en/lessons/json-and-jq#output-a-csv-csv
# How to format a JSON string as a table using jq?: 
https://stackoverflow.com/a/39144364/5472444
jq -s -r 
'(["name","type","size","block_size","latency_(ms)","bandwidth_(kb)","IOPS"] | 
(., map(length*"-"))), (.[] | .jobs[] | [.jobname, ."job options".rw, ."job 
options".size, ."job options".bs, (.read.lat_ns.mean/100), .read.bw, 
.read.iops]) | @tsv' "$tempfile" | column -t

# Convert JSON lines to JSON array using jq: 
https://stackoverflow.com/a/61867230/5472444
#jq -s '[.[] | .jobs[] | {name: .jobname, type: ."job options".rw, size: ."job 
options".size, "block size": ."job options".bs, "latency (ms)": 
(.read.lat_ns.mean/100), "bandwidth (kb)": .read.bw, IOPS: .read.iops}]' 
"$tempfile" > read_test_summary.json

# Cleanup
rm "$tempfile"

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Copying moderate-size files to a samba share using gvfs is
  ridiculously slow compared to doing the same via mount.cifs.  For
  example:

  $ ls -sh testfile
  1.2G testfile
  $ time cp testfile ~/mnt/share-gvfs/
  real  2m37.053s
  user  0m0.056s
  sys   0m5.120s
  $ time cp testfile ~/mnt/share/
  real  0m26.134s
  user  0m0.004s
  sys   0m1.724s

  I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1.

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

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

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-06-02 Thread Pierre Equoy

Hi Salima,

this bug has been identified as happening only for people who were
upgrading from a previous version of Ubuntu (that came with a previous
version of Pulseaudio). Daniel Van Vugt found a workaround (check
comments 18 and 19 above), and a fix has been made by the Pulseaudio
developers and is being reviewed (see comment 41 above).

In your case, it seems the issue happens on a fresh install, so I
believe this issue is different. Please file a new bug for this.

Thanks!

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

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

Status in gnome-control-center:
Unknown
Status in PulseAudio:
New
Status in gnome-control-center package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in gnome-control-center source package in Focal:
Invalid
Status in pulseaudio source package in Focal:
In Progress

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

Steps to reproduce:

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

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

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

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

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

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

[Desktop-packages] [Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses

2020-06-01 Thread Pierre Equoy

If that can be of any help, I have the following use case:

In addition to the default Firefox launcher, I created two other
.desktop files:

- One called "Wayland Firefox #1" to run Firefox on Wayland with user 
profile #1
- The other called "Wayland Firefox #2" to run Firefox on Wayland with user 
profile #2

I'm using a 4k screen (3840×2160), so I have *a lot* of space available
on the screen.

And yet, GNOME uses ellipsis and this is what I get when I look for
"Firefox" in the GNOME Overview screen (see attachment).

I hope this gets fixed soon. Something as simple as a tooltip when
putting the cursor on top of the icon or text would be very helpful
already.

** Attachment added: "gnome-activities.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/968213/+attachment/5379588/+files/gnome-activities.jpg

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

Title:
  Too many icons in Gnome Shell Activities Overview require ellipses

Status in GNOME Shell:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Several apps in the default Ubuntu 17.04 or 17.10 install have
  Ellipses when shown in GNOME Shell's Activities Overview.

  This was made worse by switching GNOME Shell to use the Ubuntu font
  because the Ubuntu font is a bit wider than GNOME's default Cantarell
  font so some apps that didn't require ellipses in 17.04 require them
  now in 17.10 Alpha.

  The upstream GNOME bug proposes that apps names be allowed to use 2
  lines. This is similar to what the Settings app (gnome-control-center)
  does.

  This is also really bad for languages that use more characters than
  English.

  Original Bug Title
  --
  Gnome Shell Activities Overview should show full names on mouse hover

  Original Bug Report
  ---
  The title says it all --- especially when choosing recent documents, if they 
start with the same say 12 or 14 letters, it's impossible to differentiate them 
 (see attached screenshot).

  When mouse is hovering an icon, the full name of the
  application/document should be shown.

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

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

[Desktop-packages] [Bug 1877427] Re: Double-clicking on a thread does not open the latest message

2020-05-21 Thread Pierre Rudloff

I can still reproduce with 68.8.0 from snap.

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

Title:
  Double-clicking on a thread does not open the latest message

Status in thunderbird package in Ubuntu:
  New
Status in thunderbird package in Debian:
  New

Bug description:
  When grouping messages by thread and double-clicking on a thread, it should 
open every message in the thread in a new tab.
  However, it does not open the latest message and instead opens the first 
message twice (one time correctly and a second time at the end with a messed up 
character encoding).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1530 F pulseaudio
   /dev/snd/pcmC0D0p:   pierre 1530 F...m pulseaudio
  BuildID: 20200407160932
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu May  7 19:50:11 2020
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-06 (1492 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-70906f39-d462-489a-8cc7-a27970180403
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.7.0/20200407160932 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to eoan on 2019-11-24 (165 days ago)
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1877427] Re: Double-clicking on a thread does not open the latest message

2020-05-11 Thread Pierre Rudloff

I don't get any warning in the console when I open the thread.
Also, it seems it does not always happen the first time I open a thread (but 
always the next few times I try).

I am using an IMAP account. (And I could also reproduce on another
computer with another IMAP account.)

I could not reproduce with thunderbird 68.4.1 installed from snap (with
a new profile).

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

Title:
  Double-clicking on a thread does not open the latest message

Status in thunderbird package in Ubuntu:
  Incomplete
Status in thunderbird package in Debian:
  New

Bug description:
  When grouping messages by thread and double-clicking on a thread, it should 
open every message in the thread in a new tab.
  However, it does not open the latest message and instead opens the first 
message twice (one time correctly and a second time at the end with a messed up 
character encoding).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1530 F pulseaudio
   /dev/snd/pcmC0D0p:   pierre 1530 F...m pulseaudio
  BuildID: 20200407160932
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu May  7 19:50:11 2020
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-06 (1492 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-70906f39-d462-489a-8cc7-a27970180403
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.7.0/20200407160932 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to eoan on 2019-11-24 (165 days ago)
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1877427] [NEW] Double-clicking on a thread does not open the latest message

2020-05-07 Thread Pierre Rudloff

Public bug reported:

When grouping messages by thread and double-clicking on a thread, it should 
open every message in the thread in a new tab.
However, it does not open the latest message and instead opens the first 
message twice (one time correctly and a second time at the end with a messed up 
character encoding).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pierre 1530 F pulseaudio
 /dev/snd/pcmC0D0p:   pierre 1530 F...m pulseaudio
BuildID: 20200407160932
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu May  7 19:50:11 2020
ExecutablePath: /usr/lib/thunderbird/thunderbird
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-04-06 (1492 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-70906f39-d462-489a-8cc7-a27970180403
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=68.7.0/20200407160932 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to eoan on 2019-11-24 (165 days ago)
dmi.bios.date: 10/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: W510LU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W510LU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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

** Affects: thunderbird (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug eoan

** Bug watch added: Debian Bug tracker #959748
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959748

** Also affects: thunderbird (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959748
   Importance: Unknown
   Status: Unknown

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

Title:
  Double-clicking on a thread does not open the latest message

Status in thunderbird package in Ubuntu:
  New
Status in thunderbird package in Debian:
  Unknown

Bug description:
  When grouping messages by thread and double-clicking on a thread, it should 
open every message in the thread in a new tab.
  However, it does not open the latest message and instead opens the first 
message twice (one time correctly and a second time at the end with a messed up 
character encoding).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.7.0+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1530 F pulseaudio
   /dev/snd/pcmC0D0p:   pierre 1530 F...m pulseaudio
  BuildID: 20200407160932
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu May  7 19:50:11 2020
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-06 (1492 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kern

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2020-05-03 Thread Jean-Pierre van Riel

Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.

Even worse, seems hardware acceleration ends up being disabled:

$ journalctl --no-hostname -b -p warning _COMM=gnome-shell
-- Logs begin at Wed 2019-02-06 14:13:52 SAST, end at Sun 2020-05-03 16:09:45 
SAST. --
May 03 14:51:40 org.gnome.Shell.desktop[2284]: glamor: 'wl_drm' not supported
May 03 14:51:40 org.gnome.Shell.desktop[2284]: Missing Wayland requirements for 
glamor GBM backend
May 03 14:51:40 org.gnome.Shell.desktop[2284]: Failed to initialize glamor, 
falling back to sw
...
May 03 14:53:25 gnome-shell[6549]: setup_framebuffers: assertion 'width > 0' 
failed

The "EGL failed to allocate resources" error stops happening probably
because gnome-shell isn't even using hardware acceleration now.

I've also disabled all gnome shell extensions to avoid noise/errors in
the logs and will try weed out the problem better.

I checked `grep -C2 -E '(EE)|(WW)' /var/log/Xorg.0.log` and things seem
fine:

[45.181] (II) NVIDIA dlloader X Driver  440.59  Thu Jan 30 01:08:17 UTC 2020
[45.181] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
--
[45.182] (II) LoadModule: "ramdac"
[45.182] (II) Module "ramdac" already built-in
[45.183] (WW) Falling back to old probe method for modesetting
[45.183] (II) NVIDIA(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
--
[46.392] (==) NVIDIA(0): Silken mouse enabled
[46.392] (==) NVIDIA(0): DPMS enabled
[46.393] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[46.393] (II) Loading sub module "dri2"
[46.393] (II) LoadModule: "dri2"

Note, I've done no customisation to X config - trying to stick to
defaults.

xrandr confirms only one provider / hybrid is indeed off and Intel not
in use:

$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x218 cap: 0x1, Source Output crtcs: 4 outputs: 6 associated 
providers: 0 name:NVIDIA-0

I'm guessing the Lenovo P53 impliments a mux/switch to connect the
laptop panel to the NVidia card so that Intel is disabled in this mode.

And double checking, also no i915 modules are loaded:

$ lsmod | grep '^drm'
drm_kms_helper180224  1 nvidia_drm
drm   491520  10 drm_kms_helper,nvidia_drm

So there seems to be, on current Ubuntu 18.04.4 LTS (fully up to date as
of today), a 4K / UHD 60Hz issue with Nvidia, as seen in X log

[45.228] (II) NVIDIA GLX Module  440.59  Thu Jan 30 01:05:38 UTC
2020

Lastly, I think due to `needs_root_rights=yes` in
/etc/X11/Xwrapper.config, X logs to /var/log/Xorg.0.log again instead of
the X without root which used to log at  ~/.local/share/xorg/Xorg.0.log

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2020-05-03 Thread Jean-Pierre van Riel

Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.

** Attachment added: "fix-hdmi-uhd.sh"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2020-05-03 Thread Jean-Pierre van Riel

Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.

Failure loop observed:

- Failed to blit shared framebuffer: EGL failed to allocate resources for the 
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory

To summarise and share my experience of it on a Lenovo P53 and some
quirks/workarounds:

- `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed.
- However, Nvidia modeset was not enabled as yet.

$ sudo cat /sys/module/nvidia_drm/parameters/modeset
N

- Blank external screen occurs with modeset=0 (disabled)
- Then, using `prime-select nvidia`, I tried to ensure nvidia was primary
- `prime-select nvidia` sets `options nvidia-drm modeset=1` but it's not 
effective, even after I rebooted

~$ cat /lib/modprobe.d/nvidia-kms.conf
# This file was generated by nvidia-prime
# Set value to 0 to disable modesetting
options nvidia-drm modeset=1

- To make it effective, because modeset is done during initramfs part of boot, 
I ran `sudo update-initramfs -u -k all`. 
- It seems the prime-select option fails to trigger a intiramfs update 
(probably should be filed as a separate bug)
- Regardless, the blank screen issue occured on my Lenovo P53 with or without 
Nvidia KMS modeset enabled
- But one benefit of KMS modeset for Nvida is now the external display gets 
properly recognised.  /sys/class/drm/card1-HDMI-A-1/ now exists (was missing 
with Ubuntu 18.04.4 LTS default proprietary install) including the EDID data 
being read properly and X getting the actual DPI of the screen correctly.

Without nvidia modeset, as seen in `journalctl -b _COMM=gdm-x-session |
grep -C2 -E '(EE)|(WW)'`:

(WW) NVIDIA(0): Unable to get display device for DPI computation.

With nvidia modeset:

(II) NVIDIA(0): Validated MetaModes:
(II) NVIDIA(0): "DFP-3:nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160
(--) NVIDIA(0): DPI set to (139, 140); computed from "UseEdidDpi" X config

I've also found two workarounds to my issue.

1. Run a script that sets the frequency to 30HZ and then back to 60HZ
2. Switch to discrete only graphics in the BIOS

In most cases, when one is using a 2nd display, there's usually a
powersource available so the complexity of hybrid graphics isn't worth
it and I went with simply disabling hybrid graphics in the BIOS.

It's quite interesting that toggling the display refresh rate down to
30HZ and then back up to 60HZ seems to work around the problem of gnome-
shell mutter's "EGL failed to allocate resources for the requested
operation" bug.

To conclude, even with the root access workaround in place:

$ tail -n 2 /etc/X11/Xwrapper.config
# Added by xserver-xorg-video-nvidia-440
needs_root_rights=yes

I still had external display connection issues with 4K 60Hz.

This might need to be logged as different bug? I'm unsure it's GDM3s
fault given the root workaround was in place, but it's highly
related/similar.

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

1 2 3 4 5 6 >

1 - 100 of 576 matches

Mail list logo