[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode

[Bin Li]

And I made a patch for it.
https://github.com/tseliot/ubuntu-drivers-common/pull/53

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

Title:
  The NVIDIA X server Settings is blank when under Intel mode

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Summary]
  The VIIDA X server Settings does not show anything when the intel mode(Power 
Saving Mode) is working, so that it cannot switch back to Nvidia 
mode(Performance Mode) in the settings.

  [Steps to reproduce]
  1. Boot up the system and login.
  2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is 
working, switch it to intel display card and reboot.
  3. Open the NVIDIA X Server Settings again. It does not show anything, and 
just a blank dialog.
  mode
  [Expected result]
  The NVIDIA X Server Settings should show all configurations, and users can 
switch them in it.

  [Actual result]
  The dialog is blank.

  [Failure rate]
  100%

  [Additional information]
  ubuntu: 20.04.2
  kernel-version: 5.10.0-1029-oem

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

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

[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode

[Alex Tu]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  The NVIDIA X server Settings is blank when under Intel mode

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Summary]
  The VIIDA X server Settings does not show anything when the intel mode(Power 
Saving Mode) is working, so that it cannot switch back to Nvidia 
mode(Performance Mode) in the settings.

  [Steps to reproduce]
  1. Boot up the system and login.
  2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is 
working, switch it to intel display card and reboot.
  3. Open the NVIDIA X Server Settings again. It does not show anything, and 
just a blank dialog.
  mode
  [Expected result]
  The NVIDIA X Server Settings should show all configurations, and users can 
switch them in it.

  [Actual result]
  The dialog is blank.

  [Failure rate]
  100%

  [Additional information]
  ubuntu: 20.04.2
  kernel-version: 5.10.0-1029-oem

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

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

[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode

[Bin Li]

The root cause is that the nvidia_loaded is false cause in Power Saving Mode, 
and nvidia_kmod_available is also false cause couldn't find nvidia.ko 
correctly, so it wont' do set_offloading() which cause nvidia-settings is blank.
Now we used the linux-modules-nvidia-5.10.0-xxx-oem package to support secure 
boot, and it will install the nvidia.ko in 
/lib/modules/5.10.0-xxx-oem/kernel/nvidia-460/, so we need fix the source code 
to detect the nvidia modules correctly.

else if ((intel_loaded || amdgpu_loaded) && !nouveau_loaded &&
 (nvidia_loaded || nvidia_kmod_available)) {
fprintf(log_handle, "NVIDIA hybrid system\n");

/* Try to enable prime */
if (enable_prime(prime_settings,
 _device, current_devices, cards_n)) {

/* Write permanent settings about offloading */
set_offloading();
}


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

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

Title:
  The NVIDIA X server Settings is blank when under Intel mode

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Summary]
  The VIIDA X server Settings does not show anything when the intel mode(Power 
Saving Mode) is working, so that it cannot switch back to Nvidia 
mode(Performance Mode) in the settings.

  [Steps to reproduce]
  1. Boot up the system and login.
  2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is 
working, switch it to intel display card and reboot.
  3. Open the NVIDIA X Server Settings again. It does not show anything, and 
just a blank dialog.
  mode
  [Expected result]
  The NVIDIA X Server Settings should show all configurations, and users can 
switch them in it.

  [Actual result]
  The dialog is blank.

  [Failure rate]
  100%

  [Additional information]
  ubuntu: 20.04.2
  kernel-version: 5.10.0-1029-oem

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

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

[Desktop-packages] [Bug 1931514] [NEW] The NVIDIA X server Settings is blank when under Intel mode

[Bin Li]

Public bug reported:

[Summary]
The VIIDA X server Settings does not show anything when the intel mode(Power 
Saving Mode) is working, so that it cannot switch back to Nvidia 
mode(Performance Mode) in the settings.

[Steps to reproduce]
1. Boot up the system and login.
2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is 
working, switch it to intel display card and reboot.
3. Open the NVIDIA X Server Settings again. It does not show anything, and just 
a blank dialog.
mode
[Expected result]
The NVIDIA X Server Settings should show all configurations, and users can 
switch them in it.

[Actual result]
The dialog is blank.

[Failure rate]
100%

[Additional information]
ubuntu: 20.04.2
kernel-version: 5.10.0-1029-oem

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

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

Title:
  The NVIDIA X server Settings is blank when under Intel mode

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

Bug description:
  [Summary]
  The VIIDA X server Settings does not show anything when the intel mode(Power 
Saving Mode) is working, so that it cannot switch back to Nvidia 
mode(Performance Mode) in the settings.

  [Steps to reproduce]
  1. Boot up the system and login.
  2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is 
working, switch it to intel display card and reboot.
  3. Open the NVIDIA X Server Settings again. It does not show anything, and 
just a blank dialog.
  mode
  [Expected result]
  The NVIDIA X Server Settings should show all configurations, and users can 
switch them in it.

  [Actual result]
  The dialog is blank.

  [Failure rate]
  100%

  [Additional information]
  ubuntu: 20.04.2
  kernel-version: 5.10.0-1029-oem

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

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

[Desktop-packages] [Bug 1793124]

[Arjunsriva]

I'd really like this bug solved / feature added.

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

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

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

[Desktop-packages] [Bug 1793124]

[Ckattenberg]

Also recently ran into this problem. I have to copy out the contents of
the cell into a separate text editor to see everything. I hope this get
fixed some time ...

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

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

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

[Desktop-packages] [Bug 115153] Re: Counter intuitive ordering for threaded Email ordered by "order received'

[Bug Watch Updater]

** Changed in: thunderbird
   Importance: Wishlist => Medium

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 115153]

[Ray Satiro]

Created attachment 8811577
Date thread ordering.PNG

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 115153]

[Martin]

Within a thread, being able to use the received date order instead of
the default reply-to tree is indeed a major missing feature for my TB
usage.

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 115153]

[Mozillabugz]

Not sure if I'm seeing the same bug, or a different one, for me it has
started happening a month or two ago, affecting news but not mail.

I normally view sorted by order received, threaded, ascending
I quite frequently switch between all and unread messages

Using the menu/view/sort-by/order received, I see the "selected"
indicator dot against "order received" and I see the "^" sort indicator
in the order received column header of the message list pane.

If I then swap between unread and all messages using the dropdown in the
toolbar, I see the "^" indicator moves to the date column header, at
this point the menu/view/sort-by still shows the selected indicator dot
next to the order received entry

But if I then navigate to a different group, and then switch back to the
original group, there is no longer *any* indicator in the menu under
view/sort-by and the sorting is messed up.

I can always reselect order received and it will sort properly until I
alter the all/unread toggle and navigate between different groups, then
the sort is broken again.

Running 45.6.0 on Win10 64 bit

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 115153]

[Ray Satiro]

Created attachment 8811578
Order received thread ordering.PNG

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 115153]

[Ray Satiro]

I'm not sure if I have the same problem but I'll explain it. Messages I
received in Thunderbird did not actually have the right 'Received' date.
So I added mailnews.customDBHeaders = " Received" and now the received
column shows the date when my mail was actually received. But sorting by
'Received' is still no different from supporting by date. So I tried
'Order Received' and that seems to work except with threaded messages.
For example ascending threaded:

foo  100
bar  102
-re:bar  105
qux  103

So I would expect that the 'bar' thread would come after qux but it
doesn't. This is actually a big problem sometimes because I have a lot
of messages in my inbox and sometimes when they don't arrive for several
days they end up way back earlier in the list and I don't even notice
them. I will upload two screenshots.

In fairness that happens rarely but I'm surprised this bug has been open
for a decade. How do we get it handed off to someone?

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

Title:
  Counter intuitive ordering for threaded Email ordered by "order
  received'

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

Bug description:
  Binary package hint: mozilla-thunderbird

  -> Go to the inbox, set your view to threaded and your sorting to order 
received
  -> Receive an email to an older thread

  The thread will remain in the same spot in the list, even though of
  its children is my most current email and should be on top.

  The correct way to do this would be to have the entire thread move up
  to the top, based on the received status of the children in the thread
  view.

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 16 19:02:39 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 
2006 i686 GNU/Linux

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

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

[Desktop-packages] [Bug 1931485] Re: DaVinci Resolve is not identifying my integrated Intel Graphics card

[Daniel van Vugt]

Thanks for the bug report. The attached files seem to show that your
Intel graphics drivers are working properly for Ubuntu. Whatever the
problem is you see in DaVinci Resolve appears to be specific to that
application.


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

Title:
  DaVinci Resolve is not identifying my integrated Intel Graphics card

Status in Ubuntu:
  Invalid

Bug description:
  In Windows the GPU gets identified automatically but not in Ubuntu
  which is installed on the same system

  My Configuration:

  Laptop: DELL Inspiron 15 5580
  Processor: i5-8265U
  Integrated graphics: Intel UHD Graphics 620

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  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: Thu Jun 10 00:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
  InstallationDate: Installed on 2021-06-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Inspiron 5580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2020
  dmi.bios.release: 2.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 0J0XK8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5580
  dmi.product.sku: 089D
  dmi.sys.vendor: Dell Inc.
  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.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/+bug/1931485/+subscriptions

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

[Desktop-packages] [Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => plasma-workspace (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/1931488

Title:
  Kubuntu: No more file search results in Krunner or Kickoff after
  Hirsute Upgrade

Status in plasma-workspace package in Ubuntu:
  New

Bug description:
  I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get
  any file search results ("Desktop search") in Krunner or Kickoff
  ("Application Launcher"). For example type "testfile" in Krunner gives
  zero results although there this file in the home directory.

  However baloosearch in the terminal works fine. Desktop search / file
  search is also enabled in the settings for Krunner and in system
  settings.

  If I create a new user account the file search does work. I assume
  that some setting in the home directory must have been changed during
  the upgrade.

  Please let me know which logs or files I could upload that could be of
  use to debug this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jun  9 20:10:40 2021
  DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
   virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
   Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO Q556/2
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.26
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
  dmi.board.name: D3403-U1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3403-U1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO Q556/2
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  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/+source/plasma-workspace/+bug/1931488/+subscriptions

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

[Desktop-packages] [Bug 1931387] Re: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland

[Daniel van Vugt]

Thanks for the bug report. Please run this command to send us additional
system info:

  apport-collect 1931387

Please also 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: hirsute nouveau

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

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

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

Title:
  Ubuntu UI screen image freezes randomly during usage after fresh 21.04
  install, suspecting Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui-
  freezes-randomly-after-fresh-21-04-install-suspecting-wayland

  Let me know if there's any way to collect more useful information if
  there is ever a future crash, or a better place to report.

  I was running 20.10 previously with NVIDIA drivers,

  Then four days ago, I did a clean 21.04 install without installing the
  NVIDIA drivers, and since then the UI has frozen three times on my.

  I am unable to determine exactly what action triggered the freeze.

  The third time, I was just looking at a webpage, I wasn't even
  touching my mouse at that exact moment, and then it just froze.

  I am then unable to see anything move on the screen, including after
  Ctrl + Alt + Fn, the last image just stays fixed.

  The third time was also a bit different.

  A few seconds after freezing, it actually went down to a black
  terminal screen as during boot messages and then I was redirected to
  the login screen, as if I had been logged out.

  I was able to login, my programs were closed, so I was effectively
  logged out.

  Then two Apport windows showed up, and one of them contained several
  references to Xwayland. Under
  `/var/crash/_usr_bin_Xwayland.1000.crash` I see one of them:

  - `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth 
/run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 
-initfd 7
  - `StackTraceAddressSignature` contained mentions of Xwayland and 
nouveau_dri.so:

```
StacktraceAddressSignature: 
/usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01
```

  I also checked and I am using Wayland (the default since 21.04
  apparently): https://askubuntu.com/questions/904940/how-can-i-tell-
  if-i-am-running-wayland/1344287#1344287

  Hardware:

  - Lenovo ThinkPad P51
  - NVIDIA Quadro M1200 4GB GDDR5 GPU

  Just after the crash, dmesg contained the following possibly
  interesting lines:

  ```
  [ 9556.450894] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.450907] nouveau :01:00.0: gr: GPC0/TPC2/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG]
  [ 9556.454264] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.454283] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
  [ 9556.466339] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.466351] nouveau :01:00.0: gr: GPC0/TPC3/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
  [ 9698.230726] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
  [ 9713.230743] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
  [ 9713.231918] nouveau :01:00.0: fifo: fault 00 [READ] at 
00056000 engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on 
channel 5 [00ff0d9000 Xwayland[3831]]
  [ 9713.231930] nouveau :01:00.0: fifo: channel 5: killed
  [ 

[Desktop-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode

[Daniel van Vugt]

Thanks for the bug report. Please reproduce the bug (unwanted reboot)
again, then boot in safe mode and run:

 journalctl -b-1 > prevboot1.txt
 journalctl -b-2 > prevboot2.txt

and attach the resulting text files here.

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

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

Title:
  Ubuntu only stable in safe graphics mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
   Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 16.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B460-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  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/+source/linux/+bug/1931475/+subscriptions

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

[Desktop-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

[Daniel van Vugt]

When you run 'apport-cli' it should give you a link to click on. Did you
follow that?

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

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

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

[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Daniel van Vugt]

This is not hardware-specific.

** Summary changed:

- [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem 
[17aa:a814]: Can't turn bluetooth on again after turning it off
+ [hirsute/impish] Can't turn bluetooth on again after turning it off

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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

[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

[Daniel van Vugt]

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

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

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

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

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

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

[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off

[You-Sheng Yang]

** Summary changed:

- [hirsute/impish] Can't turn bluetooth on again after turning it off
+ [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem 
[17aa:a814]: Can't turn bluetooth on again after turning it off

** Description changed:

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn it
  on again. it neither turns on nor scans/connects to any device. This is
  happening since I updated my system to ubuntu 21.04 LTS
+ 
+   Bluetooth: hci0: HCI reset during shutdown failed
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
-   DOWN 
-   RX bytes:744804 acl:76 sco:0 events:105989 errors:0
-   TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
+   DOWN
+   RX bytes:744804 acl:76 sco:0 events:105989 errors:0
+   TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

Title:
  [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem
  [17aa:a814]: Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  

[Desktop-packages] [Bug 1922186] Re: ibus very difficult to restart

[Gunnar Hjalmarsson]

Hey, how about getting a more constructive hobby than killing various
important processes on your system? ;)

More seriously: I'm not sure that "ibus restart" is intended to handle
such situations. But please feel free to comment on the issue I
submitted — the upstream maintainer hasn't attended to it yet. Or,
probably better, submit an own upstream issue since they are separate
things.

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

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1922186] Re: ibus very difficult to restart

[DarkTrick]

+ Added the PPA and installed, now ibus stays "on" after openning the dialog. 
️ 
- `ibus restart` still doesnt work: "Can't connect to IBus"

Would be nice to also have a cmd-line option working for this case.


FYI:
Btw: here's another reason for quitting/restarting ibus: if I call `killall 
python3` on my machine, ibus/anthy (?) seems to get into an inconsistent state, 
which prevents input on certain apps. I guess the reason for this is somehow 
connected to what I've described earlier.

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

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Kubuntu: No more file search results in Krunner or Kickoff after
  Hirsute Upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get
  any file search results ("Desktop search") in Krunner or Kickoff
  ("Application Launcher"). For example type "testfile" in Krunner gives
  zero results although there this file in the home directory.

  However baloosearch in the terminal works fine. Desktop search / file
  search is also enabled in the settings for Krunner and in system
  settings.

  If I create a new user account the file search does work. I assume
  that some setting in the home directory must have been changed during
  the upgrade.

  Please let me know which logs or files I could upload that could be of
  use to debug this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jun  9 20:10:40 2021
  DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
   virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
   Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO Q556/2
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.26
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
  dmi.board.name: D3403-U1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3403-U1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO Q556/2
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  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/+source/xorg/+bug/1931488/+subscriptions

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

[Desktop-packages] [Bug 1931488] [NEW] Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get any
file search results ("Desktop search") in Krunner or Kickoff
("Application Launcher"). For example type "testfile" in Krunner gives
zero results although there this file in the home directory.

However baloosearch in the terminal works fine. Desktop search / file
search is also enabled in the settings for Krunner and in system
settings.

If I create a new user account the file search does work. I assume that
some setting in the home directory must have been changed during the
upgrade.

Please let me know which logs or files I could upload that could be of
use to debug this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Jun  9 20:10:40 2021
DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
 virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
 Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU ESPRIMO Q556/2
ProcEnviron:
 LANGUAGE=de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
dmi.bios.date: 02/12/2020
dmi.bios.release: 1.26
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
dmi.board.name: D3403-U1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3403-U1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
dmi.product.family: ESPRIMO-FTS
dmi.product.name: ESPRIMO Q556/2
dmi.sys.vendor: FUJITSU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
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

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


** Tags: amd64 apport-bug hirsute kubuntu third-party-packages ubuntu
-- 
Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade
https://bugs.launchpad.net/bugs/1931488
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1931494] [NEW] Wrong scaling

[Davide]

Public bug reported:

Ubuntu 20.04
Evince 3.36.10

If I set the scale to 100% the document on display is twice the real size.
To see the document at the correct size I have to set the scale to 50%.
Evince 3.36.7 does not have this bug.

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

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

Title:
  Wrong scaling

Status in evince package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  Evince 3.36.10

  If I set the scale to 100% the document on display is twice the real size.
  To see the document at the correct size I have to set the scale to 50%.
  Evince 3.36.7 does not have this bug.

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

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

[Desktop-packages] [Bug 1875796] Re: HP Envy 5530 printer/scanner does not work

[Andrew]

I have one printer.  It is a HP Envy 5530.  I'm experiencing multiple issues.  
Sometimes CUPS finds printers, sometimes it doesn't.  It auto-adds printers 
randomly.  It auto-deletes printers randomly.  One day the printer works, the 
next it does not.

Also seeing these errors in syslog:
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=1, index=3
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
7/1/4: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=3, altset=0, index=9
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=3 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/4/1: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=0, index=11
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/cc/0: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: prnt/backend/hp.c 825: INFO: open device 
failed stat=21: hp:/usb/ENVY_5530_series?serial=CN57A5636Z05XT; will retry in 
30 seconds...


** Attachment added: "Screenshot of duplicate printers in CUPS Find New 
Printers."
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+attachment/5503675/+files/screenshot-127.0.0.1_631-2021.06.09-12_38_33%281%29.png

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

Title:
  HP Envy 5530 printer/scanner does not work

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.04 LTS
  see troubleshoot.txt please

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 08:15:00 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat:
   device for ENVY_5530_series_CN4A5310HJ067B_: 
implicitclass://ENVY_5530_series_CN4A5310HJ067B_/
   device for HP-ENVY-5530-series: 
hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
   Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-5530-series.ppd', 
'/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied
   grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[Amr Ibrahim]

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

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

Title:
  Scrolling on label doesn't work

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

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

  [ Test case ]

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

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

  [ Regression potential ]

  Scroll events on icon doesn't work anymore

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

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

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

[Amr Ibrahim]

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

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

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

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

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

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

  So we should emit the service name by default when known

  [ Test case ]

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

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

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

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

  [ Regression potential ]

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

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

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

[Desktop-packages] [Bug 1931485] [NEW] DaVinci Resolve is not identifying my integrated Intel Graphics card

[joydipto-nag]

Public bug reported:

In Windows the GPU gets identified automatically but not in Ubuntu which
is installed on the same system

My Configuration:

Laptop: DELL Inspiron 15 5580
Processor: i5-8265U
Integrated graphics: Intel UHD Graphics 620

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
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: Thu Jun 10 00:23:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
InstallationDate: Installed on 2021-06-06 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. Inspiron 5580
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2020
dmi.bios.release: 2.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.0
dmi.board.name: 0J0XK8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5580
dmi.product.sku: 089D
dmi.sys.vendor: Dell Inc.
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.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

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  DaVinci Resolve is not identifying my integrated Intel Graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  In Windows the GPU gets identified automatically but not in Ubuntu
  which is installed on the same system

  My Configuration:

  Laptop: DELL Inspiron 15 5580
  Processor: i5-8265U
  Integrated graphics: Intel UHD Graphics 620

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  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: Thu Jun 10 00:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
  InstallationDate: Installed on 2021-06-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Inspiron 5580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2020
  dmi.bios.release: 2.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 0J0XK8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5580
  dmi.product.sku: 089D
  dmi.sys.vendor: Dell Inc.
  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.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
  

[Desktop-packages] [Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver and VAAPI enabled

[Massimo Bacilieri]

The solution at #9 solved the same issue in "Parole" (the eq. of Totem in 
Xfce4)!!!
Thankyou!!!

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

Title:
  Fatal IO error 11 on totem startup when using the Nvidia binary driver
  and VAAPI enabled

Status in totem package in Ubuntu:
  Triaged

Bug description:
  Whenever I try to launch totem, I get the following error:
  Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1.

  Then, it just crashes.

  This bug only occurs when using the Nvidia binary driver. However,
  even using the Nvidia binary driver, it doesn't occur on VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul  6 20:52:08 2018
  InstallationDate: Installed on 2018-05-14 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1931475] [NEW] Ubuntu only stable in safe graphics mode

[welefort]

Public bug reported:

Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

Machine will only stay running in safe graphics mode.  When booting
normal, GUI loads for about 5 seconds then reboots.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  9 14:04:22 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2021-06-09 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: ASUS System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2021
dmi.bios.release: 16.5
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B460-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
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

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


** Tags: amd64 apport-bug hirsute ubuntu

** Attachment added: "Kern.log"
   https://bugs.launchpad.net/bugs/1931475/+attachment/5503616/+files/kern.log

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

Title:
  Ubuntu only stable in safe graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ago)
  

[Desktop-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode

[welefort]

** Attachment added: "Hardware Info"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931475/+attachment/5503634/+files/hardinfo_report.html

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

Title:
  Ubuntu only stable in safe graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
   Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 16.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B460-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  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/+source/xorg/+bug/1931475/+subscriptions

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

[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

[Jani Uusitalo]

There's no gnome-shell-extension-dashtodock package for focal [1], but I
did try with Dash to Dock from extensions.gnome.org, and could not
reproduce the issue with it. I tried with the default settings, as well
as after recreating the look & feel of Ubuntu Dock as much as possible.

Dash to Dock has customizable action for the scroll (to either switch
workspaces or windows, or to do nothing), and all of those also worked
just as expected.

I also noticed that using the two finger scroll function of the touchpad
on my laptop does *not* trigger this (whereas using the mouse on it
does).


* [1] 
https://packages.ubuntu.com/search?keywords=gnome-shell-extension-dashtodock

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

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

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

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

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

[Desktop-packages] [Bug 1931272] Re: [SRU] libreoffice 7.1.4 for hirsute

[Rico Tzschichholz]

** Description changed:

  [Impact]
  
-  * LibreOffice 7.1.4 is in its forth bugfix release of the 7.1 line:
-  https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.4_release
+  * LibreOffice 7.1.4 is in its forth bugfix release of the 7.1 line:
+  https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.4_release
  
-  * Version 7.1.3 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.3 see the list of bugs fixed in the release candidates of 7.1.4 
(that's a total of 79 bugs):
-  https://wiki.documentfoundation.org/Releases/7.1.4/RC1#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/7.1.4/RC2#List_of_fixed_bugs
+  * Version 7.1.3 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.3 see the list of bugs fixed in the release candidates of 7.1.4 
(that's a total of 79 bugs):
+  https://wiki.documentfoundation.org/Releases/7.1.4/RC1#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/7.1.4/RC2#List_of_fixed_bugs
  
-  * Given the nature of the project, the complexity of the codebase and
+  * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
  [Testing]
  
-  * Upstream testing. Bugs fixed upstream typically include
+  * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
-   * A recent set of upstream's automated jenkins testing can be found here:
- https://ci.libreoffice.org/job/gerrit_71/1220/
+   * A recent set of upstream's automated jenkins testing can be found here:
+ https://ci.libreoffice.org/job/gerrit_71/1220/
  
-   * More information about the upstream QA testing can be found here:
- * Automated tests
-   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
- * Automated UI tests
-   https://wiki.documentfoundation.org/Development/UITests
- * Regression tests
-   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
- * Feature tests
-   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
+   * More information about the upstream QA testing can be found here:
+ * Automated tests
+   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
+ * Automated UI tests
+   https://wiki.documentfoundation.org/Development/UITests
+ * Regression tests
+   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
+ * Feature tests
+   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
-  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
- * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210607_174726_685e9@/log.gz
- * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210608_013339_0abc1@/log.gz
- * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210607_175937_445f4@/log.gz
- * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210607_221555_8f69a@/log.gz
- * [s390x] ...
+  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210607_174726_685e9@/log.gz
+ * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210608_013339_0abc1@/log.gz
+ * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210607_175937_445f4@/log.gz
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210607_221555_8f69a@/log.gz
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210609_131734_bd6bf@/log.gz
  
-  * General smoke testing of all the applications in the office suite
+  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented by:
  https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
-  * A minor release with a total of 79 bug fixes always carries the
+  * A minor release with a total of 79 bug fixes always carries the
  

[Desktop-packages] [Bug 1925837]

[Catalin-sasca-z]

I was able to reproduce the window issue on Firefox 87.0b5 wayland
session under Ubuntu 20.04 by following the info provided in Comment 0.

The issue is fixed and the indicator appeared on the left side of the
screen on Firefox 90.0b5 on the same system.

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

Title:
  [Wayland] Sharing indicator window is not frameless

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I'm running updated hirsute with the firefox 87.0+build3-0ubuntu4 deb,
  just as it comes. This system was a fresh install of 20.10 that was
  then upgraded to 21.04.

  When I have a tab that will start using my webcam/mic, there is a new
  ff window that is created with these icons. The window is (more or
  less) minimized to fit the size of the icons (see screenshot). I can
  close the window by clicking the normal x, and closing this window
  does not interrupt my webcam/mic usage.

  What I normally expect is that when my webcam/mic is being used by some ff 
tab, the ff/webcam/mic icons are displayed constantly in the top middle of my 
display.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BuildID: 20210318103112
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 21.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-01-04 (108 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.6 metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Package: firefox 87.0+build3-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112 (In use)
  RunningIncompatibleAddons: False
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1931388] Re: Firefox disaplayerror after Update on last version 89

[Norbert]

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

** Tags added: groovy

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

Title:
  Firefox disaplayerror after Update on last version 89

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  After the last Update from Firefox Browser to Version 89 Firefox is unsuable. 
The Program starts but the window is somehow transparent and white. I removed 
and reinstalled Firefox but the problem is the same. My computer is an Amd 
Mashine running Ubuntu Mate 20.10 Mate 1.24.1
  I took a Screenshot.

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

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

[Desktop-packages] [Bug 1929304] Re: file-roller / gnome archive manager fails to extract

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-autoar - 0.3.3-1

---
gnome-autoar (0.3.3-1) experimental; urgency=medium

  * New upstream release
- Fix extraction of one file archives (lp: #1929304)

 -- Sebastien Bacher   Fri, 04 Jun 2021 10:58:31
+0200

** Changed in: gnome-autoar (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  file-roller / gnome archive manager fails to extract

Status in gnome-autoar package in Ubuntu:
  Fix Released
Status in gnome-autoar source package in Bionic:
  Fix Released
Status in gnome-autoar source package in Focal:
  Fix Released
Status in gnome-autoar source package in Groovy:
  Fix Released
Status in gnome-autoar source package in Hirsute:
  Fix Released
Status in gnome-autoar source package in Impish:
  Fix Released

Bug description:
  problem occurs with :

  a) ubuntu 20.04.2 | gnome version 3.36.8 | X11

  b) fedora 34 | gnome 40.0.1 | wayland

  the latest version of gnome archive manager which is 3.36.3 fails to
  extract a .gz file which it used to do earlier.

  here are 2 links to 2 separate versions of hard disk sentinel linux
  version :

  1. https://www.hdsentinel.com/hdslin/hdsentinel-018c.gz

  2. https://www.hdsentinel.com/hdslin/hdsentinel-019c-x64.gz

  when i try to extract both the above mentioned files by right clicking
  & then extract here all i get is an empty folder with nothing
  extracted in it.

  if i open the gnome archive manager 3.36.3 from the applications menu
  & then try to extract the 1st file hard disk sentinel version 018c the
  extraction is successful.

  but if i open the gnome archive manager 3.36.3 from the applications
  menu & then try to extract the 2nd file hard disk sentinel version
  019c it only makes a copy of the .gz file.

  the earlier version of gnome archive manager which is default / built-in the 
ubuntu 20.04.2 iso
  did not have this problem it is only after the update that the gnome archive 
manager fails to perform.

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

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

[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

[Alexey Kulik]

I can also confirm that update with hirsute-proposed enabled solves the problem 
for me.
Before this, the problem used to be readily reproduced by the procedure 
described in comment #51.

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

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

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

[Desktop-packages] [Bug 1931387] [NEW] Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland

[Ciro Santilli 六四事件 法轮功]

Public bug reported:

Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui-
freezes-randomly-after-fresh-21-04-install-suspecting-wayland

Let me know if there's any way to collect more useful information if
there is ever a future crash, or a better place to report.

I was running 20.10 previously with NVIDIA drivers,

Then four days ago, I did a clean 21.04 install without installing the
NVIDIA drivers, and since then the UI has frozen three times on my.

I am unable to determine exactly what action triggered the freeze.

The third time, I was just looking at a webpage, I wasn't even touching
my mouse at that exact moment, and then it just froze.

I am then unable to see anything move on the screen, including after
Ctrl + Alt + Fn, the last image just stays fixed.

The third time was also a bit different.

A few seconds after freezing, it actually went down to a black terminal
screen as during boot messages and then I was redirected to the login
screen, as if I had been logged out.

I was able to login, my programs were closed, so I was effectively
logged out.

Then two Apport windows showed up, and one of them contained several
references to Xwayland. Under `/var/crash/_usr_bin_Xwayland.1000.crash`
I see one of them:

- `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth 
/run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 
-initfd 7
- `StackTraceAddressSignature` contained mentions of Xwayland and 
nouveau_dri.so:

  ```
  StacktraceAddressSignature: 
/usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01
  ```

I also checked and I am using Wayland (the default since 21.04
apparently): https://askubuntu.com/questions/904940/how-can-i-tell-if-i
-am-running-wayland/1344287#1344287

Hardware:

- Lenovo ThinkPad P51
- NVIDIA Quadro M1200 4GB GDDR5 GPU

Just after the crash, dmesg contained the following possibly interesting
lines:

```
[ 9556.450894] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.450907] nouveau :01:00.0: gr: GPC0/TPC2/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG]
[ 9556.454264] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.454283] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9556.466339] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.466351] nouveau :01:00.0: gr: GPC0/TPC3/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9698.230726] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
[ 9713.230743] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
[ 9713.231918] nouveau :01:00.0: fifo: fault 00 [READ] at 00056000 
engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on channel 5 [00ff0d9000 
Xwayland[3831]]
[ 9713.231930] nouveau :01:00.0: fifo: channel 5: killed
[ 9713.231932] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[ 9713.231939] nouveau :01:00.0: fifo: engine 5: scheduled for recovery
[ 9713.231943] nouveau :01:00.0: Xwayland[3831]: channel 5 killed!
[ 9717.642691] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[ 9717.642702] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[ 9717.642709] nouveau :01:00.0: fifo: channel 3: killed
[ 9717.642714] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[ 9717.643113] nouveau :01:00.0: Xwayland[3831]: channel 3 killed!
[ 9719.351714] apport-gtk[119654]: segfault at 18 ip 7f337637d194 sp 
7ffd95094dc0 error 4 in libgtk-3.so.0.2404.21[7f3376274000+385000]
[ 9719.351721] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b 
e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 0c 36 17 00 <48> 8b 40 
18 48 8b 78 10 e8 ef 03 09 00 48 83 c4 08 48 89 c7 e9 a3
[ 9744.187533] rfkill: input handler enabled
[ 9745.940823] rfkill: input handler disabled
[ 9775.737572] rfkill: input handler enabled
[ 9777.953055] rfkill: input handler disabled
```

Related:

- https://askubuntu.com/questions/1334177/ubuntu-21-04-wayland-gimp-
black-window GIMP works fine

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

-- 
You received this bug notification because you are a member of 

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

[Denis Oleksiuk]

This bug still in ubuntu 20.04 :

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Desktop-packages] [Bug 1931383] Re: ipp-usb ftbfs with lto

[Matthias Klose]

https://go-review.googlesource.com/c/go/+/322614/


** Also affects: golang
   Importance: Undecided
   Status: New

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

Title:
  ipp-usb ftbfs with lto

Status in Go:
  New
Status in golang-1.16 package in Ubuntu:
  New
Status in ipp-usb package in Ubuntu:
  New

Bug description:
  ipp-usb ftbfs with lto, apparently not seen on Fedora builds.

  github.com/OpenPrinting/ipp-usb
  # github.com/OpenPrinting/ipp-usb
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:1:13: error: 
function ‘avahiClientCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:24:6: note: previously 
declared here
 24 | void avahiClientCallback(AvahiClient* client, AvahiClientState state, 
void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:4:13: error: 
function ‘avahiEntryGroupCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:46:6: note: previously 
declared here
 46 | void avahiEntryGroupCallback(AvahiEntryGroup* egroup, 
AvahiEntryGroupState state, void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:7:13: error: 
function ‘libusbHotplugCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:68:5: note: previously 
declared here
 68 | int libusbHotplugCallback(libusb_context* ctx, libusb_device* dev, 
libusb_hotplug_event event, void* p)
| ^
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:21:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiClientCallback’ redeclared as function
 21 | extern void _cgoexp_73d50ba221cf_avahiClientCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:10:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:43:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiEntryGroupCallback’ redeclared as function
 43 | extern void _cgoexp_73d50ba221cf_avahiEntryGroupCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:11:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:65:13: error: variable 
‘_cgoexp_73d50ba221cf_libusbHotplugCallback’ redeclared as function
 65 | extern void _cgoexp_73d50ba221cf_libusbHotplugCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:12:5: note: 
previously declared here
  lto1: fatal error: errors during merging of translation units
  compilation terminated.
  lto-wrapper: fatal error: /usr/bin/gcc returned 1 exit status
  compilation terminated.
  /usr/bin/ld: error: lto-wrapper failed
  collect2: error: ld returned 1 exit status

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

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

[Desktop-packages] [Bug 1931383] Re: ipp-usb ftbfs with lto

[Matthias Klose]

** Also affects: golang-1.16 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ipp-usb ftbfs with lto

Status in Go:
  New
Status in golang-1.16 package in Ubuntu:
  New
Status in ipp-usb package in Ubuntu:
  New

Bug description:
  ipp-usb ftbfs with lto, apparently not seen on Fedora builds.

  github.com/OpenPrinting/ipp-usb
  # github.com/OpenPrinting/ipp-usb
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:1:13: error: 
function ‘avahiClientCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:24:6: note: previously 
declared here
 24 | void avahiClientCallback(AvahiClient* client, AvahiClientState state, 
void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:4:13: error: 
function ‘avahiEntryGroupCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:46:6: note: previously 
declared here
 46 | void avahiEntryGroupCallback(AvahiEntryGroup* egroup, 
AvahiEntryGroupState state, void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:7:13: error: 
function ‘libusbHotplugCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:68:5: note: previously 
declared here
 68 | int libusbHotplugCallback(libusb_context* ctx, libusb_device* dev, 
libusb_hotplug_event event, void* p)
| ^
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:21:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiClientCallback’ redeclared as function
 21 | extern void _cgoexp_73d50ba221cf_avahiClientCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:10:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:43:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiEntryGroupCallback’ redeclared as function
 43 | extern void _cgoexp_73d50ba221cf_avahiEntryGroupCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:11:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:65:13: error: variable 
‘_cgoexp_73d50ba221cf_libusbHotplugCallback’ redeclared as function
 65 | extern void _cgoexp_73d50ba221cf_libusbHotplugCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:12:5: note: 
previously declared here
  lto1: fatal error: errors during merging of translation units
  compilation terminated.
  lto-wrapper: fatal error: /usr/bin/gcc returned 1 exit status
  compilation terminated.
  /usr/bin/ld: error: lto-wrapper failed
  collect2: error: ld returned 1 exit status

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

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

[Desktop-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

[rud]

Thanks, i tried that, still nothing happens and nothing new appears in 
https://errors.ubuntu.com/user/ID 
But going through the info shown when I use ubuntu-bug, I can confirm this 
crash on 2 different systems and it is about: "xorg crashed with sigabrt in 
osabort()" 
- The mentioned Intel C246 chipset with Core i3-9100, no dedicated GPU.
- Lenovo S540 AMD Ryzen 4800U laptop (no dedicated GPU).

I don't notice the crash during or after install btw. I only see the popup 
after a reboot.
In both cases it only happens once after clean install, if I remove the crash 
file, no new crash file is created after reboots.

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

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

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

[Desktop-packages] [Bug 1931383] [NEW] ipp-usb ftbfs with lto

[Matthias Klose]

Public bug reported:

ipp-usb ftbfs with lto, apparently not seen on Fedora builds.

github.com/OpenPrinting/ipp-usb
# github.com/OpenPrinting/ipp-usb
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:1:13: error: 
function ‘avahiClientCallback’ redeclared as variable
../../../../tmp/go-build3834344537/b001/_cgo_export.c:24:6: note: previously 
declared here
   24 | void avahiClientCallback(AvahiClient* client, AvahiClientState state, 
void* _)
  |  ^
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:4:13: error: 
function ‘avahiEntryGroupCallback’ redeclared as variable
../../../../tmp/go-build3834344537/b001/_cgo_export.c:46:6: note: previously 
declared here
   46 | void avahiEntryGroupCallback(AvahiEntryGroup* egroup, 
AvahiEntryGroupState state, void* _)
  |  ^
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:7:13: error: 
function ‘libusbHotplugCallback’ redeclared as variable
../../../../tmp/go-build3834344537/b001/_cgo_export.c:68:5: note: previously 
declared here
   68 | int libusbHotplugCallback(libusb_context* ctx, libusb_device* dev, 
libusb_hotplug_event event, void* p)
  | ^
../../../../tmp/go-build3834344537/b001/_cgo_export.c:21:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiClientCallback’ redeclared as function
   21 | extern void _cgoexp_73d50ba221cf_avahiClientCallback(void *);
  | ^
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:10:5: note: 
previously declared here
../../../../tmp/go-build3834344537/b001/_cgo_export.c:43:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiEntryGroupCallback’ redeclared as function
   43 | extern void _cgoexp_73d50ba221cf_avahiEntryGroupCallback(void *);
  | ^
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:11:5: note: 
previously declared here
../../../../tmp/go-build3834344537/b001/_cgo_export.c:65:13: error: variable 
‘_cgoexp_73d50ba221cf_libusbHotplugCallback’ redeclared as function
   65 | extern void _cgoexp_73d50ba221cf_libusbHotplugCallback(void *);
  | ^
../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:12:5: note: 
previously declared here
lto1: fatal error: errors during merging of translation units
compilation terminated.
lto-wrapper: fatal error: /usr/bin/gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

** Affects: ipp-usb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lto

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

Title:
  ipp-usb ftbfs with lto

Status in ipp-usb package in Ubuntu:
  New

Bug description:
  ipp-usb ftbfs with lto, apparently not seen on Fedora builds.

  github.com/OpenPrinting/ipp-usb
  # github.com/OpenPrinting/ipp-usb
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:1:13: error: 
function ‘avahiClientCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:24:6: note: previously 
declared here
 24 | void avahiClientCallback(AvahiClient* client, AvahiClientState state, 
void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:4:13: error: 
function ‘avahiEntryGroupCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:46:6: note: previously 
declared here
 46 | void avahiEntryGroupCallback(AvahiEntryGroup* egroup, 
AvahiEntryGroupState state, void* _)
|  ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:7:13: error: 
function ‘libusbHotplugCallback’ redeclared as variable
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:68:5: note: previously 
declared here
 68 | int libusbHotplugCallback(libusb_context* ctx, libusb_device* dev, 
libusb_hotplug_event event, void* p)
| ^
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:21:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiClientCallback’ redeclared as function
 21 | extern void _cgoexp_73d50ba221cf_avahiClientCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:10:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:43:13: error: variable 
‘_cgoexp_73d50ba221cf_avahiEntryGroupCallback’ redeclared as function
 43 | extern void _cgoexp_73d50ba221cf_avahiEntryGroupCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:11:5: note: 
previously declared here
  ../../../../tmp/go-build3834344537/b001/_cgo_export.c:65:13: error: variable 
‘_cgoexp_73d50ba221cf_libusbHotplugCallback’ redeclared as function
 65 | extern void _cgoexp_73d50ba221cf_libusbHotplugCallback(void *);
| ^
  ../../../../tmp/go-build3834344537/b001/cgo-generated-wrappers:12:5: 

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

Ok, let's keep this bug report about the udev rule. We will need to make
sure 470 works properly with prime, I'll follow up with that separately.

So would you be able to prepare a merge proposal please? 

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

Title:
  [nvidia-prime] switches between xorg and wayland session

Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Impish:
  New

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too.

  Performance mode is selected in nvidia-settings, which is supposed to
  mean nvidia & therefore xorg but it's not working. Selecting it
  explicitly doesn't help either.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1929304] Re: file-roller / gnome archive manager fails to extract

[ipv]

did a fresh install of focal > did an update > did the extraction & it
was successful.

problem solved for focal.

huge thanks to marc, paul & sebastien.

god bless canonical.

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

Title:
  file-roller / gnome archive manager fails to extract

Status in gnome-autoar package in Ubuntu:
  Fix Committed
Status in gnome-autoar source package in Bionic:
  Fix Released
Status in gnome-autoar source package in Focal:
  Fix Released
Status in gnome-autoar source package in Groovy:
  Fix Released
Status in gnome-autoar source package in Hirsute:
  Fix Released
Status in gnome-autoar source package in Impish:
  Fix Committed

Bug description:
  problem occurs with :

  a) ubuntu 20.04.2 | gnome version 3.36.8 | X11

  b) fedora 34 | gnome 40.0.1 | wayland

  the latest version of gnome archive manager which is 3.36.3 fails to
  extract a .gz file which it used to do earlier.

  here are 2 links to 2 separate versions of hard disk sentinel linux
  version :

  1. https://www.hdsentinel.com/hdslin/hdsentinel-018c.gz

  2. https://www.hdsentinel.com/hdslin/hdsentinel-019c-x64.gz

  when i try to extract both the above mentioned files by right clicking
  & then extract here all i get is an empty folder with nothing
  extracted in it.

  if i open the gnome archive manager 3.36.3 from the applications menu
  & then try to extract the 1st file hard disk sentinel version 018c the
  extraction is successful.

  but if i open the gnome archive manager 3.36.3 from the applications
  menu & then try to extract the 2nd file hard disk sentinel version
  019c it only makes a copy of the .gz file.

  the earlier version of gnome archive manager which is default / built-in the 
ubuntu 20.04.2 iso
  did not have this problem it is only after the update that the gnome archive 
manager fails to perform.

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

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

[Desktop-packages] [Bug 1931324] Re: [HP ENVY Laptop 15-ep0xxx] Mute-microphone key doesn't work

[Fikrul Arif]

** Summary changed:

- Mic mute key doesn't work on HP Envy 15
+ [HP ENVY Laptop 15-ep0xxx] Mute-microphone key doesn't work

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

Title:
  [HP ENVY Laptop 15-ep0xxx] Mute-microphone key doesn't work

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

Bug description:
  Pressing mic mute on the keyboard doesn't mute/unmute the microphone,
  and the light indicator on the key is not changed. `xev` gives this
  when the key is pressed:

  MappingNotify event, serial 37, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  KeyPress event, serial 37, synthetic NO, window 0x221,
  root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x221,
  root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  However, trying to record/add the keyboard shortcut in Settings >
  Keyboard is not successful. When the key is pressed it seems it
  doesn't detect the key pressed event.

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

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

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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Timo Aaltonen]

21.04 comes with Mesa 21.0.1 which does not seem to have 820dec3f7c7

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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

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

[Desktop-packages] [Bug 1931324] Re: Mic mute key doesn't work on HP Envy 15

[Fikrul Arif]

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

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

Title:
  Mic mute key doesn't work on HP Envy 15

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

Bug description:
  Pressing mic mute on the keyboard doesn't mute/unmute the microphone,
  and the light indicator on the key is not changed. `xev` gives this
  when the key is pressed:

  MappingNotify event, serial 37, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  KeyPress event, serial 37, synthetic NO, window 0x221,
  root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x221,
  root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  However, trying to record/add the keyboard shortcut in Settings >
  Keyboard is not successful. When the key is pressed it seems it
  doesn't detect the key pressed event.

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

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

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

[Desktop-packages] [Bug 1818593] Re: PS data generated on Ubuntu 16.04 is larger than on Ubuntu 14.04

[Sebastien Bacher]

Thanks for the comment Alex, closing the report

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

** Changed in: ghostscript (Ubuntu)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

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

Title:
  PS data generated on Ubuntu 16.04 is larger than on Ubuntu 14.04

Status in ghostscript package in Ubuntu:
  Invalid

Bug description:
  OS: Ubuntu 16.04LTS
  Ghostscript Version: 9.18
  Generated file size: 1280KB

  OS: Ubuntu 14.04LTS
  Ghostscript Version: 9.10
  Generated file size: 556KB

  We found a problem about Ghostscript:
  When converting from PDF file to PS data using the Ghostscript command, the 
PS data generated by Ghostscript 9.18 on Ubuntu 16.04LTS is twice as large as 
the PS data generated by Ghostscript 9.10 on Ubuntu 14.04LTS. Due to the 
increase in size, the printing speed of PCL6 driver will be severe slow down on 
Ubuntu 16.04LTS.

  The following is the Ghostscript command which we use for converting from PDF 
file to PS data:
  gs -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=ps2write 
-sOUTPUTFILE={out_ps_file_path} -dLanguageLevel=3 -r600 -dCompressFonts=false 
-dNoT3CCITT -dNOINTERPOLATE -f sample.pdf

  We'd like you to answer the following questions.

  1. Is it Ghostscript's specification or bug?
  2. If it is a bug, do you have any plan to fix it?
  3. Is there any workaround?

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

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

[Desktop-packages] [Bug 1931324] [NEW] Mic mute key doesn't work on HP Envy 15

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Pressing mic mute on the keyboard doesn't mute/unmute the microphone,
and the light indicator on the key is not changed. `xev` gives this when
the key is pressed:

MappingNotify event, serial 37, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248

KeyPress event, serial 37, synthetic NO, window 0x221,
root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x221,
root 0x93b, subw 0x0, time 1133652, (210,515), root:(2914,643),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

However, trying to record/add the keyboard shortcut in Settings >
Keyboard is not successful. When the key is pressed it seems it doesn't
detect the key pressed event.

Description:Ubuntu 20.04.2 LTS
Release:20.04

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


** Tags: bot-comment
-- 
Mic mute key doesn't work on HP Envy 15
https://bugs.launchpad.net/bugs/1931324
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1928458] Re: inconsistent and unneeded password prompts

[Sebastien Bacher]

sorry but it's a bit unclear from the description what the issue is, it
just sounds like those softwares do try to read the keyring for whatever
reason, could be to check if there is a stored credential and to do that
they need to unlock the keyring, it doesn't sound a bug

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

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 1925795] Re: SRU the current 0.20.4 stable update

[Chris Halse Rogers]

Hey Seb! This is a candidate for release into -updates, but I don't
think we can do that while it supersedes any package in Groovy.

I understand that the Desktop team has constrained resources. The SRU
team intends to propose a policy change to help, but for now could you
please do a Groovy upload too?

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

Title:
  SRU the current 0.20.4 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes and 
translation updates
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

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

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