[Desktop-packages] [Bug 1939163] Re: Screen splash when suspend or resume on I+N platform

[Daniel van Vugt]

In case it is relevant:

Please try uninstalling all Nvidia drivers (so you're left with none but
nouveau in 'lspci -k') and reboot. Does the problem still happen?

Also is there an option to disable the discrete GPU in the BIOS? What
happens if you disable it?

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

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

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

Title:
  Screen splash when suspend or resume on I+N platform

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

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

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


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

[Desktop-packages] [Bug 1928458] Re: inconsistent and unneeded password prompts

[Launchpad Bug Tracker]

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

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

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

Title:
  inconsistent and unneeded password prompts

Status in gnome-keyring package in Ubuntu:
  Expired

Bug description:
  On several occasions I have experienced that gnome-keyring prompts to be 
unlocked when I believe it should not.
  * I have Spotify installed as a .deb. When starting Spotify, on some 
occasions gnome-keyring prompts to be unlocked, on others not. This behaviour 
has been observed both when gnome-keyring has been unlocked in advance as well 
as when not. I have not added my Spotify password to gnome-keyring.
  * same behaviour as described above when starting Lutris. Did also not add 
any Lutris related passwords to gnome-keyring.
  * similar behaviour is observed with other applications where no passwords 
have been added to gnome-keyring.

  Whether or not I actually unlock the keyring, it has no functional
  impact in these cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 13:24:00 2021
  InstallationDate: Installed on 2020-05-09 (369 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1939163] Re: Screen splash when suspend or resume on I+N platform

[Daniel van Vugt]

It's likely that "I+N" is not relevant. Only the Intel GPU is used to
draw the shell and login screen.

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

Title:
  Screen splash when suspend or resume on I+N platform

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

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

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


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

[Desktop-packages] [Bug 1903936] Re: Update to 1.58

[Robert Ancell]

Updated to snapd-glib 1.58-0ubuntu0.18.04.0 on bionic and all
dependencies are working.

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

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

Title:
  Update to 1.58

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released
Status in snapd-glib source package in Groovy:
  Fix Released
Status in snapd-glib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Changes to error message carry low risk of introducing an issue if such an 
error occurred. GIR annotation changes fix a call that was previously broken, 
and is unlikely to make that any worse.
  Risks are mitigated by automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+subscriptions


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

[Desktop-packages] [Bug 1939186] Re: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts

[Daniel van Vugt]

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

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

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

Title:
  Wayland causes arrow key scroll lock behavior when using Japanese or
  US-intl keyboard layouts

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 21.04 with Wayland as default, the arrow
  keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as
  though scroll lock is toggled on (even though the scroll lock light is
  not on) instead of moving the cell in focus. (This happens with the
  US-intl keyboard layout too.) The arrow keys work as expected in other
  programs though, including LibreOffice Writer.

  If I switch to the default US keyboard layout, the arrow keys on the
  same keyboard work properly: moving the cell in focus.

  I tried removing grp_led:scroll from
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in
  /etc/default/keyboard, but that did not fix it.

  I also tried uninstalling LibreOffice and removing the config files as
  explained here, but that didn't fix it either.

  This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard
  arrow keys work correctly in LibreCalc on Windows, so the issue
  appears to be specific to Ubuntu 21.04, not LibreOffice, nor this
  keyboard.

  As a workaround, if I start the session with Xorg instead, the arrow
  keys work as expected with any keyboard layout. Therefore, this bug
  appears to be related to Wayland.

  I was encouraged to file this bug report for gnome-shell in the
  comments on this AskUbuntu post:
  https://askubuntu.com/questions/1356052/why-do-japanese-keyboard-
  arrow-keys-scroll-in-libreoffice-calc-but-move-cell-
  wit/1356059?noredirect=1#comment2321519_1356059

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 12:18:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (548 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515

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


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

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

[koyakun]

Workaround: Use Xorg (not Wayland)

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

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


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

[Desktop-packages] [Bug 1939163] Re: Screen splash when suspend or resume on I+N platform

[Bin Li]

@Daniel,

 Thanks for your feedback, I checked bug 1923335, the description is
similar, but it's not a I+N platform, and from my side, when I switch to
Power Saving Mode to use Intel, I could not reproduce this issue.
Thanks.

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

Title:
  Screen splash when suspend or resume on I+N platform

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

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

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


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

[Desktop-packages] [Bug 1939186] Re: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts

[koyakun]

Issue ID:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1909

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

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

Title:
  Wayland causes arrow key scroll lock behavior when using Japanese or
  US-intl keyboard layouts

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 21.04 with Wayland as default, the arrow
  keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as
  though scroll lock is toggled on (even though the scroll lock light is
  not on) instead of moving the cell in focus. (This happens with the
  US-intl keyboard layout too.) The arrow keys work as expected in other
  programs though, including LibreOffice Writer.

  If I switch to the default US keyboard layout, the arrow keys on the
  same keyboard work properly: moving the cell in focus.

  I tried removing grp_led:scroll from
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in
  /etc/default/keyboard, but that did not fix it.

  I also tried uninstalling LibreOffice and removing the config files as
  explained here, but that didn't fix it either.

  This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard
  arrow keys work correctly in LibreCalc on Windows, so the issue
  appears to be specific to Ubuntu 21.04, not LibreOffice, nor this
  keyboard.

  As a workaround, if I start the session with Xorg instead, the arrow
  keys work as expected with any keyboard layout. Therefore, this bug
  appears to be related to Wayland.

  I was encouraged to file this bug report for gnome-shell in the
  comments on this AskUbuntu post:
  https://askubuntu.com/questions/1356052/why-do-japanese-keyboard-
  arrow-keys-scroll-in-libreoffice-calc-but-move-cell-
  wit/1356059?noredirect=1#comment2321519_1356059

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 12:18:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (548 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515

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


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

[Desktop-packages] [Bug 1939163] Re: Screen splash when suspend or resume on I+N platform

[Bin Li]

** Tags added: oem-priority originate-from-1938768 sutton

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

Title:
  Screen splash when suspend or resume on I+N platform

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

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

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


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

[Desktop-packages] [Bug 1844934] Re: screen jitter after long idle

[Daniel van Vugt]

If the problem is still happening then please try disabling PSR:
  
  i915.enable_psr=0

** Changed in: oem-priority
   Status: Confirmed => Incomplete

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

Title:
  [Dell XPS 13 9380] screen jitter after long idle

Status in OEM Priority Project:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It's 1st time happens on my xps13 9380 with bionic + oem kernel 
4.15.0-1056-oem.
  I have updated to 1056 from 1050 for several days, this issue not happens for 
these days and not experienced it on 1050 as well. So, looks it's just randomly 
happens or I can not find a static way to reproduce it.

  I also not sure if unattended upgrade bring in some regression.

  So, my plan would be
  1. do apt full-upgrade, and if it still can be reproduce then.
  2. try mainline kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1056.65-oem 4.15.18
  Uname: Linux 4.15.0-1056-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 00:14:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: Installed on 2019-08-11 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1056-oem 
root=UUID=d6c42edb-0a08-49cc-89e9-fe4df2d0c5e1 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

[Desktop-packages] [Bug 1844934] Re: screen jitter after long idle

[Daniel van Vugt]

See also bug 1939211

** Summary changed:

- screen jitter after long idle
+ [Dell XPS 13 9380] screen jitter after long idle

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

Title:
  [Dell XPS 13 9380] screen jitter after long idle

Status in OEM Priority Project:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It's 1st time happens on my xps13 9380 with bionic + oem kernel 
4.15.0-1056-oem.
  I have updated to 1056 from 1050 for several days, this issue not happens for 
these days and not experienced it on 1050 as well. So, looks it's just randomly 
happens or I can not find a static way to reproduce it.

  I also not sure if unattended upgrade bring in some regression.

  So, my plan would be
  1. do apt full-upgrade, and if it still can be reproduce then.
  2. try mainline kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1056.65-oem 4.15.18
  Uname: Linux 4.15.0-1056-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 00:14:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: Installed on 2019-08-11 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1056-oem 
root=UUID=d6c42edb-0a08-49cc-89e9-fe4df2d0c5e1 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

[Desktop-packages] [Bug 1939228] Re: screen tearing and redraw in ubuntu 20.04 LTS

[Daniel van Vugt]

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

The kernel in Ubuntu 20.04 got upgraded recently, so now it has the same
bug as 21.04 :(

Please keep using bug 1937072

** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu)

** This bug has been marked a duplicate of bug 1937072
   [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

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

Title:
  screen tearing and redraw in ubuntu 20.04 LTS

Status in linux-hwe-5.11 package in Ubuntu:
  New

Bug description:
  I have used ubuntu 21.04 before on this device and  reported a bug and
  it is solved by making psr value to 0. but in ubuntu 20.04LTS is not
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-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..30.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:30: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.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Aug  8 13:57:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-08-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82A1
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN32WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939228/+subscriptions


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

[Desktop-packages] [Bug 1939221] Re: Screen Freeze then system without response

[Daniel van Vugt]

Next time the freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run this command:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also follow these instructions to check for any crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Screen Freeze then system without response

Status in Ubuntu:
  Incomplete

Bug description:
  It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking 
at first i watch video then put it on full screen (especially in browser 
chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" 
or try "Ctrl+alt+F2" to text mode.
  then I search google and install amd's opencl driver to replace intel. but, 
it just better then previous.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.9-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 
5.4.41
  Uname: Linux 5.4.0-7634-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 13:48:50 2021
  InstallationDate: Installed on 2019-11-23 (623 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1939202] Re: Driver no aparece ni Intel ni nvidia

[Daniel van Vugt]

According to the Nvidia web site, the Geforce 820M GPU requires driver
version 430. But you have driver 460 installed which does not support
the Geforce 820M GPU:

[4.712300] NVRM: The NVIDIA GeForce 820M GPU installed in this system is
   NVRM:  supported through the NVIDIA 390.xx Legacy drivers. Please
   NVRM:  visit http://www.nvidia.com/object/unix.html for more
   NVRM:  information.  The 460.91.03 NVIDIA driver will ignore
   NVRM:  this GPU.  Continuing probe...

You will need to uninstall the version 460 driver packages you have and
then install 430 instead:

  sudo apt update
  sudo apt install nvidia-driver-430

If that doesn't work then try:

  sudo apt install nvidia-driver-390



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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  Driver no aparece ni Intel ni nvidia

Status in Ubuntu:
  Invalid

Bug description:
  Muy Buenas en información de software mas controladores, no aparece
  nada sin embargo nvidia x  lo puse como por demanda es decir intel en
  segundo lugar y baje  la resolución de pantalla a 1080x 748 ayuda
  donde estan los controladores? gracias

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 17:13:30 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.91.03, 5.11.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:228a]
 Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:228a]
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b40a Chicony Electronics Co., Ltd USB2.0 HD UVC 
WebCam
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550LD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=34ca3807-bd85-48be-8355-4184cd90c75e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LD.302:bd04/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LD
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel

[Daniel van Vugt]

Yes please try turning off panel self refresh again by adding this
kernel parameter:

  i915.enable_psr=0

** Summary changed:

- Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
+ [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 
kernel

** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu)

** Changed in: linux-hwe-5.11 (Ubuntu)
   Status: New => Incomplete

** Tags added: regression-update

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

Title:
  [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel
  to 5.11 kernel

Status in linux-hwe-5.11 package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the upgrade to the 5.8 series kernel to the 5.11 series kernel,
  I have noticed some screen flickering. I had the same problem
  previously on Fedora after upgrading to the 5.0 series kernel, but
  this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series
  kernels. On Fedora, it was fixed by turning off panel self-refresh on
  my Dell XPS 13 9380. I can try that again here if you all think it
  would be a useful piece of information. In the Fedora bug, it was
  reported that this problem is fixed in the 5.13 kernel. Let me know
  whatever else I can do.

  Thanks!
  Ben

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 18:56:38 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2021-06-24 (44 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 13 9380
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  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/linux-hwe-5.11/+bug/1939211/+subscriptions


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

[Desktop-packages] [Bug 1939186] Re: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts

[Daniel van Vugt]

Please report the issue to the developers at:

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

and then tell us the new issue ID.


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

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

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

Title:
  Wayland causes arrow key scroll lock behavior when using Japanese or
  US-intl keyboard layouts

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 21.04 with Wayland as default, the arrow
  keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as
  though scroll lock is toggled on (even though the scroll lock light is
  not on) instead of moving the cell in focus. (This happens with the
  US-intl keyboard layout too.) The arrow keys work as expected in other
  programs though, including LibreOffice Writer.

  If I switch to the default US keyboard layout, the arrow keys on the
  same keyboard work properly: moving the cell in focus.

  I tried removing grp_led:scroll from
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in
  /etc/default/keyboard, but that did not fix it.

  I also tried uninstalling LibreOffice and removing the config files as
  explained here, but that didn't fix it either.

  This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard
  arrow keys work correctly in LibreCalc on Windows, so the issue
  appears to be specific to Ubuntu 21.04, not LibreOffice, nor this
  keyboard.

  As a workaround, if I start the session with Xorg instead, the arrow
  keys work as expected with any keyboard layout. Therefore, this bug
  appears to be related to Wayland.

  I was encouraged to file this bug report for gnome-shell in the
  comments on this AskUbuntu post:
  https://askubuntu.com/questions/1356052/why-do-japanese-keyboard-
  arrow-keys-scroll-in-libreoffice-calc-but-move-cell-
  wit/1356059?noredirect=1#comment2321519_1356059

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  7 12:18:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (548 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515

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


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

[Desktop-packages] [Bug 1939163] Re: Screen splash when suspend or resume on I+N platform

[Daniel van Vugt]

I wonder if this is related to bug 1923335. That also has an issue with
the screen flashing back on when it should be off.

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

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

** Tags added: focal

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

Title:
  Screen splash when suspend or resume on I+N platform

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

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

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


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

[Desktop-packages] [Bug 1939254] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Chris Guiver]

Original filing -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939251

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  My two older Zotacs use the NV 340.108 driver and both are having the
  same issue. After the latest dist-upgrade they boot fine but don't
  display video, just a blank black screen with a randomly blinking
  cursor. They're headless but I got into both with ssh in order to
  uninstall the NV driver and now both boot normally but just use the
  Nuveau default driver. Unfortunately I can't use either computer like
  this (no NV driver). After I had uninstalled the nvidia driver and
  rebooted I tried installing the NV driver with Software-Updater but
  then received this warning after a few minutes:

  Error while applying changes
  pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
  OK

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-25-generic
  Date: Sat Aug  7 12:08:14 2021
  InstallationDate: Installed on 2021-02-24 (165 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1939173] Re: [HP 120-1100eo API] Screen flickering white vertical lines

[Daniel van Vugt]

I also wonder if this might be another HP BIOS bug like bug 1906086...
Please try changing your BIOS mode to legacy BIOS (or to UEFI if it's
already legacy). But be warned; you may need to reinstall Ubuntu in
order to boot again after changing the setting.

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

Title:
  [HP 120-1100eo API] Screen flickering white vertical lines

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The screen on my HP AIO computer flickers. I'm able to browse the
  computer, but it's giving me headache.

  Flickering consists pattern of 2cm height white vertical pixel lines
  (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section.

  Flicker also has 1px lines with dashes ending them about 10cm from
  left of the screen and 2cm from right of the screen.

  Mathematically letter W being 100% of screen width in above
  description.

  Flickering seems to be consistent to screen refresh state (~60Hz).
  Changing refresh rate does not affect in to amount of flickering.

  Same thing not happening in Windows nor BIOS. Even though this looks a
  LOT like a hardware/wiring issue.

  Also the problem is visible in Ubuntu installer, but not in graphic
  safe one.

  Best regards, korho.

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

  $ apt-cache policy xorg
  xorg:
    Installed: 1:7.7+19ubuntu14
    Candidate: 1:7.7+19ubuntu14
    Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 23:04:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ac5]
  InstallationDate: Installed on 2021-08-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard 120-1100eo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: LEO_707
  dmi.board.name: 2AC5
  dmi.board.vendor: Quanta
  dmi.board.version: 100
  dmi.chassis.asset.tag: CZC2128RP3
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 120-1100eo
  dmi.product.sku: H1E79EA#UUW
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1939173] Re: [HP 120-1100eo API] Screen flickering white vertical lines

[Daniel van Vugt]

Thanks for the bug report. You appear to be using Wayland at the moment.
Can you please try logging into Xorg instead? It's the option on the
login screen titled "Ubuntu" instead of "Ubuntu on Wayland".

** Summary changed:

- Screen flickering white vertical lines
+ [HP 120-1100eo API] Screen flickering white vertical lines

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

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

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

Title:
  [HP 120-1100eo API] Screen flickering white vertical lines

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The screen on my HP AIO computer flickers. I'm able to browse the
  computer, but it's giving me headache.

  Flickering consists pattern of 2cm height white vertical pixel lines
  (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section.

  Flicker also has 1px lines with dashes ending them about 10cm from
  left of the screen and 2cm from right of the screen.

  Mathematically letter W being 100% of screen width in above
  description.

  Flickering seems to be consistent to screen refresh state (~60Hz).
  Changing refresh rate does not affect in to amount of flickering.

  Same thing not happening in Windows nor BIOS. Even though this looks a
  LOT like a hardware/wiring issue.

  Also the problem is visible in Ubuntu installer, but not in graphic
  safe one.

  Best regards, korho.

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

  $ apt-cache policy xorg
  xorg:
    Installed: 1:7.7+19ubuntu14
    Candidate: 1:7.7+19ubuntu14
    Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 23:04:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:2ac5]
  InstallationDate: Installed on 2021-08-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard 120-1100eo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: LEO_707
  dmi.board.name: 2AC5
  dmi.board.vendor: Quanta
  dmi.board.version: 100
  dmi.chassis.asset.tag: CZC2128RP3
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 120-1100eo
  dmi.product.sku: H1E79EA#UUW
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1937090] Re: Opening a very wide window crashes the entire system

[Daniel van Vugt]

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

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

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

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

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


** Tags added: focal

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

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

Title:
  Opening a very wide window crashes the entire system

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04, programming in python and by mixing up left/right and
  up/down in matrix operations created an array of size 1x409600 instead
  of 2048x200.

  When I tried to show the data as an image Ubuntu completely crashes.
  Unable to get any form of crash report, only thing I could do was hard
  reset my PC.

  Here is some code that reproduces the problem:

  
  import cv2
  import numpy as np

  cv2.imshow("window name", np.zeros((1, 2048*200)))
  cv2.waitKey()

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


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

[Desktop-packages] [Bug 1914915] Re: Sound or Audio is breaking

[Daniel van Vugt]

** Tags added: vmware

** Summary changed:

- Sound or Audio is breaking 
+ [vmware] Sound or Audio is breaking

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

Title:
  [vmware] Sound or Audio is breaking

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I am watching videos sound is breaking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  balashanmugam   1437 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb  7 15:27:47 2021
  InstallationDate: Installed on 2021-02-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  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: 08/10/2020
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.16722896.B64.2008100651
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Desktop-packages] [Bug 1891429] Re: Unable to use any application or return to homescreen after opening application menu

[Daniel van Vugt]

Thanks for the bug report. Please tell us if the problem is still
occurring and if so then run this command to collect more system info:

  apport-collect 1891429

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

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

Title:
  Unable to use any application or return to homescreen after opening
  application menu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  OS- Ubuntu 20.04
  Comfortably using since 25 April 2020

  The issue started yesterday.
  After clicking the show application button on the taskbar, there is no way to 
return back to the home screen again. There is an extra black box available in 
the right corner. I am able to open the application but not use them.
  On opening any of my favorite applications from the taskbar that application 
freezes and a red circle with white cross appear to kill this program. No even 
the close, or minimize commands word expect that big cross on the left top. 
This is sometimes sorted by restarting but sometimes even that doesn't help.
  Please help me sort this issue. Its urgent.

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


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

[Desktop-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

[Chris Guiver]

** Package changed: gnome-terminal (Ubuntu) => e2fsprogs (Ubuntu)

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

Title:
  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hello
  This problem did not occur on my computer.

  https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

  It occurs in users who are not competent.
  This week, the French forum collapsed over this incident.

  I think changing the advice phrase might improve understanding of the
  action to be taken.

  Can these lines
  "   ( i.e.. without -a or -p options) 
  fsck existed with status code 4
  The root file system on /dev/ requires a manual fsck"
  become
  "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 15:16:28 2021
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-08-02 (370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


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

[Desktop-packages] [Bug 1939243] Re: i don´t know

[Daniel van Vugt]

What kind of problem are you experiencing?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  i don´t know

Status in Ubuntu:
  Incomplete

Bug description:
  i don´t know

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Sun Aug  8 13:11:24 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1162]
  InstallationDate: Installed on 2016-12-02 (1710 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Itautec S.A. Infoway
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007
  dmi.board.name: ST 1350
  dmi.board.vendor: Itautec S.A.
  dmi.board.version: ST-1350 Padrao 02(Itautec_M)
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrItautecST1350BIOS0203-SL2,06/27/2007:bd06/27/2007:svnItautecS.A.:pnInfoway:pvrCorp:rvnItautecS.A.:rnST1350:rvrST-1350Padrao02(Itautec_M):cvnChassisManufacture:ct3:cvr:
  dmi.product.name: Infoway
  dmi.product.version: Corp
  dmi.sys.vendor: Itautec S.A.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
  xserver.bootTime: Sun Aug  8 13:01:17 2021
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputSIGMACHIP Usb Mouse  MOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.11-1ubuntu1.1

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


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

[Desktop-packages] [Bug 1939254] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[marcw]

Public bug reported:

My two older Zotacs use the NV 340.108 driver and both are having the
same issue. After the latest dist-upgrade they boot fine but don't
display video, just a blank black screen with a randomly blinking
cursor. They're headless but I got into both with ssh in order to
uninstall the NV driver and now both boot normally but just use the
Nuveau default driver. Unfortunately I can't use either computer like
this (no NV driver). After I had uninstalled the nvidia driver and
rebooted I tried installing the NV driver with Software-Updater but then
received this warning after a few minutes:

Error while applying changes
pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
OK

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-25-generic
Date: Sat Aug  7 12:08:14 2021
InstallationDate: Installed on 2021-02-24 (165 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageVersion: 340.108-0ubuntu5.20.04.2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  My two older Zotacs use the NV 340.108 driver and both are having the
  same issue. After the latest dist-upgrade they boot fine but don't
  display video, just a blank black screen with a randomly blinking
  cursor. They're headless but I got into both with ssh in order to
  uninstall the NV driver and now both boot normally but just use the
  Nuveau default driver. Unfortunately I can't use either computer like
  this (no NV driver). After I had uninstalled the nvidia driver and
  rebooted I tried installing the NV driver with Software-Updater but
  then received this warning after a few minutes:

  Error while applying changes
  pk-client-error-quark: Error while installing package: installed nvidia-340 
package post-installation script subprocess returned error exit status 10(313)
  OK

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-25-generic
  Date: Sat Aug  7 12:08:14 2021
  InstallationDate: Installed on 2021-02-24 (165 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working

[ali]

Having the same problem with a 2017 12” Macbook (the Macbook10,2). The
microphone shows up as “(unplugged)” in pavucontrol and pacmd regardless
of if I have the headset plugged into the combo jack or not. Headphones
are detected and work. The internal mic is still accessible and the
Microphone input seems to be mirrorring it (could be to do with some
chip-level switching that somehow doesn’t happen on Linux?). I’ve tried
inputting all choices of model available in the CS4208 quirk list for
PulseAudio (there isn’t one for my particular model) into alsa-base.conf
and nothing has changed (having nothing in alsa-base.conf, which I did
before attempting this fix, also makes no difference). I’m running
Debian 10 with kernel 4.19.0-17-amd64.

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

Title:
  MacBook Air 6,2 TRRS Headset Mic Not Working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus
  Logic CS4208 and would love to get the microphone part of the TRRS
  connector working. Mac OS picks up and utilizes the TRRS headset mic
  without issue so I know the hardware is a go.

  With the headset plugged in, running sudo hdajacksensetest -a results
  in:

  Pin 0x05 ( Digital Out, HDMI): present = No
  Pin 0x06 ( Digital Out, HDMI): present = No
  Pin 0x07 ( Digital Out, HDMI): present = No

  AlsaInfo output here:
  http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83

  I opened up hdajackretask to find four pins:
  Green Headphone
  Pin ID: 0x10
  Headphone

  Internal Speaker
  Pin ID: 0x12
  Internal speaker

  Pink Mic
  Pin ID: 0x18
  Not connected

  Internal Mic
  Pin ID: 0x1c
  Internal mic

  Unplugging and replugging the headset changes the Output device in
  sound settings from Headphones to Speakers so that works, but nothing
  in the input tab ever changes. It always lists two devices: Internal
  Microphone and Microphone. Both of these seem to actually be the
  internal microphone in the mac - either works without the headset
  connected at all.

  So I'm not really sure how to proceed from here, but I'd be happy to
  run whatever diagnostic tests might prove useful and/or even
  contribute code toward a fix - but I just have no idea where to start.
  Is it as simple as just finding the right pin and telling the system
  to use it as a microphone?

  Similar bug report here:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494

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


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

[Desktop-packages] [Bug 1939206] Re: Missing translations

[Gunnar Hjalmarsson]

Most of those strings are present in Launchpad and recently translated
by you.

I'd suggest that we wait until the next update of the language packs. If
some strings keep being untranslated after that, it may be motivated to
investigate further.

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

Title:
  Missing translations

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

Bug description:
  Hello,

  I hope this is the proper place to report this bug.
  I am using the daily built and I see that some strings are not translated but 
they are not available on Launchpad for translation.

  Also, I noticed that the language packs are not updated every 2 weeks
  like I read somewhere.

  Best regards

  Quentin

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


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

[Desktop-packages] [Bug 1620085] Re: --exclude-if-present gives OSError looking for tag in locked folders

[Jesse Hines]

I've tried both the snap distribution which is at 0.8.19 and the apt
distribution which is at 0.8.12 and both print the same error.

Everything still works fine so its only a cosmetic issue though.

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

Title:
  --exclude-if-present gives OSError looking for tag in locked folders

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Zesty:
  Fix Released

Bug description:
  As per:
  http://lists.nongnu.org/archive/html/duplicity-talk/2016-08/msg9.html

  "I want to send a backup with --exclude-if-present=TAG and
  --include-filelist.
  The folder /src/folder is not accessible (mode 750, not owner, not
  member of group). This folder is excluded by way of '- **/folder' in
  the include filelist. Does the selection process resolve
  exclude-if-present=TAG before it looks at include/exclude filelists
  anyway ?

  duplicity 0.7.10 (python 2.7.12) fails with

  OSError: [Errno 13] Permission denied: '/src/folder/TAG'

  duplicity 0.7.06 prints

  Error accessing possibly locked file /src/folder

  but it isn't a showstopper."

  I can confirm this is the case. The reason is that --exclude-if-
  present looks in each folder within the backup tree looking for the
  excluded tag, even if that folder is later excluded.

  The difference between version 0.7.06 and 0.7.10 is likely caused by my rev 
1224:
  http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1224
  which fixed Bug #1089131 by removing the readability check when the directory 
was first scanned and instead moved it to when the file comes to be included by 
the Select function. The issue here is that the function that deals with 
--exclude-if-present checks for the tag by simply trying to access it, without 
checking if it has access, giving an OSError.

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


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

[Desktop-packages] [Bug 1939206] Re: Missing translations

[Quentin PAGÈS]

Hello,
there is "Keyboard" on the side panel and then on the main content:
Keyboard as a title for the section, then "Switch input sources individually 
for each window"
"Keyboard Shortcut" "This can be changed in Customize Shortcuts" "Type Special 
Characters", "Alternate Characters Key" "Hold down and tape to enter different 
characters" "Layout default" (twice) and finally "Customize Shortcuts".
I hope it helps

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

Title:
  Missing translations

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

Bug description:
  Hello,

  I hope this is the proper place to report this bug.
  I am using the daily built and I see that some strings are not translated but 
they are not available on Launchpad for translation.

  Also, I noticed that the language packs are not updated every 2 weeks
  like I read somewhere.

  Best regards

  Quentin

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


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

[Desktop-packages] [Bug 1939206] Re: Missing translations

[Gunnar Hjalmarsson]

On 2021-08-07 19:02, Quentin PAGÈS wrote:
> I hope this is the proper place to report this bug.

Well, the screenshot is from a standard-Ubuntu installation, i.e. the
related package is gnome-control-center and not unity-control-center.

> I am using the daily built and I see that some strings are not
> translated but they are not available on Launchpad for translation.

Which strings exactly are those?

> Also, I noticed that the language packs are not updated every 2 weeks
> like I read somewhere.

I wrote that on the mailing list, but it's correct that it has not
worked that way for impish so far. Possibly that's the reason why you
see untranslated strings in the daily build.

I'll try to find out the reason.

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

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

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

Title:
  Missing translations

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

Bug description:
  Hello,

  I hope this is the proper place to report this bug.
  I am using the daily built and I see that some strings are not translated but 
they are not available on Launchpad for translation.

  Also, I noticed that the language packs are not updated every 2 weeks
  like I read somewhere.

  Best regards

  Quentin

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


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

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

[Brian]

I hope I did this properly, but I changed status back to new. This is
still an issue, and if more info is needed I can provide it, at least
from my end of things.

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: Incomplete => New

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

Title:
  GPU lockup ring 0 stalled for more than X msec

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 [radeon]
do_vfs_ioctl+0xa9/0x640
? __schedule+0x2b0/0x670
ksys_ioctl+0x75/0x80
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x130
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
  ppa but that made no difference. It appears to be a bug in radeon.

  Nothing specific makes this happen, just regular usage with a
  compositing window manager. I'm not playing games or particularly
  exercising the GPU. The last two times I was just reading in web
  browser. It's also happened in the middle of the night while I was
  asleep. Sometimes I have a few days uptime, sometimes it happens in
  less than 24 hours from boot.

  This never happened before the radeon update mentioned on the first
  line.

  I'll attach two files of dmesg output. As per
  https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
  started apport for next time it happens.

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


-- 
Mailing list: 

[Desktop-packages] [Bug 1939243] [NEW] i don´t know

[joao dos santos]

Public bug reported:

i don´t know

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Sun Aug  8 13:11:24 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1162]
InstallationDate: Installed on 2016-12-02 (1710 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Itautec S.A. Infoway
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007
dmi.board.name: ST 1350
dmi.board.vendor: Itautec S.A.
dmi.board.version: ST-1350 Padrao 02(Itautec_M)
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrItautecST1350BIOS0203-SL2,06/27/2007:bd06/27/2007:svnItautecS.A.:pnInfoway:pvrCorp:rvnItautecS.A.:rnST1350:rvrST-1350Padrao02(Itautec_M):cvnChassisManufacture:ct3:cvr:
dmi.product.name: Infoway
dmi.product.version: Corp
dmi.sys.vendor: Itautec S.A.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
xserver.bootTime: Sun Aug  8 13:01:17 2021
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputSIGMACHIP Usb Mouse  MOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.11-1ubuntu1.1

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


** Tags: amd64 apport-bug hirsute 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/1939243

Title:
  i don´t know

Status in xorg package in Ubuntu:
  New

Bug description:
  i don´t know

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Sun Aug  8 13:11:24 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1162]
  InstallationDate: Installed on 2016-12-02 (1710 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Itautec S.A. Infoway
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007
  dmi.board.name: ST 1350
  dmi.board.vendor: Itautec S.A.
  dmi.board.version: ST-1350 Padrao 02(Itautec_M)
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: 
  dmi.modalias: 

[Desktop-packages] [Bug 908791] Re: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place

[josh]

a few years later, i am still seeing this issue running as a normal
(non-root) user w/most recent pkgs for 16.04.3LTS.

gvfs-backends was not installed automatically w/deja-dup pkg installed
today (almost 10yr after this issue was opened).

i located this ticket via this post, figured i'd let you know it's still
out there.

https://askubuntu.com/questions/459679/deja-dup-ssh-method-doesnt-work-
writes-locally-instead

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

Title:
  Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-
  Dup launch place

Status in Déjà Dup:
  Expired
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  1. I'm using up to date ArchLinux, x86_64.
  2.  20.2-2
  3. org.gnome.DejaDup backend 'file'
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD', '/home/ernestas/dw', 
'/home/ernestas/Muzika', '/home/ernestas/books']
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup last-backup '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2011-12-26T15:08:43.807421Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup prompt-check ''
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup welcomed true
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path 
'ftp://ernes...@home.versme.net:21/home/ernestas/backup/'
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.Rackspace container 'pluto'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'pluto'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.U1 folder '/deja-dup/pluto'

  **

  Let's say I launch Deja-Dup in home directory /home/ernestas. Then it creates 
/home/ernestas/sftp:/ or /home/ernestas/ftp:/ directories at which it places 
backups.
  What dependencies is Deja-Dup missing and why isn't it displaying any errors 
about that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/908791/+subscriptions


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

[Desktop-packages] [Bug 1939226] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Jeffrey Pych]

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

** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is 
invalid)

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  on ubuntu 20.04.2 TLS

  during compilation of nvidia-340
  in make file at line 11096
  no file in asm/kmap_types.h because they are no directory asm

  In file included from /var/lib/dkms/nvidia-340/340.108/build/nv-frontend.c:13:
  /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h: At top level:
  /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h:122:10: fatal error: 
asm/kmap_types.h: Aucun fichier ou dossier de ce type
122 | #include  /* page table entry lookup
  */
|  ^~
  compilation terminated.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-25-generic
  Date: Sun Aug  8 09:12:09 2021
  InstallationDate: Installed on 2021-01-15 (204 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1939220] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Jeffrey Pych]

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

** This bug has been marked a duplicate of bug 1938978
nvidia-340 kernel module failed to build (ERROR: Kernel configuration is 
invalid)

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  nvidia graphic problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-25-generic
  Date: Sun Aug  8 11:14:11 2021
  InstallationDate: Installed on 2021-06-01 (67 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

[geole0]

https://forum.ubuntu-fr.org/viewtopic.php?id=2066134
https://forum.ubuntu-fr.org/viewtopic.php?id=2066096
https://forum.ubuntu-fr.org/viewtopic.php?id=2066153

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

Title:
  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hello
  This problem did not occur on my computer.

  https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

  It occurs in users who are not competent.
  This week, the French forum collapsed over this incident.

  I think changing the advice phrase might improve understanding of the
  action to be taken.

  Can these lines
  "   ( i.e.. without -a or -p options) 
  fsck existed with status code 4
  The root file system on /dev/ requires a manual fsck"
  become
  "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 15:16:28 2021
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-08-02 (370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


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

[Desktop-packages] [Bug 1939238] [NEW] UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

[geole0]

Public bug reported:

Hello
This problem did not occur on my computer.

https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

It occurs in users who are not competent.
This week, the French forum collapsed over this incident.

I think changing the advice phrase might improve understanding of the
action to be taken.

Can these lines
"   ( i.e.. without -a or -p options) 
fsck existed with status code 4
The root file system on /dev/ requires a manual fsck"
become
"execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-terminal 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  8 15:16:28 2021
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2020-08-02 (370 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hello
  This problem did not occur on my computer.

  https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

  It occurs in users who are not competent.
  This week, the French forum collapsed over this incident.

  I think changing the advice phrase might improve understanding of the
  action to be taken.

  Can these lines
  "   ( i.e.. without -a or -p options) 
  fsck existed with status code 4
  The root file system on /dev/ requires a manual fsck"
  become
  "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 15:16:28 2021
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-08-02 (370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


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

[Desktop-packages] [Bug 1620085] Re: --exclude-if-present gives OSError looking for tag in locked folders

[Michael Terry]

Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.

Maybe we would need a smarter fix to avoid both the non-fatal and fatal
errors.

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

Title:
  --exclude-if-present gives OSError looking for tag in locked folders

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Zesty:
  Fix Released

Bug description:
  As per:
  http://lists.nongnu.org/archive/html/duplicity-talk/2016-08/msg9.html

  "I want to send a backup with --exclude-if-present=TAG and
  --include-filelist.
  The folder /src/folder is not accessible (mode 750, not owner, not
  member of group). This folder is excluded by way of '- **/folder' in
  the include filelist. Does the selection process resolve
  exclude-if-present=TAG before it looks at include/exclude filelists
  anyway ?

  duplicity 0.7.10 (python 2.7.12) fails with

  OSError: [Errno 13] Permission denied: '/src/folder/TAG'

  duplicity 0.7.06 prints

  Error accessing possibly locked file /src/folder

  but it isn't a showstopper."

  I can confirm this is the case. The reason is that --exclude-if-
  present looks in each folder within the backup tree looking for the
  excluded tag, even if that folder is later excluded.

  The difference between version 0.7.06 and 0.7.10 is likely caused by my rev 
1224:
  http://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1224
  which fixed Bug #1089131 by removing the readability check when the directory 
was first scanned and instead moved it to when the file comes to be included by 
the Select function. The issue here is that the function that deals with 
--exclude-if-present checks for the tag by simply trying to access it, without 
checking if it has access, giving an OSError.

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


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

[Desktop-packages] [Bug 1939206] Re: Missing translations

[lotuspsychje]

Thank you for reporting this bug and make Ubuntu better!

to drag useful info about your system into this bug please
run apport-collect 1939206 from a terminal, so developers can debug a better way

Thank you!

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

Title:
  Missing translations

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

Bug description:
  Hello,

  I hope this is the proper place to report this bug.
  I am using the daily built and I see that some strings are not translated but 
they are not available on Launchpad for translation.

  Also, I noticed that the language packs are not updated every 2 weeks
  like I read somewhere.

  Best regards

  Quentin

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


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

[Desktop-packages] [Bug 1936254] Re: [snap] 7.2.0.1 build from tarball fails to find modules

[Adolfo Jayme]

** Changed in: libreoffice (Ubuntu)
   Status: New => Triaged

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

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

Title:
  [snap] 7.2.0.1 build from tarball fails to find modules

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  The LO snap builds from the upstream tarballs. In this case, we're building 
from (in the snapcraft.yaml):
  
http://download.documentfoundation.org/libreoffice/src/7.2.0/libreoffice-7.2.0.1.tar.xz

  The snap repo commit being built:
  https://git.launchpad.net/~hellsworth/+git/libreoffice-
  snap/commit/?id=d8a871e0d330928885201dcaafdec30dfb0c7b61

  The build failure:
  
https://launchpadlibrarian.net/548455036/buildlog_snap_ubuntu_focal_amd64_libreoffice-7.2-wip_BUILDING.txt.gz

  Locally, I've reproduced this failure and the modules are there, just
  not in the expected place.

  snapcraft-libreoffice # find . -name Module_helpcontent2.mk
  
./parts/libreoffice/build/src/libreoffice-help-7.2.0.1/helpcontent2/Module_helpcontent2.mk

  Looking through the libreoffice source changes, I believe this commit is the 
culprit:
  
https://cgit.freedesktop.org/libreoffice/core/commit/?id=f3b7dc649bc384be6000d98a87763cab26fe3f32

  Reverting this commit in a patch gets past the issue and the build
  resumes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1936254/+subscriptions


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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[SunBear]

For Ubuntu 20.04, I have also noticed that both snap installed Chromium
and Brave Web browsers fails to work with the gnome-shell-integration
extension.

In the case of Brave, this issue can be overcome by following their instruction 
on installing the .deb versions of brave-browser and brave-keyring files. 
$ sudo apt install apt-transport-https curl
$ sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg 
https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg
$ echo "deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg 
arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main"|sudo 
tee /etc/apt/sources.list.d/brave-browser-release.list
$ sudo apt update
$ sudo apt install brave-browser

However, the chromium-browser does not have a .deb version to fix this issue. 
If one does issue the command:
sudo apt install chromium-browser, 
this command will instead instruct snap to install chromium.

Hope the Chromium developer community can fix this issue given it was
first reported in 2018-01-03. Chroumium adoption would be made easier
too. Thank you.

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions


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

[Desktop-packages] [Bug 1939228] [NEW] screen tearing and redraw in ubuntu 20.04 LTS

[Nishant Kumar Singh]

Public bug reported:

I have used ubuntu 21.04 before on this device and  reported a bug and
it is solved by making psr value to 0. but in ubuntu 20.04LTS is not
working.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-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..30.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:30: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.91.03  Fri Jul  2 06:04:10 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Aug  8 13:57:13 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
   Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
InstallationDate: Installed on 2021-08-08 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 82A1
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2021
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: DHCN32WW
dmi.board.asset.tag: ���
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55722 WIN
dmi.chassis.asset.tag: ���
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Slim 7 14IIL05
dmi.ec.firmware.release: 1.29
dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
dmi.product.family: Yoga Slim 7 14IIL05
dmi.product.name: 82A1
dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
dmi.product.version: Yoga Slim 7 14IIL05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "20210808_135627.jpg"
   
https://bugs.launchpad.net/bugs/1939228/+attachment/5516599/+files/20210808_135627.jpg

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

Title:
  screen tearing and redraw in ubuntu 20.04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I have used ubuntu 21.04 before on this device and  reported a bug and
  it is solved by making psr value to 0. but in ubuntu 20.04LTS is not
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-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..30.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:30: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.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: 

[Desktop-packages] [Bug 1939226] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Bruno Normand]

Public bug reported:

on ubuntu 20.04.2 TLS

during compilation of nvidia-340
in make file at line 11096
no file in asm/kmap_types.h because they are no directory asm

In file included from /var/lib/dkms/nvidia-340/340.108/build/nv-frontend.c:13:
/var/lib/dkms/nvidia-340/340.108/build/nv-linux.h: At top level:
/var/lib/dkms/nvidia-340/340.108/build/nv-linux.h:122:10: fatal error: 
asm/kmap_types.h: Aucun fichier ou dossier de ce type
  122 | #include  /* page table entry lookup  
*/
  |  ^~
compilation terminated.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-25-generic
Date: Sun Aug  8 09:12:09 2021
InstallationDate: Installed on 2021-01-15 (204 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageVersion: 340.108-0ubuntu5.20.04.2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  on ubuntu 20.04.2 TLS

  during compilation of nvidia-340
  in make file at line 11096
  no file in asm/kmap_types.h because they are no directory asm

  In file included from /var/lib/dkms/nvidia-340/340.108/build/nv-frontend.c:13:
  /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h: At top level:
  /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h:122:10: fatal error: 
asm/kmap_types.h: Aucun fichier ou dossier de ce type
122 | #include  /* page table entry lookup
  */
|  ^~
  compilation terminated.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-25-generic
  Date: Sun Aug  8 09:12:09 2021
  InstallationDate: Installed on 2021-01-15 (204 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1933088] Re: Does not work properly for videos with latest Chrome

[Sebastian Ramacher]

** Package changed: intel-media-driver-non-free (Ubuntu) => chromium-
browser (Ubuntu)

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

Title:
  Does not work properly for videos with latest Chrome

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chrome always gives software decoders for videos even though the same
  method works on Ubuntu 21.04 or Fedora 34 with Xorg. I can get
  VDAVideoDecoder with these new distros but not with Ubuntu 20.04 LTS
  and suspecting that package. I run Google Chrome (currently
  91.0.4472.114) with these flags:

  --use-gl=desktop --enable-features=VaapiVideoDecoder --force-dark-mode
  --flag-switches-begin --enable-gpu-rasterization --enable-zero-copy
  --ignore-gpu-blocklist --flag-switches-end --origin-trial-disabled-
  features=SecurePaymentConfirmation

  with intel-media-driver-non-free installed.

  vainfo:
  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_7
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.7 (libva 2.6.0)
  vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
  vainfo: Supported profile and entrypoints
VAProfileNone   :   VAEntrypointVideoProc
VAProfileNone   :   VAEntrypointStats
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointFEI
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointFEI
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointFEI
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileVP8Version0_3  :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointFEI
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice
VAProfileVP9Profile0:   VAEntrypointVLD
VAProfileVP9Profile2:   VAEntrypointVLD

  Tried with iHD and i965, nothing changed at all. Got VpxVideoDecoder
  instead of VDAVideoDecoder and my GPU has the capability of using
  VDAVideoDecoder, as it worked with Ubuntu 21.04 and Fedora 34.

  I have Intel UHD Graphics 620.

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  apt-cache policy intel-media-va-driver-non-free 
  intel-media-va-driver-non-free:
Installed: 20.1.1+ds1-1build1
Candidate: 20.1.1+ds1-1build1
Version table:
   *** 20.1.1+ds1-1build1 500
  500 http://tr.archive.ubuntu.com/ubuntu focal/multiverse amd64 
Packages
  100 /var/lib/dpkg/status

  What you expected to happen:
  Got VDAVideoDecoder when watching a video with Google Chrome.

  What happened instead:
  Got VpxVideoDecoder, which is a software decoder. Also, h264ify-variants did 
not work.

  
  Thanks in advance.

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


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

[Desktop-packages] [Bug 1933088] [NEW] Does not work properly for videos with latest Chrome

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Chrome always gives software decoders for videos even though the same
method works on Ubuntu 21.04 or Fedora 34 with Xorg. I can get
VDAVideoDecoder with these new distros but not with Ubuntu 20.04 LTS and
suspecting that package. I run Google Chrome (currently 91.0.4472.114)
with these flags:

--use-gl=desktop --enable-features=VaapiVideoDecoder --force-dark-mode
--flag-switches-begin --enable-gpu-rasterization --enable-zero-copy
--ignore-gpu-blocklist --flag-switches-end --origin-trial-disabled-
features=SecurePaymentConfirmation

with intel-media-driver-non-free installed.

vainfo:
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD

Tried with iHD and i965, nothing changed at all. Got VpxVideoDecoder
instead of VDAVideoDecoder and my GPU has the capability of using
VDAVideoDecoder, as it worked with Ubuntu 21.04 and Fedora 34.

I have Intel UHD Graphics 620.

lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

apt-cache policy intel-media-va-driver-non-free 
intel-media-va-driver-non-free:
  Installed: 20.1.1+ds1-1build1
  Candidate: 20.1.1+ds1-1build1
  Version table:
 *** 20.1.1+ds1-1build1 500
500 http://tr.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages
100 /var/lib/dpkg/status

What you expected to happen:
Got VDAVideoDecoder when watching a video with Google Chrome.

What happened instead:
Got VpxVideoDecoder, which is a software decoder. Also, h264ify-variants did 
not work.


Thanks in advance.

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

-- 
Does not work properly for videos with latest Chrome
https://bugs.launchpad.net/bugs/1933088
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to chromium-browser in Ubuntu.

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

[Desktop-packages] [Bug 1937343] Re: FireFox 90 unable to install unsigned webextensions

[Wang Ling]

Very much agree! 
For the very reason, I abandoned Firefox after 20 years of loyal support, and 
finally embrassed Chrome just this week. 
I do need my personal extensions. I do not want to submit my personal 
extensions for signature. I do not even need to pack them.
In chrome I can install unpacked extensions in develop mode and keep using them 
that way, while Firefox discards loaded unpacked extension after each session. 
I'm not sure if this feature will be changed in the future in chrome. So, the 
fact that I can not use my personal extension in FF is still kinda pain in my 
ass.
As long as there is a workaround, like patching omni.jar, this "stricter 
meassure" makes no difference from before, thus I would say "pointless".
Anyway, I'm starting to appreciate Mozilla turning me into a "majority" chrome 
user. Good luck to 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/1937343

Title:
  FireFox 90 unable to install unsigned webextensions

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04
  FireFox 90.0+build1-0ubuntu0.18.04.1

  Steps:

  - Set xpinstall.signatures.required to FALSE in about:config

  - Attempt to install UNSIGNED extension from file (Install Add-on
  From File...) in about:addons

  Expected:

  - FireFox warns about unverified add-on but ALLOWS installation.

  Actual result:

  - FireFox prevents the installation.


  Installing unsigned extensions used to work on all FireFox versions
  before 90.

  Related question https://answers.launchpad.net/ubuntu/+question/698053

  There appears to be at least one other affected person
  
https://old.reddit.com/r/firefox/comments/ootacl/unverified_addon_not_working_anymore_since/

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


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

[Desktop-packages] [Bug 1939221] [NEW] Screen Freeze then system without response

[petervec43]

Public bug reported:

It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking 
at first i watch video then put it on full screen (especially in browser 
chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" 
or try "Ctrl+alt+F2" to text mode.
then I search google and install amd's opencl driver to replace intel. but, it 
just better then previous.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.9-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 
5.4.41
Uname: Linux 5.4.0-7634-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  8 13:48:50 2021
InstallationDate: Installed on 2019-11-23 (623 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Screen Freeze then system without response

Status in mutter package in Ubuntu:
  New

Bug description:
  It seems that I install a new graphic cart AMD Radeon R7 240, it was blinking 
at first i watch video then put it on full screen (especially in browser 
chrome). it suddenly no response for any keys. even i press "Ctrl+alt+delete" 
or try "Ctrl+alt+F2" to text mode.
  then I search google and install amd's opencl driver to replace intel. but, 
it just better then previous.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.9-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-7634.38~1592497129~20.04~9a1ea2e-generic 
5.4.41
  Uname: Linux 5.4.0-7634-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 13:48:50 2021
  InstallationDate: Installed on 2019-11-23 (623 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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