date:20220222

I think you mean the new libx11 is useful in solving other bugs. This
bug should be about the log messages only, so it's low importance.
Although it's prevalent enough that people who read logs all day (me)
will really appreciate the fix.

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xlibs:
  Unknown
Status in libx11 package in Ubuntu:
  Fix Committed
Status in x11-xkb-utils package in Ubuntu:
  Confirmed

Bug description:
  Get lot of such warnings into Jammy logged;
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and

[Desktop-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....

2022-02-22 Thread madigal

Also brings a huge help to firefox freezing/crashing:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/153

** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #153
   https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/153

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xlibs:
  Unknown
Status in libx11 package in Ubuntu:
  Fix Committed
Status in x11-xkb-utils package in Ubuntu:
  Confirmed

Bug description:
  Get lot of such warnings into Jammy logged;
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built

[Desktop-packages] [Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess

2022-02-22 Thread Chris Guiver

On rebooting into my installed system on same box
- dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)

AND using 'Ubuntu on Xorg' (sorry i forget exact wording) on Ubuntu
jammy.

- I am NOT getting any video glitches using the GNOME desktop; if I had
I would have noticed before now

HOWEVER

- SCREENshots are showing issues to the left & right of what my scree
showed just as LIVE image showed, these are only visible using
PRINTSCREEN, and AFTER screen-position-change (even if change is very
slight)

What I see varies on each SCREENSHOT but on the attached picture I see
bits of the terminal window mostly; parts of my `gpicview` display of
first picture (will talk about this shortly!) .. & other windows.

PLEASE NOTE the image shown in the `gpicview` window; nothing glitchy
shows on that picture!! which was directly after login before I adjusted
screens; the issues appear to be after moving alignment of screen
on four subsequent PRINTSCREEN presses after slight changes of
screen.alignment GLITCHES were evident a per top-left & bottom-right of
the image itself.

I see nothing wrong on my displays, I'm talking about PRINTSCREEN images
saved to disk that are later viewed in my old gpicview.

Note: this installed system was installed in the artful cycle; is
release-upgraded every 6 months (though wasn't on artful long at all) so
is heavily modified.

This is my observation of this session only; I'd want to confirm what I
wrote here on subsequent logouts/logins before I relied on it.. (QA-
test installs & other stuff going on at same time currently)

** Attachment added: "Screenshot from 2022-02-23 15-21-58.png"

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1953507/+attachment/5562868/+files/Screenshot%20from%202022-02-23%2015-21-58.png

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

Title:
[radeon] jammy live - on adjusting display config; one display is
unsuable blocky-mess

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

Bug description:
ubuntu jammy daily (canary build) live test on
- dell optiplex 960

(this is my primary machine; so is normally used for entry of data &
not doing the QA-testing).

on adjusting the displays to match my setup (six displays; two high &
three across; this box uses two in the middle with middle on top row &
middle on bottom row).. the top display is still useable, but the
bottom is not. This boxes are not perfectly aligned as not all my
displays are the exact same size; so top display is slightly to right
of bottom display

the bottom resembles a digital TV with bad signal, mostly blocky &
parts of it flashing (very quickly). it doesn't match the attached
picture (as viewable on this box anyway.. my top display; which was
LEFT prior to alignment is perfectly readable).

** actual

my top display is usable, bottom is not (blocky warped picture)

** expected

on adjust displays to match my config; both displays remain usable &
readable.

** notes

likely related to graphics card & not GNOME. If I recall correctly;
this box has an older video card used as it had 2x DVI connections my
screens use.

My usual install on this box is jammy; but I usually use LXQt/Lubuntu
and I don't experience issues.. I also have installed Xubuntu/Xfce &
Ubuntu/GNOME so can test the installed OS (where I don't believe I
have issue), but my install is somewhat old (artful install upgraded
every six months ~30-36 hours after each release) thus is likely
heavily modified.

** Picture comments

My top display is ~perfect (vertical white bar to left of ubuntu-dock-
items I'd not expect, but the color-blocks to the left of the
'install/firefox/thunderbird/files` is NOT visible; only a vertical
WHITE bar a few pixels wide to left of the dock appears' rest of top
display is perfect.

My bottom display is nothing like picture; it's unusable. A mixture
of black/white boxes with red/purple bits which would be the picture
warped into blocky-components. When I type, I get reactions on this
display with the picture changing (mostly the black & white portions
which flash, the red/purple bits which are warped indri picture appear
to remain static).

My phone/camera isn't working, but I've taken a photograph. I didn't
anticipate issues in this QA-test (it's past 1AM now) otherwise I'd
not have run this QA-test now.

** further comments

this is likely a duplicate... I experience this type of reaction on
other boxes; likely radeon related but I've yet to look & can't even
remember which video card exists in this box (I don't experience
issues with the display configuration of the box with identical card
to this, but it relates to display setup/config... my other box with
this card is

[Desktop-packages] [Bug 1961558] Re: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish

2022-02-22 Thread Launchpad Bug Tracker

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  802.1x connection Handshake failure ssl3 error in Jammy Jellyfish

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I had install Jammy (beta) release to test it. I have my network with
  Radius authentication configured, so we have made a Network Profile
  enabling 802.1x authentication in Ubuntu. When I tried to connecting
  to the network it doesn't worked. I saw the logs (see picture) and it
  says that it was a handshake failure in the connection because there
  is a SSL3 error.

  I read that probably it can be a problem with the  legacy
  renegotiation in the handshake, but I'm not sure why happens that and
  what can I do to fix this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558/+subscriptions


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

[Desktop-packages] [Bug 1961867] [NEW] Sync gjs 1.71.1-1 (main) from Debian experimental (main)

Public bug reported:

Please sync gjs 1.71.1-1 (main) from Debian experimental (main)

Changelog entries since current jammy version 1.70.1-1:

gjs (1.71.1-1) experimental; urgency=medium

  * New upstream release:
- New JavaScript features! This version of GJS is based on SpiderMonkey 91
  For more information, look them up on MDN or devdocs.io
- It's now possible to pass BigInt values to GObject-introspected functions
  with 64-bit parameters
  * debian/patches: Cherry-pick upstream test fixes
  * debian/patches: Do not crash on instanceof checks on interfaces
(LP: #1960898)
  * debian/patches: Correctly handle later handled promises rejections
  * debian/control: Bump dependency on mozjs-91
  * debian/libgjs0g.symbols: Include new symbols

 -- Marco Trevisan (Treviño)   Tue, 22 Feb 2022
12:26:43 +0100

** Affects: gjs (Ubuntu)
 Importance: Wishlist
 Status: Fix Released

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

** Changed in: gjs (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync gjs 1.71.1-1 (main) from Debian experimental (main)

Status in gjs package in Ubuntu:
  Fix Released

Bug description:
  Please sync gjs 1.71.1-1 (main) from Debian experimental (main)

  Changelog entries since current jammy version 1.70.1-1:

  gjs (1.71.1-1) experimental; urgency=medium

* New upstream release:
  - New JavaScript features! This version of GJS is based on SpiderMonkey 91
For more information, look them up on MDN or devdocs.io
  - It's now possible to pass BigInt values to GObject-introspected 
functions
with 64-bit parameters
* debian/patches: Cherry-pick upstream test fixes
* debian/patches: Do not crash on instanceof checks on interfaces
  (LP: #1960898)
* debian/patches: Correctly handle later handled promises rejections
* debian/control: Bump dependency on mozjs-91
* debian/libgjs0g.symbols: Include new symbols

   -- Marco Trevisan (Treviño)   Tue, 22 Feb 2022
  12:26:43 +0100

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


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

[Desktop-packages] [Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess

2022-02-22 Thread Chris Guiver

I've booted today's daily (jammy canary ISO - ISO date 20220222) on my
- dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

On FIRST adjustment of displays (one [directly] above the other) no
visual issues were observed.

On SECOND adjustment of displays (top display slightly to the right of
the below display; this is how my displays actually are as not all
displays are identical size), visual glitches did occur - however they
don't match the description of my original post.

My bottom display today is PERFECT, the glitches appeared top display
along the left edge only.. but they've since returned to normal
(glitches stopped flashing after I took screenshot)

See screenshot - it'll explain how I've aligned displays PLUS shows
~blocky-mess where screens do not show  (left of my-top display & right
of my-bottom display..  this POSSIBLY is what I was seeing on original
post EXCEPT it was showing on screen but isn't today at least not now
(but was left edge of my upper screen at beginning of session after
second adjustment of display settings until I hit printscreen).

GNOME Settings About - tells me X11 is the "Windowing System" used in
this default run.

Either way; nothing would stop me from using this box today...   (I may
[if i remember] when I reboot into my normal jammy] use GNOME & have a
look at how it is there

I did NOT find a way at gdm3 to login using WAYLAND instead of default
X11/Xorg in the live session.

(I'm not going to report this bug on QA-test; it's not bad enough as
only an extremely mild version of what this report was like; my QA-
comments can be found at
http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244757/testcases/1743/results)

** Attachment added: "Screenshot from 2022-02-23 03-26-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1953507/+attachment/5562862/+files/Screenshot%20from%202022-02-23%2003-26-05.png

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

Title:
  [radeon] jammy live - on adjusting display config; one display is
  unsuable blocky-mess

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

Bug description:
  ubuntu jammy daily (canary build) live test on 
  - dell optiplex 960

  (this is my primary machine; so is normally used for entry of data &
  not doing the QA-testing).

  on adjusting the displays to match my setup (six displays; two high &
  three across; this box uses two in the middle with middle on top row &
  middle on bottom row)..  the top display is still useable, but the
  bottom is not.  This boxes are not perfectly aligned as not all my
  displays are the exact same size; so top display is slightly to right
  of bottom display

  the bottom resembles a digital TV with bad signal, mostly blocky &
  parts of it flashing (very quickly).  it doesn't match the attached
  picture (as viewable on this box anyway.. my top display; which was
  LEFT prior to alignment is perfectly readable).

  ** actual

  my top display is usable, bottom is not (blocky warped picture)

  ** expected

  on adjust displays to match my config; both displays remain usable &
  readable.

  ** notes

  likely related to graphics card & not GNOME.   If I recall correctly;
  this box has an older video card used as it had 2x DVI connections my
  screens use.

  My usual install on this box is jammy; but I usually use LXQt/Lubuntu
  and I don't experience issues.. I also have installed Xubuntu/Xfce &
  Ubuntu/GNOME so can test the installed OS (where I don't believe I
  have issue), but my install is somewhat old (artful install upgraded
  every six months ~30-36 hours after each release) thus is likely
  heavily modified.

  ** Picture comments

  My top display is ~perfect (vertical white bar to left of ubuntu-dock-
  items I'd not expect, but the color-blocks to the left of the
  'install/firefox/thunderbird/files` is NOT visible; only a vertical
  WHITE bar a few pixels wide to left of the dock appears' rest of top
  display is perfect.

  My bottom display is nothing like picture; it's unusable.  A mixture
  of black/white boxes with red/purple bits which would be the picture
  warped into blocky-components.  When I type, I get reactions on this
  display with the picture changing (mostly the black & white portions
  which flash, the red/purple bits which are warped indri picture appear
  to remain static).

  My phone/camera isn't working, but I've taken a photograph. I didn't
  anticipate issues in this QA-test (it's past 1AM now) otherwise I'd
  not have run this QA-test now.

  ** further comments

  this is likely a duplicate... I experience this type of reaction on
  other boxes; likely radeon related but I've yet to look & can't even
  remember which video card exists in this box (I don

[Desktop-packages] [Bug 1961618] Re: Pi server image no longer connects to eth0 after upgrade to jammy

2022-02-22 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-settings - 22.04.2

---
ubuntu-settings (22.04.2) jammy; urgency=medium

  * d/ubuntu-raspi-settings.maintscript: Remove the pre-jammy netplan eth0
rules; the newer netplan chokes on the space-separated driver filter
(LP: #1961618)
  * meson.build: Remove incorrect positional param

 -- Dave Jones   Mon, 21 Feb 2022 17:28:05
+

** Changed in: ubuntu-settings (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Pi server image no longer connects to eth0 after upgrade to jammy

Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
  unfortunately causes problems on upgrade from impish to jammy as the
  file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
  and the new netplan version on jammy chokes on the space-separated
  driver filter.

  This results in the entire netplan configuration failing to apply,
  with the result that the network doesn't come up.

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


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

[Desktop-packages] [Bug 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects

Thanks for the bug report.

bluez has not changed at all since 2022-01-13 so the problem isn't going
to be that. Next I would usually blame the kernel but that hasn't
changed since 2022-01-27.

I don't see anything in comment #2 related to Bluetooth either (maybe
pipewire?). Can you provide more of the log?


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

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

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

Title:
  bluetooth connects with headset, deconects, connects, deconnects

Status in Ubuntu:
  Incomplete

Bug description:
  bluetooth connects with headset, then times out, deconnects.
  Forcing it to connect again it does, then times out and deconnects again.

  Seen this with:
  - Cyber jack
  - Phonak Hearing Aids
  - Sennheiser Headset

  Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00.
  And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00.
  One of the packages updated produced the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.63-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Feb 22 23:18:09 2022
  InstallationDate: Installed on 2021-12-11 (73 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FAS16K00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET84W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS16K00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS16K00
  dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 34:F3:9A:EE:2A:4A  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:18813 acl:14 sco:0 events:2736 errors:0
TX bytes:606658 acl:14 sco:0 commands:2675 errors:0

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


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

[Desktop-packages] [Bug 1961459] Re: adsys pam issues

2022-02-22 Thread Seth Arnold

Heh, so Dmitry might actually remove the other 'free' calls in the error
paths :) -- and he spotted that the strdup() calls are unchecked:

https://github.com/linux-pam/linux-pam/issues/444

It might be worth mirroring whatever he decides to do.

Thanks

** Bug watch added: github.com/linux-pam/linux-pam/issues #444
   https://github.com/linux-pam/linux-pam/issues/444

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

Title:
  adsys pam issues

Status in adsys package in Ubuntu:
  New

Bug description:
  These may not be security issues but it's possible I overlooked
  something; since they live in a security boundary I thought it worth
  reporting with a bit of hassle. If you'd rather work on this in the
  open, feel free to open this.

  pam_adsys.c update_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to
  work but I don't think that's how that API is supposed to be used
  pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny

  Thanks

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


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

[Desktop-packages] [Bug 1961823] Re: [RTL8822BE] Bluetooth adapter not found

** Summary changed:

- Bluetooth button off and doesn't work 
+ [RTL8822BE] Bluetooth adapter not found

** Package changed: bluez (Ubuntu) => linux-hwe-5.13 (Ubuntu)

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

Title:
  [RTL8822BE] Bluetooth adapter not found

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

Bug description:
  Bluetooth button off and doesn't work  the massage that show me when i
  open the setting " No Bluetooth Found plug in a dongle to use
  Bluetooth "

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth 5.53-0ubuntu3.5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 22 21:08:36 2022
  InstallationDate: Installed on 2022-02-17 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  InterestingModules: bnep bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   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/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 15-da1xxx
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2021
  dmi.bios.release: 15.38
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8533
  dmi.board.vendor: HP
  dmi.board.version: 70.38
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 70.38
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da1xxx
  dmi.product.sku: 6EX79EA#A2N
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


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

[Desktop-packages] [Bug 1961857] Re: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r30

See also bug 1961858.

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

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

** Tags added: radeon

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

Title:
  compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from
  draw_create_vs_llvm() from draw_create_vertex_shader() from
  r300_draw_init_vertex_shader() from r300_create_vs_state()

Status in compiz package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
compiz.  This problem was most recently seen with package version 
1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/253612f74aa79d2e52b8f27505f04cb72de285c1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1961561] Re: [radeon] Blinking screen

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

Thanks. The only crash report from your machine that looks like this bug
is now in bug 1961857. But that is so rare it's only ever been reported
twice.

Most likely it will be resolved (or already has been) in a newer version
of Mesa.

** This bug has been marked a duplicate of bug 1961857
   compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from 
draw_create_vs_llvm() from draw_create_vertex_shader() from 
r300_draw_init_vertex_shader() from r300_create_vs_state()

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

Title:
  [radeon] Blinking screen

Status in compiz package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb 21 10:13:34 2022
  DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' 
produces an unwanted removal 'gnome-software-plugin-snap', skipping
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
     Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  InstallationDate: Installed on 2015-11-26 (2278 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.release: 2.10
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8061JND
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.product.sku: EW318AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Feb 21 10:00:44 2022
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.13-1ubuntu1~20.04.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1961858] Re: compiz crashed with SIGSEGV in ntt_no_indirects_mask() from nir_to_tgsi() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_

See also bug 1961857.

** Summary changed:

- 
/usr/bin/compiz:11:ntt_no_indirects_mask:nir_to_tgsi:draw_create_vertex_shader:r300_draw_init_vertex_shader:r300_create_vs_state
+ compiz crashed with SIGSEGV in ntt_no_indirects_mask() from nir_to_tgsi() 
from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from 
r300_create_vs_state()

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

** Tags added: radeon

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

Title:
  compiz crashed with SIGSEGV in ntt_no_indirects_mask() from
  nir_to_tgsi() from draw_create_vertex_shader() from
  r300_draw_init_vertex_shader() from r300_create_vs_state()

Status in compiz package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
compiz.  This problem was most recently seen with package version 
1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e715e808830237b34f47eaf08647380de1916892 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1961459] Re: adsys pam issues

2022-02-22 Thread Seth Arnold

Oh yes, the waitpid() stuff.. if it works in testing, leaving it alone
is probably fine then. Thanks.

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

Title:
  adsys pam issues

Status in adsys package in Ubuntu:
  New

Bug description:
  These may not be security issues but it's possible I overlooked
  something; since they live in a security boundary I thought it worth
  reporting with a bit of hassle. If you'd rather work on this in the
  open, feel free to open this.

  pam_adsys.c update_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to
  work but I don't think that's how that API is supposed to be used
  pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny

  Thanks

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


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

[Desktop-packages] [Bug 1961459] Re: adsys pam issues

2022-02-22 Thread Seth Arnold

Hah so I've got another bug to report then? :) Thanks!

** Information type changed from Private Security to Public

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

Title:
  adsys pam issues

Status in adsys package in Ubuntu:
  New

Bug description:
  These may not be security issues but it's possible I overlooked
  something; since they live in a security boundary I thought it worth
  reporting with a bit of hassle. If you'd rather work on this in the
  open, feel free to open this.

  pam_adsys.c update_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() arggv leak in fork() failure
  pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to
  work but I don't think that's how that API is supposed to be used
  pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny

  Thanks

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


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

[Desktop-packages] [Bug 1961852] [NEW] PRIME profiles is missing in nvidia-settings

2022-02-22 Thread Thomas

Public bug reported:

Usually I used the on-demand profile. Somehow this is gone in latest 510
version. I also tried 460 but no success. I only can switch between
internal graphics and nvidia. (Power Saving and Performance).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-prime 0.8.16~0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18
Uname: Linux 5.8.0-55-lowlatency x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Feb 23 00:56:00 2022
Dependencies:
 
InstallationDate: Installed on 2019-12-19 (796 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot_2022-02-23_01-00-47.png"
   
https://bugs.launchpad.net/bugs/1961852/+attachment/5562852/+files/Screenshot_2022-02-23_01-00-47.png

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

Title:
  PRIME profiles is missing in nvidia-settings

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Usually I used the on-demand profile. Somehow this is gone in latest
  510 version. I also tried 460 but no success. I only can switch
  between internal graphics and nvidia. (Power Saving and Performance).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-prime 0.8.16~0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18
  Uname: Linux 5.8.0-55-lowlatency x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 23 00:56:00 2022
  Dependencies:
   
  InstallationDate: Installed on 2019-12-19 (796 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+subscriptions


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

[Desktop-packages] [Bug 1961852] Re: PRIME profiles is missing in nvidia-settings

2022-02-22 Thread Thomas

** Attachment added: "Screenshot_2022-02-23_01-00-47.png"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+attachment/5562855/+files/Screenshot_2022-02-23_01-00-47.png

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

Title:
  PRIME profiles is missing in nvidia-settings

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Usually I used the on-demand profile. Somehow this is gone in latest
  510 version. I also tried 460 but no success. I only can switch
  between internal graphics and nvidia. (Power Saving and Performance).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-prime 0.8.16~0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18
  Uname: Linux 5.8.0-55-lowlatency x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 23 00:56:00 2022
  Dependencies:
   
  InstallationDate: Installed on 2019-12-19 (796 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+subscriptions


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

[Desktop-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects

2022-02-22 Thread Thomas Schweikle

Public bug reported:

bluetooth connects with headset, then times out, deconnects.
Forcing it to connect again it does, then times out and deconnects again.

Seen this with:
- Cyber jack
- Phonak Hearing Aids
- Sennheiser Headset

Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00.
And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00.
One of the packages updated produced the problem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.63-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Feb 22 23:18:09 2022
InstallationDate: Installed on 2021-12-11 (73 days ago)
InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FAS16K00
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 1.52
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET84W (1.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS16K00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS16K00
dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 34:F3:9A:EE:2A:4A  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:18813 acl:14 sco:0 events:2736 errors:0
TX bytes:606658 acl:14 sco:0 commands:2675 errors:0

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


** Tags: amd64 apport-bug jammy

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

Title:
  bluetooth connects with headset, deconects, connects, deconnects

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth connects with headset, then times out, deconnects.
  Forcing it to connect again it does, then times out and deconnects again.

  Seen this with:
  - Cyber jack
  - Phonak Hearing Aids
  - Sennheiser Headset

  Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00.
  And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00.
  One of the packages updated produced the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.63-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Feb 22 23:18:09 2022
  InstallationDate: Installed on 2021-12-11 (73 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FAS16K00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET84W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS16K00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS16K00
  dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 34:F3:9A:EE:2A:4A  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:18813 acl:14 sco:0 events:2736 errors:0
TX bytes:606658 acl:14 sco:0 commands:2675 errors:0

To manage notifications about

[Desktop-packages] [Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Won't Fix => In Progress

** Changed in: gjs (Ubuntu)
   Importance: Medium => High

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: High => Low

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

Title:
  Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool
  InterfacePrototype::has_instance_impl(JSContext*, const
  JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu-
  d...@ubuntu.com/locations.js:1108

Status in gjs package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Hardware: https://linux-hardware.org/?probe=1055dc7082

  Worked without Problem in 21.04
  Had some flicker and problem with the left dock in 21.10
  not working since updating to 22.04

  now I'm running xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 15 08:07:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-15 (183 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1961848] [NEW] gst-play-1.0 crashes when attempting to play a mp4 file

2022-02-22 Thread Breton M. Saunders

Public bug reported:

I am attempting to play a mp4 file using gstreamer's gst-play-1.0.  What
I see is that a window is opened and a segmentation fault is reported
(window closes).

I am running Jammy:

Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

On an Intel Coffelake core-i7 / integrated (Gen 9) graphics.

The machine is updated as of Feb 22, 2022.  Package version is:

$ apt-cache policy gstreamer1.0-plugins-base-apps
gstreamer1.0-plugins-base-apps:
  Installed: 1.20.0-2
  Candidate: 1.20.0-2
  Version table:
 *** 1.20.0-2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
bms20@lichking:/tmp$ 


Crash log attached.

Any advice on how to fix welcome!

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "_usr_bin_gst-play-1.0.1000.crash.gz"
   
https://bugs.launchpad.net/bugs/1961848/+attachment/5562828/+files/_usr_bin_gst-play-1.0.1000.crash.gz

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

Title:
  gst-play-1.0 crashes when attempting to play a mp4 file

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  I am attempting to play a mp4 file using gstreamer's gst-play-1.0.
  What I see is that a window is opened and a segmentation fault is
  reported (window closes).

  I am running Jammy:

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  On an Intel Coffelake core-i7 / integrated (Gen 9) graphics.

  The machine is updated as of Feb 22, 2022.  Package version is:

  $ apt-cache policy gstreamer1.0-plugins-base-apps
  gstreamer1.0-plugins-base-apps:
Installed: 1.20.0-2
Candidate: 1.20.0-2
Version table:
   *** 1.20.0-2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  bms20@lichking:/tmp$ 

  
  Crash log attached.

  Any advice on how to fix welcome!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1961848/+subscriptions


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

[Desktop-packages] [Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus

2022-02-22 Thread Francis Chin

There is one important step for reproducing this bug, not only in 
gnome-terminal, but also in nautilus and gedit:
* open multiple tabs

* !!! reorder one of the tabs !!!

* leave pointer hovering over one of the tabs
* observe tooltip appearing, and cursor changing to reflect loss of focus in 
the tab window
* observe the next keypress not going to the tab window, but seemingly either 
the tooltip or the tab widget (not sure which); after this, focus returns to 
the tab window for subsequent input.

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

Title:
  Gnome-terminal tab bar steals keyboard focus

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure when it started, but using the version of Gnome-Terminal
  in latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing
  keyboard focus.

  This is dangerous.

  The problem is usually that I click on a tab, leave the mouse there,
  and start typing. The tab bar then steals the first character typed.
  Sometimes I click in the terminal window, and then move the mouse out
  of the way (to the tab bar). Sometimes it happens later, when the
  mouse drifts onto a tab (maybe I knock it slightly while typing).

  There are many cases in which the unexpected loss of a character typed
  could lead to significant damage. For example,

  rm *~

  losing the tilde. Or

  sudo rm -rf /mnt/1/*

  losing the 1.

  I have preferred click to focus (as opposed to focus-follows-mouse) in
  X for nearly 30 years. Gnome-Terminal should not pervert this
  preference.

  Reported upstream - https://gitlab.gnome.org/GNOME/gnome-
  terminal/-/issues/245

  Not clear that this is 100% a bug with gnome-terminal, or whether it
  is an interaction between it and another part of the
  XWayland/gnome/gnome-shell setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 16 10:16:15 2020
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1961835] [NEW] Attempting to remove iw results in attempted removal of the kernel.

2022-02-22 Thread Philip Llewelyn Davies

Public bug reported:

root@eleanor:~/work# apt purge iw
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  intel-microcode iucode-tool libnl-genl-3-200 wireless-regdb
Use 'apt autoremove' to remove them.
The following packages will be REMOVED
  crda* iw* linux-generic-hwe-20.04* linux-image-generic-hwe-20.04* 
linux-modules-extra-5.11.0-27-generic* linux-modules-extra-5.13.0-28-generic*
0 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
After this operation, 516 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

root@eleanor:~/work# apt-mark manual linux-image-generic-hwe-20.04
linux-image-generic-hwe-20.04 set to manually installed.

root@eleanor:~/work# apt-mark manual linux-modules-extra-5.11.0-27-generic 
linux-modules-extra-5.13.0-28-generic
linux-modules-extra-5.11.0-27-generic set to manually installed.
linux-modules-extra-5.13.0-28-generic set to manually installed.

root@eleanor:~/work# apt purge iw
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  intel-microcode iucode-tool libnl-genl-3-200 wireless-regdb
Use 'apt autoremove' to remove them.
The following packages will be REMOVED
  crda* iw* linux-generic-hwe-20.04* linux-image-generic-hwe-20.04* 
linux-modules-extra-5.11.0-27-generic* linux-modules-extra-5.13.0-28-generic*
0 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
After this operation, 516 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iw 5.4-1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Feb 22 19:34:53 2022
InstallationDate: Installed on 2022-02-16 (6 days ago)
InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
SourcePackage: iw
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Attempting to remove iw results in attempted removal of the kernel.

Status in iw package in Ubuntu:
  New

Bug description:
  root@eleanor:~/work# apt purge iw
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
intel-microcode iucode-tool libnl-genl-3-200 wireless-regdb
  Use 'apt autoremove' to remove them.
  The following packages will be REMOVED
crda* iw* linux-generic-hwe-20.04* linux-image-generic-hwe-20.04* 
linux-modules-extra-5.11.0-27-generic* linux-modules-extra-5.13.0-28-generic*
  0 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
  After this operation, 516 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  root@eleanor:~/work# apt-mark manual linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04 set to manually installed.

  root@eleanor:~/work# apt-mark manual linux-modules-extra-5.11.0-27-generic 
linux-modules-extra-5.13.0-28-generic
  linux-modules-extra-5.11.0-27-generic set to manually installed.
  linux-modules-extra-5.13.0-28-generic set to manually installed.

  root@eleanor:~/work# apt purge iw
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
intel-microcode iucode-tool libnl-genl-3-200 wireless-regdb
  Use 'apt autoremove' to remove them.
  The following packages will be REMOVED
crda* iw* linux-generic-hwe-20.04* linux-image-generic-hwe-20.04* 
linux-modules-extra-5.11.0-27-generic* linux-modules-extra-5.13.0-28-generic*
  0 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
  After this operation, 516 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: iw 5.4-1
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Feb 22 19:34:53 2022
  InstallationDate: Installed on 2022-02-16 (6 days ago)
  InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  SourcePackage: iw
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 320057] Re: Thunderbird hangs for 10secs when auto-completing address

** Changed in: thunderbird
   Status: Confirmed => Won't Fix

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

Title:
  Thunderbird hangs for 10secs when auto-completing address

Status in Mozilla Thunderbird:
  Won't Fix
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  This bug seems to be very old, but somehow I didn't find it in
  Launchpad - forgive me if  it's a dupe.

  When composing a new mail, I start typing a few letters into the address bar 
of the Thunderbird composer windows, and TB tries to autocomplete it from the 
address book.
  The drop-down menu appears, giving me the possibilities that start with the 
letters I typed, BUT - Thunderbird hangs (compiz darkens the window) for 
approx. 10 seconds - then it gets itself up again and processes complete 
normally, no errors, no wrong behaviour - and the address book searches are 
correct.

  First I thought it was the prefs.js, see
  http://kb.mozillazine.org/Long_time_to_open_address_book

  Funny thing is, that I NEVER had used Thunderbird 1.5 before - but I had 
about 50 lines with that "nonascii" in it.
  I deleted them, and gone was the problem, for a few days.
  TB worked normally.

  Then the problem reoccurred.
  Now my prefs.js is clean, and it still has the problem.
  It might have something to do with LDAP search as well - I first thought it 
has to do with that: I have a LDAP server on a openVPN network which is not 
always connected - and I thought the delay was a network timeout when TB 
searches for the LDAP and doesn't find it.
  But I now disabled the LDAP address search in Thunderbird, and the problem 
remains.

  Also see here:
  http://forums.mozillazine.org/viewtopic.php?f=39=499016=2648760

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


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

[Desktop-packages] [Bug 320057]

2022-02-22 Thread rns

LDAP c-sdk has been removed in bug 1729862. Please file new bug if this
is still a problem.

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

Title:
  Thunderbird hangs for 10secs when auto-completing address

Status in Mozilla Thunderbird:
  Won't Fix
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  This bug seems to be very old, but somehow I didn't find it in
  Launchpad - forgive me if  it's a dupe.

  When composing a new mail, I start typing a few letters into the address bar 
of the Thunderbird composer windows, and TB tries to autocomplete it from the 
address book.
  The drop-down menu appears, giving me the possibilities that start with the 
letters I typed, BUT - Thunderbird hangs (compiz darkens the window) for 
approx. 10 seconds - then it gets itself up again and processes complete 
normally, no errors, no wrong behaviour - and the address book searches are 
correct.

  First I thought it was the prefs.js, see
  http://kb.mozillazine.org/Long_time_to_open_address_book

  Funny thing is, that I NEVER had used Thunderbird 1.5 before - but I had 
about 50 lines with that "nonascii" in it.
  I deleted them, and gone was the problem, for a few days.
  TB worked normally.

  Then the problem reoccurred.
  Now my prefs.js is clean, and it still has the problem.
  It might have something to do with LDAP search as well - I first thought it 
has to do with that: I have a LDAP server on a openVPN network which is not 
always connected - and I thought the delay was a network timeout when TB 
searches for the LDAP and doesn't find it.
  But I now disabled the LDAP address search in Thunderbird, and the problem 
remains.

  Also see here:
  http://forums.mozillazine.org/viewtopic.php?f=39=499016=2648760

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


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

[Desktop-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

** Changed in: pulseaudio
   Status: Unknown => Fix Committed

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Fix Committed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

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


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

[Desktop-packages] [Bug 1961823] [NEW] Bluetooth button off and doesn't work

2022-02-22 Thread mohamm

Public bug reported:

Bluetooth button off and doesn't work  the massage that show me when i
open the setting " No Bluetooth Found plug in a dongle to use Bluetooth
"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth 5.53-0ubuntu3.5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 22 21:08:36 2022
InstallationDate: Installed on 2022-02-17 (4 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
InterestingModules: bnep bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
 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/6p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
 |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
MachineType: HP HP Laptop 15-da1xxx
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2021
dmi.bios.release: 15.38
dmi.bios.vendor: Insyde
dmi.bios.version: F.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8533
dmi.board.vendor: HP
dmi.board.version: 70.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 70.38
dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-da1xxx
dmi.product.sku: 6EX79EA#A2N
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
hciconfig:
 
rfkill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth button off and doesn't work

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth button off and doesn't work  the massage that show me when i
  open the setting " No Bluetooth Found plug in a dongle to use
  Bluetooth "

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth 5.53-0ubuntu3.5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 22 21:08:36 2022
  InstallationDate: Installed on 2022-02-17 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  InterestingModules: bnep bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   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/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 15-da1xxx
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=616f1e34-70a5-4b45-82ae-a86b7f795ab2 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2021
  dmi.bios.release: 15.38
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8533
  dmi.board.vendor: HP
  dmi.board.version: 70.38
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 70.38
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHPLaptop15-da1xxx:pvrType1ProductConfigId:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:sku6EX79EA#A2N:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da1xxx
  dmi.product.sku: 6EX79EA#A2N
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft

[Desktop-packages] [Bug 1915744] Re: System settings power saving section has misleading wording

2022-02-22 Thread Launchpad Bug Tracker

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

** Changed in: nautilus-share (Ubuntu)
   Status: New => Confirmed

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

Title:
  System settings power saving section has misleading wording

Status in nautilus-share package in Ubuntu:
  Confirmed

Bug description:
  The power saving section of system settings has the title "Power
  saving" (all GUI text is translated to English in this report, but I
  suspect the wording is similar enough in the English localization of
  the UI that the points still stand). There are some problems with that
  title in combination with the actual options in that section:

  - Screen backlight level
  - Automatic backlight level
  - Keyboard backlight level
  - Dim screen when inactive
  - Empty screen (after interval)
  - Automatic suspend
  - Wireless network: The wireless network can be turned off to save power.
  - Bluetooth: Bluetooth can be turned off to save power.

  1. Let's start with the problem with the two bottommost controls
  (wireless network, and bluetooth). Their subtitles in combination with
  the section title "Power saving" gives a very clear impression that
  these settings enable/disable *the ability for these components to be
  automatically turned off in order to save power*, but that's not what
  they do at all. They're just switches to turn off the components
  manually, as though the focus of this section weren't to automate
  power saving but to offer manual controls that are already available
  not only in their own respective setions of system settings, but
  readily available at any time in the global system menu in the top
  right corner of the desktop.

  There's no good reason to believe that the Power saving switches are
  just triply redundant instances of these already highly available
  switches, since no one is actually that interested in manually
  managing their power saving from a buried panel in system settings
  every time they decide to go battery powered or are critically low on
  battery. What's expected in this section are settings unique to power
  saving, like automating it during battery power, as opposed to just
  general preferences about whether you need wifi or bluetooth. It
  doesn't hurt to suggest turning the transmitters off in the power
  saving section, but doing it this way is misleading.

  I mistakenly turned off the Bluetooth transmitter in this way in an
  attempt to prevent the system from automatically power it off, during
  my efforts to troubleshoot Bluetooth. Needless to say, that didn't
  help, and I was later surprised to discover that Bluetooth was off.

  2. The other problem in the Power saving section is that many of the
  settings aren't really about power saving strategies -- they're just
  general preferences that would have to be adjusted manually every
  single time you want to save power:

  - Screen backlight level
  - Keyboard backlight level
  - Wireless network: The wireless network can be turned off to save power.
  - Bluetooth: Bluetooth can be turned off to save power.

  Sure, they technically have the potential to save power, but then they
  would have to be micromanaged all the time, i.e. not very useful in
  practice if you're using battery power on a daily basis. You would
  have to be extremely proactive for these settings to be preventative
  of needlessly draining your battery, and they're instead very likely
  going to be used when it's "too late" and you're already low on
  battery.

  Here are the ones actually concerned with power saving strategies,
  i.e. preventing battery from draining prematurely:

  - Automatic backlight level
  - Dim screen when inactive
  - Empty screen (after interval)
  - Automatic suspend

  Notice how you don't have to babysit these settings every time you
  decide to use battery power, and how they're actually focused on the
  problem of conserving power before it's too late.

  To alleviate these issues, the easiest quick fix would be to:

  1. either remove or change the subtitles of the two bottommost to
  something like "WiFi/Bluetooth can consume a lot of power" which
  succinctly explains why these switches are here while at the same time
  not misleading the reader to think the switches control something
  else.

  2. Move the "micromanagement settings" to their own section to clearly
  separate the more relevant "power conservation strategies" from the
  "general user preferences for components with potential for high power
  consumption that can be manually adjusted here if you're in a pinch
  and are critically low on battery".

  The less easy fix would of course be to offer automatic keyboard
  backlight levels instead of manual controls, and to offer actual
  automatic wifi and bluetooth power saving (if that's a thing). Not to
  mention

[Desktop-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-02-22 Thread Avamander

** Bug watch added: Debian Bug tracker #991597
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597

** Also affects: pulseaudio via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
   Importance: Unknown
   Status: Unknown

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Unknown
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

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


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

[Desktop-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options

** Changed in: pulseaudio (Debian)
   Status: New => Fix Committed

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

Title:
  AptX and AptX HD unavailable as Bluetooth audio quality options

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Committed

Bug description:
  Current situation:

  When one connects a Bluetooth audio device, at best one can choose
  between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback
  (A2DP Sink)". That is sad when the audio device supports AptX or AptX
  HD.

  
  Expected situation:

  One can select AptX or AptX HD as the Bluetooth audio output profile.

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


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

[Desktop-packages] [Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

** Changed in: libusb
   Status: Unknown => New

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

Title:
  fprintd crashed with SIGSEGV in log_v() from usbi_log() from
  libusb_unref_device()

Status in libusb:
  New
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libusb package in Ubuntu:
  Confirmed

Bug description:
  +

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.1-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb  7 21:58:32 2022
  ExecutablePath: /usr/libexec/fprintd
  InstallationDate: Installed on 2021-12-21 (50 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/libexec/fprintd
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8a7a3855f:call   *%rax
   PC (0x7fd8a7a3855f) ok
   source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region 
(needed readable region)!
   destination "(%rsp)" (0x7ffdceacc590) ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: fprintd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: fprintd crashed with SIGSEGV in libusb_unref_device()
  UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 1880586] Re: Serious regression (low FPS) in overview animation 3.36/20.04

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Serious regression (low FPS) in overview animation 3.36/20.04

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

Bug description:
  This is a downstream report to help track upstream
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697.

  The issue has been described at length (maybe excessively) upstream,
  so I'm pointing to a "sum up" comment here
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697#note_788658.

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


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

[Desktop-packages] [Bug 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

** Bug watch added: github.com/libusb/libusb/issues #1079
   https://github.com/libusb/libusb/issues/1079

** Also affects: libfprint via
   https://github.com/libusb/libusb/issues/1079
   Importance: Unknown
   Status: Unknown

** Project changed: libfprint => libusb

** Changed in: fprintd (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

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

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

Title:
  fprintd crashed with SIGSEGV in log_v() from usbi_log() from
  libusb_unref_device()

Status in libusb:
  Unknown
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libusb package in Ubuntu:
  Confirmed

Bug description:
  +

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.1-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb  7 21:58:32 2022
  ExecutablePath: /usr/libexec/fprintd
  InstallationDate: Installed on 2021-12-21 (50 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/libexec/fprintd
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8a7a3855f:call   *%rax
   PC (0x7fd8a7a3855f) ok
   source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region 
(needed readable region)!
   destination "(%rsp)" (0x7ffdceacc590) ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: fprintd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: fprintd crashed with SIGSEGV in libusb_unref_device()
  UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 1961565] Re: Package in bionic installs unnecessary build artifacts

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

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

Title:
  Package in bionic installs unnecessary build artifacts

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser source package in Bionic:
  New

Bug description:
  Not sure when this started happening, but today I noticed while
  testing chromium-browser 98.0.4758.102-0ubuntu0.18.04.1 that the
  chromium-browser binary package installs a lot of build artifacts that
  increase unnecessarily the size of the package.

  These artifacts include *.runtime_deps files, as well as binaries such
  as transport_security_state_generator or protozero_plugin.

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


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

[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO

** Description changed:

  [Impact]
  
-  * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some 
cases, the nvidia driver will probe later than launching gdm.
+  * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg 
with proprietary nvidia driver), in some cases, the nvidia driver will probe 
later than launching gdm.
   * If above race condition happens in iGPU + nvidia cases and monitor 
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg. 
Which may lead the monitor stuck in black-screen or boot LOGO.
  
  [Test Plan]
  
   * The environment:
    1. A desktop or workstation which containing an iGPU.
    2. Plug a nvidia graphic card to the system and installing proprietary
    nvidia driver (470 in my case)
    3. Attach a monitor to dGPU and leave iGPU connect to nothing.
    (in my test environment, there is the other ethernet card and TBT4 cards)
   * Setup a cronjob,
     e.g. @reboot /home/u/test.sh
   * Have a test script in something like /home/u/test.sh as
  
  #!/bin/bash
  
  sleep 20
  count="$(cat /home/ubuntu/count)"
  count=$((count+1))
  echo $count | tee /home/ubuntu/count
  journalctl -b | grep -q -i wayland || sudo reboot
  
   * the system will probably stuck in black-screen or boot LOGO.
   * Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
-  * After applying the fix, it got pass within 90 reboot cycles.
+  * After applying the fix, it got pass within 1000+ reboot cycles.
+  * Test PPA can be found here 
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
+ 
+ [Fix]
+  * The patch makes gpu-manager to probe nvidia (if needed) first and waiting 
for the /run/u-d-c-nvidia-drm-was-loaded be touched by 
71-u-d-c-gpu-detection.rules.
+  * Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking 
the nvidia driver presents or not.
+  * gpu-manager is before display-manager. Thus, gpu-manager will wait for 
nvidia uevent be processed and then continue to work. When gdm be launched, the 
targeted nvidia uevent has been processed already. 
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
  
  [Where problems could occur]
-  * The patch checkes device/boot_vga with tag "master-of-seat". If a system 
without any GPU as boot_vga then it will wait 10 seconds in the loop.
-  * I tried to detach all monitors from the system and the boot_vga still 
exist (default to use iGPU, the first device found during initialization)
-  * I don't think they will a case which boot_vga doesn't exist in this moment 
because:
- In drivers/gpu/vga/vgaarb.c (linux package)
- vga_arb_select_default_device() has a fallback function to determine the 
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
+  * there is not potential regression from my mind but it will lead the boot 
time be longer.
+  * In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms. 
Worst case, over 1 s in 8xx runs (of 1000).
+  * I think the stability is important than performance in this case.
+ 
+ [Other Info]
+  * For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm 
will meet this issue still. The other potential fix (from either gdm or logind) 
is under discussion in 
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786. 
  
  ---
  
  Test environment/steps:
  1. A desktop or workstation which containing an iGPU.
  2. Plug a nvidia graphic card to the system and installing proprietary nvidia 
driver (470 in my case)
  3. Attach a monitor to dGPU and leave iGPU connect to nothing.
  (in my test environment, there is the other ethernet card and TBT4 cards)
  4. Reboot system.
  
  Based on:
  $ cat /lib/udev/rules.d/61-gdm.rules
  # disable Wayland on Hi1710 chipsets
  ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", 
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
  # disable Wayland when using the proprietary nvidia driver
  DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
  
  It will disable wayland by default if proprietary nvidia driver load.
  But in some race condition cases, the nvidia probe is later than gnome 
launches. (The fail rate is 6/24.)
  Thus, ubuntu-gdm has a fix for Bug#1794280 to add 
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
  
  The gdm-wait-for-drm is intend to make sure all drm udev devices
  enumerated before launching gdm.
  
  It rely on at least one "master-of-seat" graphic card for gdm but it's not 
rigorous enough.
  Since most of graphic cards are own "master-of-seat"[1].
  
  In my case, it detects the iGPU is probed but dGPU.
  However, the display is attached to dGPU.
  
  We need to make sure the targeted gpu (connecting to monitor) is probe
  before launching gdm.
  
  debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
  upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
  
  [1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

We do need pipewire-media-session since according to GNOME upstream
without it gnome shell recording would just stay pause and not actually
work, unsure if that's still true so worth testing

** Also affects: pipewire-media-session (Ubuntu Jammy)
   Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
   Status: In Progress

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

Title:
  In Jammy sound level reset after reboot

Status in pipewire-media-session package in Ubuntu:
  In Progress
Status in pipewire-media-session source package in Jammy:
  In Progress

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package:

[Desktop-packages] [Bug 1961197] Re: gvfsd hangs on hanging filesystem

Thanks for the details, indeed it seems a special situation and not a
rls blocker

** Tags removed: rls-jj-incoming
** Tags added: rls-jj-notfixing

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

Title:
  gvfsd hangs on hanging filesystem

Status in gvfs package in Ubuntu:
  New

Bug description:
  This means that no file open dialog works anymore. I needed to restart
  gvfs-daemon.service twice today in order to attach two files in
  chrome.

  There seems to be some issue with samba, but not sure what it's trying
  to connect to or why it hangs the entire thing.

  Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem 
service...  

   
  Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service.  


  
  Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No 
compatible protocol selected by server. 


  Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$  


  
  Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem 
service...  

   
  Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service.  


  
  Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s 
CPU time.   

  
  Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem 
service...  

   
  Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service.  


  
  Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No 
compatible protocol selected by server. 


  Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$  


  
  Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem 
service...  

   
  Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service.  


  
  Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s 
CPU time.   

  
  Feb 17 13:02:42 jak-t480s systemd[5652]: Starting Virtual filesystem 
service...

[Desktop-packages] [Bug 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell

** Changed in: at-spi2-core (Ubuntu)
   Importance: Undecided => Low

** Changed in: at-spi2-core (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: at-spi2-core (Ubuntu)
   Importance: Low => High

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

Title:
  patch git_socket_dir.patch causing FTBFS in gspell

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  With this patch applied gspell is FTBFS with the following errors:

  Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
  Failed to connect to socket debian/home/.cache/at-spi/bus: No such
  file or directory

  I removed the patch and rebuilt this package in a PPA. When built
  against this PPA, gpsell is able to build again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+subscriptions


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

[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO

u-d-c for focal

** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562740/+files/0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff

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

Title:
[nvidia][xorg] display hangs on boot LOGO

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

Bug description:
[Impact]

* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.

[Test Plan]

* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as

#!/bin/bash

sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot

* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 90 reboot cycles.

[Where problems could occur]
* The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will wait 10 seconds in the loop.
* I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
* I don't think they will a case which boot_vga doesn't exist in this moment
because:
In drivers/gpu/vga/vgaarb.c (linux package)
vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.

---

Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.

Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".

The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.

It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].

In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.

We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.

debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763

[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules

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

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

[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO

u-d-c for impish

** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562739/+files/0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch

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

Title:
[nvidia][xorg] display hangs on boot LOGO

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

Bug description:
[Impact]

[Test Plan]

#!/bin/bash

sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot

---

The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.

It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].

In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.

We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.

debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763

[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules

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

[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO

u-d-c patch for jammy

** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562733/+files/0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch

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

Title:
[nvidia][xorg] display hangs on boot LOGO

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

Bug description:
[Impact]

[Test Plan]

#!/bin/bash

sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot

---

The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.

It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].

In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.

We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.

debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763

[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules

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

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

2022-02-22 Thread EML

I have a reproducible test case, but you need to set up for VNC (I have
a fresh 20.04 install, running headless, and this bug is a total PITA -
it's pretty much permanent. Note that it's worse than the screenshot
from comment #3 because the password is also viewable, and anyone can
come along, click the eye icon, and see my password). If you don't want
to vnc, see below.

In my case, I've installed the tigervnc server (tigervnc-standalone-
server).  Two changes to /etc/vnc.conf and you're good to go (note that
no custom xstartup is required):

# must do this to connect remotely
$localhost = "no";

# set to whatever your remote screen size is
$geometry = "3840x2160";

polkit has issues with remote access and pops up lots of 'Authentication
Required' windows. Eventually one will go in the top left corner and
stay there, with the described behaviour. I think, but I'm not sure,
that one way to trigger this is by hitting RET after entering your
password, rather than the Authenticate button. Note that you may have to
wait 10 or 15 minutes for another popup if the initial popups don't
trigger this bug.

I've added a local polkit policy to try to get rid of the popups, to try
to make a remote session look like a local session, which would
hopefully get rid of the popups, but this isn't yet working. The Alt
F2/r fix described above doesn't work.

If you don't want to run remotely over vnc, you should be able to
trigger this by changing the default polkit policy for an app you use.
See /usr/share/polkit-1/actions. A good one would be
org.freedesktop.color.policy, which is the one which traditionally
causes VNC problems ("create a color profile", etc). Find the 'allow
active' lines, and replace the 'yes' with something like
auth_admin/auth_admin_keep/auth_self_keep/etc. You'll then get the auth
popups when you log in, and various time afterwards.

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1961561] Re: [radeon] Blinking screen

2022-02-22 Thread Dash

Finally I could manage something, step #2
https://errors.ubuntu.com/user/9578793ceeb5644eebbc93a1c623f77177c6ec9f84bf04c4e4060e749cd18f2fe3e6806ff52ecc9de8fb1a7176ea8a61204188cebea751c0feba4e7c9ebd1a5a

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

Title:
  [radeon] Blinking screen

Status in compiz package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb 21 10:13:34 2022
  DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' 
produces an unwanted removal 'gnome-software-plugin-snap', skipping
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
     Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  InstallationDate: Installed on 2015-11-26 (2278 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.release: 2.10
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8061JND
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.product.sku: EW318AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Feb 21 10:00:44 2022
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.13-1ubuntu1~20.04.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1961561] Re: [radeon] Blinking screen

2022-02-22 Thread Dash

How can I connect to https://errors.ubuntu.com/user/ID if I have no
access to the web browser *FROM* the machine ? I only have console which
is usable.

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

Title:
  [radeon] Blinking screen

Status in compiz package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb 21 10:13:34 2022
  DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' 
produces an unwanted removal 'gnome-software-plugin-snap', skipping
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
     Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  InstallationDate: Installed on 2015-11-26 (2278 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.release: 2.10
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8061JND
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.product.sku: EW318AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Feb 21 10:00:44 2022
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.13-1ubuntu1~20.04.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

It might be possible to refine further if not all of these need
removing:

> with-audio = [
> metadata
> default-nodes
> default-profile
> default-routes
> alsa-seq
> alsa-monitor
> ]

Hard to tell because the docs either aren't built properly in places,
don't exist at all for some things, or are just too hard to find.

** Package changed: pipewire (Ubuntu) => pipewire-media-session (Ubuntu)

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

Title:
  In Jammy sound level reset after reboot

Status in pipewire-media-session package in Ubuntu:
  In Progress

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center

[Desktop-packages] [Bug 1961769] [NEW] Pulse audio doesn't switch to headset-input when microphone requested

2022-02-22 Thread Bartłomiej Żogała

Public bug reported:

I've recently upgraded 2 versions - from Ubuntu 18.04 LTS to 20.04 LTS
and then to 21.10.  Before I was able to both listen quality audio and
speak over my headset. Right now after some time of struggling with why
I can't use bluetooth microphone anymore I've realised it's because it
used A2DP profile which doesn't support mic input. I can't check it now
but pretty sure microphone usage was seamless in past - I didn't need to
manually switch to HFP/HSP and then back to A2DP to listen music. Can we
reintroduce this functionality ?

"nusch@xps13:~$ LANG="en" pactl list | grep -iA 100 jabra
Description: Jabra Evolve 65
Driver: module-bluez5-device.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 26
Mute: no
Volume: front-left: 56763 /  87%,   front-right: 0 /   0%
balance -1.00
Base Volume: 65536 / 100%
Monitor Source: bluez_sink.30_50_75_07_11_8C.a2dp_sink.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_VOLUME_CTRL LATENCY 
Properties:
bluetooth.protocol = "a2dp_sink"
bluetooth.codec = "sbc"
device.description = "Jabra Evolve 65"
device.string = "30:50:75:07:11:8C"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_30_50_75_07_11_8C"
bluez.class = "0x240404"
bluez.alias = "Jabra Evolve 65"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Ports:
headset-output: Słuchawki z mikrofonem (type: Headset, 
priority: 0, availability unknown)
Active Port: headset-output
Formats:
pcm

Source #1
State: SUSPENDED
Name: alsa_output.pci-_00_1f.3.analog-stereo.monitor
Description: Monitor of Wbudowany dźwięk Analogowe stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 22
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: alsa_output.pci-_00_1f.3.analog-stereo
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Wbudowany dźwięk Analogowe 
stereo"
device.class = "monitor"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0x60531d8000 irq 188"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "a0c8"
device.product.name = "Tiger Lake-LP Smart Sound Technology 
Audio Controller"
device.form_factor = "internal"
device.string = "0"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Formats:
pcm

Source #20
State: SUSPENDED
Name: bluez_sink.30_50_75_07_11_8C.a2dp_sink.monitor
Description: Monitor of Jabra Evolve 65
Driver: module-bluez5-device.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 26
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: bluez_sink.30_50_75_07_11_8C.a2dp_sink
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Jabra Evolve 65"
device.class = "monitor"
device.string = "30:50:75:07:11:8C"
device.api = "bluez"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_30_50_75_07_11_8C"
bluez.class = "0x240404"
bluez.alias = "Jabra Evolve 65"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Formats:
pcm

Sink Input #58
Driver: protocol-native.c
Owner Module: 10
Client: 106
Sink: 14
Sample Specification: s16le 2ch 44100Hz

[Desktop-packages] [Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Opinion => Won't Fix

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

Title:
  Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool
  InterfacePrototype::has_instance_impl(JSContext*, const
  JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu-
  d...@ubuntu.com/locations.js:1108

Status in gjs package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  Hardware: https://linux-hardware.org/?probe=1055dc7082

  Worked without Problem in 21.04
  Had some flicker and problem with the left dock in 21.10
  not working since updating to 22.04

  now I'm running xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 15 08:07:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-15 (183 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

The offending package seems to be coming via:

ubuntu-meta >
gnome-remote-desktop >
pipewire-media-session | wireplumber

So it's a dependency we probably can't drop. Maybe a config change is
the only real option.

** No longer affects: alsa-utils (Ubuntu)

** No longer affects: pulseaudio (Ubuntu)

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

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

Title:
  In Jammy sound level reset after reboot

Status in pipewire package in Ubuntu:
  In Progress

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

** Changed in: alsa-utils (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pipewire (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  In Jammy sound level reset after reboot

Status in pipewire package in Ubuntu:
  In Progress

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname:

[Desktop-packages] [Bug 1954765] Re: Firefox instance opens with an unusable window that has the content area filled with the frozen image of the window/desktop image in the background

2022-02-22 Thread Guruprasad

This issue happened on a laptop of mine with a hybrid GPU setup. It
reliably went away after I switched my GPU settings from 'Intel (Power
saving mode)' to 'NVIDIA On-Demand'. I am not sure why that is the case.
I got the solution within a week or so after I reported this bug. So
yes, this issue is not happening any more.

If it will help, I can switch to the 'Intel (Power saving mode)' and
test if the issue happens again.

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

Title:
  Firefox instance opens with an unusable window that has the content
  area filled with the frozen image of the window/desktop image in the
  background

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After a recent Firefox update (I think this started after the Firefox
  95 upgrade), opening Firefox often opens a window with a visible title
  bar that indicates that the application in focus is Firefox but the
  content area is invisible because it has the frozen image/background
  of either the windows/application behind the Firefox window or the
  desktop background image if there are no windows behind Firefox.

  The Firefox shortcut keys work and I am able to open a site by
  pressing Ctrl+L to focus the address bar and type a domain name/URL.
  The website/URL loads okay but nothing is visible because of the
  content area being hidden by the frozen image.

  Resizing/minimizing+maximizing the Firefox window doesn't resolve this
  issue. However, when I launch Firefox from the terminal, it works
  properly every single time. So it looks like there might be some issue
  only when launching from the Firefox application launcher (.desktop
  file).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 95.0+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guruprasad   4057 F pulseaudio
  BuildID: 20211129150630
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Dec 14 17:17:46 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-12-02 (12 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlp59s0 proto dhcp metric 600 
   10.154.85.0/24 dev lxdbr0 proto kernel scope link src 10.154.85.1 
   169.254.0.0/16 dev lxdbr0 scope link metric 1000 
   192.168.0.0/24 dev wlp59s0 proto kernel scope link src 192.168.0.102 metric 
600
  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:363
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=94.0/20211028161635 (Out of date)
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=95.0/20211129150630 (In use)
   Profile2 - LastVersion=95.0/20211129150630 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2021
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell

[Desktop-packages] [Bug 1961565] Re: Package in bionic installs unnecessary build artifacts

2022-02-22 Thread Olivier Tilloy

With the following changes:

  - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/bionic-beta/revision/1616
  - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/bionic-beta/revision/1617

version 99.0.4844.35 (currently in the beta channel) goes from:

  Download-Size: 84,7 MB
  Installed-Size: 283 MB

to:

  Download-Size: 77,7 MB
  Installed-Size: 250 MB

i.e. a net gain of 7 MB in compressed size, and 33 MB in installed size.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Package in bionic installs unnecessary build artifacts

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser source package in Bionic:
  New

Bug description:
  Not sure when this started happening, but today I noticed while
  testing chromium-browser 98.0.4758.102-0ubuntu0.18.04.1 that the
  chromium-browser binary package installs a lot of build artifacts that
  increase unnecessarily the size of the package.

  These artifacts include *.runtime_deps files, as well as binaries such
  as transport_security_state_generator or protozero_plugin.

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


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

[Desktop-packages] [Bug 1827735] Re: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped"

2022-02-22 Thread moma

Hello,
Some applications monitor the DBus for Start/Pause/Stop-messages from media 
players.
When an audio track ends (in Totem), it should send a "Stop" message so other 
applications can update their status properly.

For example, audio-recorder shows "Paused" status for Totem even Totem has 
Stopped. 
Audio-recorder can stop/pause/continue/stop recording based on messages on DBus.

Audio-recorder is now quite old and ought to be re-written. There is now 
PipeWire that replaces Pulseaudio, and it is now possible to record individual 
streams (audio from individual applications). 
Ref. https://launchpad.net/audio-recorder

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

Title:
  DBus/MPRIS2: Totem says it is "Paused" even the stream has ended
  "Stopped"

Status in Totem:
  Fix Released
Status in totem package in Ubuntu:
  Triaged

Bug description:
  Hello,

  Question 1:
  ===
  When asking status of Totem via DBus/MPRIS2, it says "Paused" even the song 
has ended. Shouldn't it return "Stopped" state.

  
  I am using a small bash-script to see the DBus-messages.

  $ ./debug1.sh

  org.mpris.MediaPlayer2.rhythmbox says: I AM PLAYING.
  Confirmed state is: (<'Playing'>,)
  -

  Then the song ends.

  org.mpris.MediaPlayer2.rhythmbox says: I AM PAUSED.
  Confirmed state is: (<'Paused'>,)
  

  Question 2:
  ===
  GNOME's Music player is "org.gnome.Music".

  GNOME's Video player is: "org.mpris.MediaPlayer2.totem"

  Why this difference?

  I like both products.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  4 19:24:02 2019
  InstallationDate: Installed on 2019-03-06 (58 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


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

[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound

2022-02-22 Thread Léo Pajot

I began facing this bug starting this very week on a quite recent
install, even though I have been using 20.04 LTS for quite some time now
(but not on this specific machine). Appeared while using Discord
(installed through a .deb package) in parallel with Firefox. I also had
Spotify open in Firefox, which implies DRM code running, that maybe
could interfere with the sounds outputted by my machine ?

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions


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

[Desktop-packages] [Bug 1961561] Re: [radeon] Blinking screen

That's just step 1, so try step 2.

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

Title:
  [radeon] Blinking screen

Status in compiz package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Binking screen with radeon after upgrade 18.04 to 20.04 - Console OK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb 21 10:13:34 2022
  DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' 
produces an unwanted removal 'gnome-software-plugin-snap', skipping
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
     Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  InstallationDate: Installed on 2015-11-26 (2278 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2021-03-08 (349 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.release: 2.10
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8061JND
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:br2.10:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:skuEW318AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.product.sku: EW318AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Feb 21 10:00:44 2022
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.13-1ubuntu1~20.04.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1959502] Re: U2F not connected in snap package