date:20220406

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

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

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

Title:
  gnome-keyring-daemon crashed with signal 7

Status in gnome-keyring package in Ubuntu:
  Confirmed

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

  gnome-keyring:
Installed: 40.0-3ubuntu1
Candidate: 40.0-3ubuntu1
Version table:
   *** 40.0-3ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  Background process crashes unexpectedly a few moments after login.

  I'm running the dev release of Jammy on a Raspberry Pi 400 with all
  updates applied.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-keyring 40.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Mon Mar 14 15:26:41 2022
  Disassembly: => 0x:   Cannot access memory at address 0x
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  ImageMediaBuild: 20201022
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 7
  SourcePackage: gnome-keyring
  StacktraceTop:
   ()
   ()
   () at /lib/aarch64-linux-gnu/libgio-2.0.so.0
   g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-keyring-daemon crashed with signal 7
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1964795/+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 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

2022-04-06 Thread Alex Murray

I can reproduce this by just running `sudo systemctl restart
udisks2.service` - will see if I can perhaps run it under valgrind and
see where the memory corruption is happening.

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

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
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/udisks2/+bug/1964532/+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 1944113] Re: Many UI elements (list box, drop down) don't work at all in kf5 environment

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1944113]

2022-04-06 Thread Libreoffice-commits

Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to "libreoffice-7-3":

https://git.libreoffice.org/core/commit/c309ddb6d9cd61f3024ffeee33fce1a0e173d9cc

tdf#144585 Qt fix Wayland LO fake popups

It will be available in 7.3.3.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1938735]

2022-04-06 Thread Xiscofauli

I wrote a unittest for this issue
 but it hits an assert.

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

Title:
  Can't insert a row into a OpenOffice calc file

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  Won't Fix

Bug description:
  Mexican coin inventory is a large Calc file - 57.3 KB. I cannot insert a row 
into this file without a crash, however I can add a line to the bottom of the 
file. Ubuntu Error Tracker contains multiple crash reports similar to this one: 
 
  2021-08-02 17:08  2021-08-02 22:08 UTCCrash   libreoffice-core

  at this URL.
  
https://errors.ubuntu.com/user/6b8e33fe437c1034a81072912cfe9c22792a3f69c4d33e45a69c800783a88079fb6601dc059840bc806cd850c6efecc383497b22497a8c8536c063887939dd99

  I will attach the file to this report.

  Thank You,
  Duane Palmer

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 17:32:40 2021
  InstallationDate: Installed on 2021-06-30 (33 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1938735/+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 1944113]

2022-04-06 Thread Libreoffice-commits

Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/fbf739198aa7f02975d531521c6525073783c7f1

tdf#144585 Qt fix Wayland LO fake popups

It will be available in 7.4.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 548866] Re: forgets middlemouse.contentLoadURL on upgrade or browser restart

** Changed in: firefox
   Status: In Progress => Confirmed

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

Title:
  forgets middlemouse.contentLoadURL on upgrade or browser restart

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in firefox source package in Lucid:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in firefox source package in Precise:
  Won't Fix

Bug description:
  Binary package hint: firefox

  Whenever firefox is updated, the setting for
  middlemouse.contentLoadURL is forgotten in my profiles.

  To simulate this:

  0) go to "about:config" and set middlemouse.contentLoadURL to "true"
  1) close firefox
  2) remove .mozilla/firefox/[profile]/compatibility.ini
  3) open firefox
  4) observe setting has reverted to "false"

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/548866/+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 828413] Re: Firefox places downloads to irrelevant directories

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=118924.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2002-01-09T08:34:04+00:00 pype wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801
BuildID:2001080104

I usually put MP3 in a different directory than PDF files, which is not either
the one i use for pictures, etc.
It would be really great if mozilla was smart enough to pick the target
directory of a saved file based on its mime type (plus some user preference)
rather than storing every file in the last used directory ...

An intermediate feature would be to support a list of user's favourite store
location.

Reproducible: Always
Steps to Reproduce:
1. Download a tarball and put it into "install"
2. Download a mp3 and save it into "music"
3. Download a tarball again

Actual Results:  aargh! you have to go back manually into "install" from
music :(

Expected Results:  mozilla "see" (or i told it before) i like storing tarballs
into "install" and open the save dialog with that directory rather than
the last directory used.

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/0


On 2002-01-09T10:15:13+00:00 Lhirlimann wrote:

Reporter could you add [RFE] in your bug's description ? and change OS
=> ALL ?

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/1


On 2002-01-09T17:13:39+00:00 Alex-mozillazine wrote:

Nice idea. Modern Windows versions have folders such as My Documents, My 
Pictures, My Music and My Videos (they can be placed on older systems by other 
software but the locations aren't always consistent e.g. Windows Media Player 
prefers C:\My Documents\My Music whereas RealJukebox prefers C:\My Music). 
These could serve as useful defaults on that platform. It should be possible to 
customise these locations (and the MIME types), at the very least with a hidden 
pref or possibly heuristics.

Marking NEW.

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/2


On 2002-01-09T19:01:03+00:00 Bugzilla-iwaruna wrote:

file handling

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/3


On 2002-04-04T06:12:57+00:00 Ipottinger wrote:

adding self to cc list

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/4


On 2008-03-15T12:40:47+00:00 Jruderman wrote:


*** This bug has been marked as a duplicate of bug 405146 ***

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/5


On 2013-11-15T12:26:35+00:00 Deletesoftware+moz wrote:

*** Bug 405146 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/16


On 2013-11-15T12:27:00+00:00 Deletesoftware+moz wrote:

*** Bug 680580 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/18


On 2022-04-06T13:56:54+00:00 Release-mgmt-account-bot wrote:

The bug assignee didn't login in Bugzilla in the last 7 months.
:Gijs, could you have a look please?
For more information, please visit [auto_nag 
documentation](https://wiki.mozilla.org/Release_Management/autonag#assignee_no_login.py).

Reply at: https://bugs.launchpad.net/firefox/+bug/828413/comments/21


** Changed in: firefox
   Status: Unknown => Confirmed

** Changed in: firefox
   Importance: Unknown => Medium

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

Title:
  Firefox places downloads to irrelevant directories

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox places downloaded files to irrelevant directories to the downloaded 
file type, for ex.
  saves .mp3 to 'Downloads' directory not to 'Music'
  saves .doc to 'Downloads' directory not to 'Documents'
  though it saves video files to 'Video' directory not to 'Downloads'

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Po

[Desktop-packages] [Bug 548866]

2022-04-06 Thread Release-mgmt-account-bot

The bug assignee didn't login in Bugzilla in the last 7 months.
:KrisWright, could you have a look please?
For more information, please visit [auto_nag 
documentation](https://wiki.mozilla.org/Release_Management/autonag#assignee_no_login.py).

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

Title:
  forgets middlemouse.contentLoadURL on upgrade or browser restart

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in firefox source package in Lucid:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in firefox source package in Precise:
  Won't Fix

Bug description:
  Binary package hint: firefox

  Whenever firefox is updated, the setting for
  middlemouse.contentLoadURL is forgotten in my profiles.

  To simulate this:

  0) go to "about:config" and set middlemouse.contentLoadURL to "true"
  1) close firefox
  2) remove .mozilla/firefox/[profile]/compatibility.ini
  3) open firefox
  4) observe setting has reverted to "false"

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/548866/+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 1968099] [NEW] gnome shell crashes after disconnecting external monitors

2022-04-06 Thread Rafal

Public bug reported:

Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

After disconnecting external monitors Gnome crashes:
- logged out to login screen
- after login there is new session

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  7 00:51:54 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-01-12 (84 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

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


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

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1968094] [NEW] BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy

2022-04-06 Thread Milan Ulej

Public bug reported:

= Description =
On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem, 
root subvolume (subvol=@) is always mounted as read only. There is a kernel 
flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by 
script /usr/sbin/update-grub during every kernel update. Only home subvolume 
(@home) is actually mounted as rw according to fstab which is correct.
Image: Jammy Beta (220330)

= Steps to Reproduce =
1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS 
(subvolumes @ and @home are created)
2. Launch the kernel via the default grub entry

= Expected Results =
root / should be mounted as rw (mount -v | grep @), there should be no (ro) 
flag on /proc/cmdline

= Actual Results =
in grub.cfg:
linux   /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... 
rootflags=subvol=@ ro quiet splash $vt_handoff
in /proc/cmdline:
BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

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

Title:
  BTRFS root subvolume @ mounted always as readonly (... ro
  rootflags=subvol=@ ...) on Jammy

Status in network-manager package in Ubuntu:
  New

Bug description:
  = Description =
  On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem, 
root subvolume (subvol=@) is always mounted as read only. There is a kernel 
flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by 
script /usr/sbin/update-grub during every kernel update. Only home subvolume 
(@home) is actually mounted as rw according to fstab which is correct.
  Image: Jammy Beta (220330)

  = Steps to Reproduce =
  1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS 
(subvolumes @ and @home are created)
  2. Launch the kernel via the default grub entry

  = Expected Results =
  root / should be mounted as rw (mount -v | grep @), there should be no (ro) 
flag on /proc/cmdline

  = Actual Results =
  in grub.cfg:
  linux   /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... 
rootflags=subvol=@ ro quiet splash $vt_handoff
  in /proc/cmdline:
  BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1968094/+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 1900347] Current status

2022-04-06 Thread Larry C.

Dear Mr. Bacher,

I am a linux novice.  You responded to a bug report I made in Oct
20, 2020.  On February 26, 2021 there was a updated report posted here:

https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1900347

So has this bug been fixed? If so were would the fixed package be?  If
not when and how do bugs like this get resolved?

Thanks,

Larry C.

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

Title:
  Doesn't import gpg keys Doesn't export armored (asc) gpg keys

Status in seahorse:
  Unknown
Status in seahorse package in Ubuntu:
  Fix Committed

Bug description:
  Very similar to bug # 1577198.  Seahorse (Passwords and Keys) won't
  import gpg keys.  But if I double click on the gpg key in the file
  manager it will show as imported after I restart Seahorse. After keys
  are imported (using the double click method or CLI) they can only be
  exported as binary keys i.e. keyname.pgp.  If I try the option to
  export as a keyname.asc version (armored) I only get the same binary
  key.  Everything works fine with gpg in a terminal.

  This is with a fresh install of 20.04.1,  Seahorse 3.36-1 with
  Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is
  2.2.19

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: seahorse 3.36-1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 18 11:32:13 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-10-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/1900347/+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 27867]

2022-04-06 Thread Technologicz12

Technology Write For Us (Guest Post) – Tech, Social Media, Business, Marketing, 
Gadgets, AI, IoT, Big Data, VoIP
https://technologicz.com/write-for-us-technology/

Write for us Guest post Technology, Business, Education, Software, Game
https://technologicz.com/write-for-us-guest-post/

Rarbg Proxy Unblock Rarbg Proxy List mirrors 
https://technologicz.com/rarbg-proxy/

TamilBlasters Proxy Unblocked TamilBlasters Proxy List [100% Working] Sites
https://technologicz.com/tamilblasters-proxy/

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

Title:
  Background color is always white, top banner is never displayed in
  Firefox

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

Bug description:
  Problem shows whatever the version of Epiphany (before and after today's 
upodate
  ie).

  Whatever the website I visit, the background colour is always white, and the
  logo/banner at the top of the page, is not displayed.

  I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and
  no yellow background.

  http://bugzilla.gnome.org/show_bug.cgi?id=121118:
  http://bugzilla.gnome.org/show_bug.cgi?id=121118

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/27867/+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 1968081] Re: [FFe] [UIFe] gnome-characters 42

fossfreedom, thanks for looking into this. This feature is not important
enough to cause a regression for Ubuntu Budgie this late in the
development cycle.

We do plan to let these libadwaita app autosync once 22.10 development
starts though.

** Changed in: gnome-characters (Ubuntu)
Status: New => Invalid

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
Invalid

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert
if there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

* New upstream release
- Supports Unicode 14
- Support for Emoji Sequences and Modifiers is planned
for the 43 release
* Drop all patches: applied in new release
* Switch to gtk4 and libadwaita instead of gtk3 and libhandy
* debian/control.in: Switch from gnome-desktop 3 to gnome-desktop 4
* debian/control.in: Drop obsolete Build-Depends on libunistring

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

Install:
$ sudo apt install ./gnome-characters_42.0-1_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'gnome-characters' instead of
'./gnome-characters_42.0-1_amd64.deb'
The following additional packages will be installed:
gir1.2-gnomedesktop-4.0
The following NEW packages will be installed:
gir1.2-gnomedesktop-4.0
The following packages will be upgraded:
gnome-characters
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,660 B/385 kB of archives.
After this operation, 2,655 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /home/jeremy/devel/temp/gnome-characters_42.0-1_amd64.deb
gnome-characters amd64 42.0-1 [379 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu jammy/main amd64
gir1.2-gnomedesktop-4.0 amd64 42.0-1ubuntu1 [5,660 B]
Fetched 5,660 B in 1s (9,886 B/s)
Selecting previously unselected package gir1.2-gnomedesktop-4.0:amd64.
(Reading database ... 209429 files and directories currently installed.)
Preparing to unpack .../gir1.2-gnomedesktop-4.0_42.0-1ubuntu1_amd64.deb ...
Unpacking gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
Preparing to unpack .../gnome-characters_42.0-1_amd64.deb ...
Unpacking gnome-characters (42.0-1) over (41.0-4) ...
Setting up gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
Setting up gnome-characters (42.0-1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for libglib2.0-0:amd64 (2.72.0-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1968081/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-04-06 Thread Umair Iqbal

The same error when executing UIO tests in eclipse under docker
environment

[xcb] Unknown sequence number while processing reply
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been 
called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:702: _XReply: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/108

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

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

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

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert
if there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

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

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

2022-04-06 Thread fossfreedom

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

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert
if there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

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

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

2022-04-06 Thread fossfreedom

From a Ubuntu Budgie point of view, the new libadwaita app looks out of
place in our distro with adwaita's ghastly dark brown colouration. With
a GTK_THEME based override the headerbar looks broken with our default
theme (i.e. we would have used this to suggest this type of workaround
for folk that wants to use a non libadwaita theme).

However - we will not die in a ditch on this. If Ubuntu really wants
this then we would request that "ubuntu-budgie-meta" be added as
affected and we will need to use this UIFe as a way to remove gnome-
characters from our seeds - i.e. we will not ship with the app.

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert
if there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

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

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

[Desktop-packages] [Bug 1943768] Re: gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale

This bug was fixed in the package ubiquity - 22.04.12

---
ubiquity (22.04.12) jammy; urgency=medium

  [ Gunnar Hjalmarsson ]
  * Update the localechooser subtree from 2.89ubuntu3
(lp: #1943768, #1966530)
  * Automatic update of included source packages: localechooser
2.89ubuntu3.

  [ Dimitri John Ledkov ]
  * Switch kernel flavours [oem|hwe]-20.04 to [oem|hwe]-22.04.

 -- Dimitri John Ledkov   Wed, 06 Apr 2022
15:12:50 +0100

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

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

Title:
  gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in localechooser package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  Per https://lists.ubuntu.com/archives/ubuntu-
  devel/2021-September/041616.html, Sri Lanka has a national keyboard
  standard, wijesekera, which is implemented by ibus-m17n but which is
  not being used by default.  We should add si_LK to the list of locales
  for which we use m17n.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1943768/+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 1968081] [NEW] [FFe] [UIFe] gnome-characters 42

Public bug reported:

Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert if
there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:
https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

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

** Tags: jammy

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
--

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

** Attachment added: "gnome-characters42.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1968081/+attachment/5577714/+files/gnome-characters42.png

** Description changed:

Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Comment
---
GNOME Characters 42 still doesn't support emoji modifiers and sequences which
is a really big omission for an emoji app. There is a merge proposal for
version 43 and it may be worth a major SRU for 22.04 LTS later.
+
+ Other UI comments
+ -
+ The sidebar has switched to monochrome symbolic icons instead of fullcolor.
+
+ It looks like the selection highlight color is gray instead of the
+ Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
+ sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert if
there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

- * New upstream release
- - Supports Unicode 14
- - Support for Emoji Sequences and Modifiers is planned
- for the 43 release
- * Drop all patches: applied in new release
- * Switch to gtk4 and libadwaita instead of gtk3 and libhandy
- * debian/control.in: Switch from gnome-desktop 3 to gnome-desktop 4
- * debian/control.in: Drop obsolete Build-Depends on libunistring
+ * New upstream release
+ - Supports Unicode 14
+ - Support for Emoji Sequences and Modifiers is planned
+ for the 43 release
+ * Drop all patches: applied in new release
+ * Switch to gtk4 and libadwaita instead of gtk3 and libhandy
+ * debian/control.in: Switch from gnome-desktop 3 to gnome-desktop 4
+ * debian/control.in: Drop obsolete Build-Depends on libunistring

- -- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400
+ -- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

Install:
- $ sudo apt install ./gnome-characters_42.0-1_amd64.deb
+ $ sudo apt install ./gnome-characters_42.0-1_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'gnome-characters' instead of
'./gnome-characters_42.0-1_amd64.deb'
The following additional packages will be installed:
- gir1.2-gnomedesktop-4.0
+ gir1.2-gnomedesktop-4.0
The following NEW packages will be installed:
- gir1.2-gnomedesktop-4.0
+ gir1.2-gnomedesktop-4.0
The following packages will be upgraded:
- gnome-characters
+ gnome-characters
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,660 B/385 kB of archives.
After this operation, 2,655 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /home/jeremy/devel/temp/gnome-characters_42.0-1_amd64.deb
gnome-characters amd64 42.0-1 [379 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu jammy/main amd64
gir1.2-gnomedesktop-4.0 amd64 42.0-1ubuntu1 [5,660 B]
- Fetched 5,660 B in 1s (9,886 B/s)
+ Fetched 5,660 B in 1s (9,886 B/s)
Selecting previously unselected package gir1.2-gnomedesktop-4.0:amd64.
(Reading database ... 209429 files and directories currently installed.)
Preparing to unpack .../gir1.2-gnomedesktop-4.0_42.0-1ubuntu1_amd64.deb ...
Unpacking gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
Preparing to unpack .../gnome-characters_42.0-1_amd64.deb ...
Unpacking gnome-characters (42.0-1) over (41.0-4) ...
Setting up gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
Setting up gnome-characters (42.0-1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for libglib2.0-0:amd64 (2.72.0-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

** Attachment added: "gnome-characters41.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1968081/+attachment/5577713/+files/gnome-characters41.png

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

Title:
[FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
New

Bug description:
Benefit
---
The new GNOME Characters app significantly improves the usability of the app,
upgrading the Unicode support from something like Unicode 9 all the way to
Unicode 14.

The new version also removes the horizontal lines that the emoji are
resting on. I think the UI is better without those lines.

Other UI comments
-
The sidebar has switched to monochrome symbolic icons instead of fullcolor.

It looks like the selection highlight color is gray instead of the
Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
sidebar.)

Why This Wasn't Done Sooner
---
GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04
today.

Risks and Mitigation

This version is already present in Debian Testing without new reported bugs.

Both Ubuntu and Ubuntu Budgie includes this app by default.

The app is standalone and does not impact other apps. We could revert
if there were a major bug discovered.

Changes
---
https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

gnome-characters (42.0-1) unstable; urgency=medium

-- Jeremy Bicha Sat, 19 Mar 2022 13:36:05 -0400

Logs

Build:

https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

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

[Desktop-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0

2022-04-06 Thread Steve Langasek

> https://github.com/libarchive/libarchive/releases/tag/v3.6.0

This looks fine.

> https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

I'm not reading this. An FFe request should include a human-readable
*summary* of upstream feature-freeze-breaking that may introduce risk of
regression; a git log is not that.

FFe granted.

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

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

Title:
[FFe] update libarchive to 3.6.0

Status in evince package in Ubuntu:
New
Status in libarchive package in Ubuntu:
Triaged

Bug description:
I request a Feature Freeze Exception to update libarchive from 3.5.2
to 3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

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

[Desktop-packages] [Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

2022-04-06 Thread Treviño

Upstream issue is https://gitlab.gnome.org/GNOME/mutter/-/issues/2216

Proposed fix:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2368

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

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

  A similar behavior can also be observed in gedit, nautilus and other
  GNOME applications whether they are confined or not (while snapped
  ones seems to underline the issue more)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

2022-04-06 Thread Sascha Lucas

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

** This bug has been marked a duplicate of bug 1967901
   [qxl] Xorg fails to start with "Screen(s) found, but none have a usable 
configuration."

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

glib doesn't support `x-terminal-emulator` so the first found supported
terminal emulator (which will be mate-terminal in Ubuntu MATE) will be
used, regardless of what preferred applications or alternatives have
been configured.

This is why panels/launchers will favour mate-terminal in Ubuntu MATE.

** Changed in: mate-desktop-environment (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

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

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

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

** Changed in: mate-desktop-environment (Ubuntu)
   Status: New => Confirmed

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Triaged
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Triaged
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

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

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

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

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

  A similar behavior can also be observed in gedit, nautilus and other
  GNOME applications whether they are confined or not (while snapped
  ones seems to underline the issue more)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

2022-04-06 Thread Sascha Lucas

adding Xorg crash dump

** Attachment added: "Xorg crash dump"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+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 1968063] [NEW] Jammy: Xorg crash on virtual QXL graphics

2022-04-06 Thread Sascha Lucas

Public bug reported:

Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
Server will not start. Either directly via lightdm or via gdm/wayland
selecting Xubuntu session.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  6 17:59:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash jammy ubuntu

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-

[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser

2022-04-06 Thread Leonora Tindall

Is there a more appropriate place to file this bug? It's only a low
priority if you consider all KDE-related issues low priority; for KDE
users, I'd argue that it is a pretty high priority!

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

Title:
  Firefox snap cannot be set as default browser

Status in firefox package in Ubuntu:
  New

Bug description:
  I was unable to set Firefox as the default browser by going to
  Settings -> Applications -> Default Applications -> Web browser. It
  was set to Other... and web links opened in Kate.

  In addition, I was unable to report a bug against Firefox because "it
  is provided by a snap provided by Mozilla."

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:54:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20L50067US
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L50067US
  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.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L50067US
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+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 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."

This bug was fixed in the package xserver-xorg-video-qxl -
0.1.5+git20200331-3

---
xserver-xorg-video-qxl (0.1.5+git20200331-3) unstable; urgency=medium

  * configure-Simplify-fragile-libdrm-detection.patch: Fix detecting
qxl_drm.h. (LP: #1967901)

 -- Timo Aaltonen   Wed, 06 Apr 2022 10:23:41 +0300

** Changed in: xserver-xorg-video-qxl (Ubuntu)
   Status: New => Fix Released

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

Title:
  [qxl] Xorg fails to start with "Screen(s) found, but none have a
  usable configuration."

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Desktop Jammy 20220405

  It fails to boot to the live session in virt-manager and gnome-boxes.
  ubiquity-dm starts fine but the live session does. The graphical session 
keeps dying. 

  If I switch from QXL to Virtio then it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+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 1962593] Re: SMB Mount to backup directory prevents mounting parent directories

2022-04-06 Thread Dan Sorak

** Summary changed:

- SMB Mount to backup directory prevents mounting parent directory
+ SMB Mount to backup directory prevents mounting parent directories

** Summary changed:

- SMB Mount to backup directory prevents mounting parent directories
+ SMB Mount to backup directory prevents mounting parent directories of share

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

Title:
  SMB Mount to backup directory prevents mounting parent directories of
  share

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
    - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * Can happen at semi-random times if the backup is on a schedule
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time
  * Prevents access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in 
nautilus
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out or the backup 
process exits

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1962593/+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 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2022-04-06 Thread michael kosko

This issue is still present. I just did a fresh 20.04.4 installation and
tracker still used high CPU at system startup until I disabled it.

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+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

Re: [Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions

2022-04-06 Thread BertN45

I don't use a wayland session. Also on the first login screen the xorg
session has been selected in the menu. I understand vmwgfx is the
VMware Linux graphics driver also used by Virtualbox for exposing
3D/OpenGL/3D hardware acceleration to guest virtual machines. Switching
off 3D acceleration did not help. 

Remains the fact that the problem only shows up in Ubuntu 22.04 and not
in Ubuntu 22.04; Ubuntu Mate 22.04 nor in any 20.04 version or in
Fedora 36 Beta also with Gnome 42. 

Curious, do you have any cooperation with the VBox maintainers?

On Wed, 2022-04-06 at 02:35 +, Daniel van Vugt wrote:
> BertN45: The only error that stands out to me in your log is that the
> vmwgfx kernel driver keeps logging:
> 
>   kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open
> channel.
> 
> If that's the problem then it's a bug in the kernel (where the vmwgfx
> driver lives) and/or the hypervisor.
> 
> Otherwise the log shows that the Wayland session starts successfully
> and
> tries to register itself with GDM. And 30 seconds later, GDM starts a
> Xorg session.
> 
> ** Tags added: vmwgfx
>

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

Title:
  login screen shown twice with VirtualBox Guest Additions

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1968046] Re: No printer found after libreoffice version snap update

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

https://github.com/snapcore/snapd/pull/11616

** This bug has been marked a duplicate of bug 1967799
   firefox, chromium and other snap apps can't print

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

Title:
  No printer found after libreoffice version snap update

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After the last update of the LibreOffice snap (ver. 7.3.2.2), LibreOffice 
can't find any printer in my system and I can't print. 
  Other applications continue to print correctly in my network installed 
printer.

  I'm attaching a screenshot where you can see the LibreOffice interface
  where no printer can be find and my system printer

  -Ubuntu release.
  Ubuntu 20.04.4 LTS

  -Updated LibreOffice.
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968046/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-04-06 Thread Stefan Fleischmann

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

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776800/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-06 Thread Łukasz Zemczak

Not an expert in seeds, but the changes made sense. Merged and pushed!

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)

2022-04-06 Thread Treviño

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

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

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

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => In Progress

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Tags added: rls-jj-incoming

** Summary changed:

- Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 
(Wayland session)
+ Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

** Description changed:

  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.
  
  syslog has the following:
  
  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  
  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)
+ 
+ A similar behavior can also be observed in gedit, nautilus and other
+ GNOME applications whether they are confined or not (while snapped ones
+ seems to underline the issue more)

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

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

  A similar behavior can also be observed in gedit, nautilus and other
  GNOME applications whether they are confined or not (while snapped
  ones seems to underline the issue more)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/418662

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread Nick Rosbrook

** Tags added: rls-jj-incoming

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1803586] Re: SeaHorse hangs Panel when trying to decrypt file

Can you reproduce this issue in Ubuntu MATE 22.04?

** Changed in: mate-panel (Ubuntu)
   Status: New => Incomplete

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

Title:
  SeaHorse hangs Panel when trying to decrypt file

Status in mate-panel package in Ubuntu:
  Incomplete
Status in seahorse package in Ubuntu:
  New

Bug description:
  Hello ,

  Let's say that we have a file that we need to encrypt , so you go
  ahead and click Encrypt and then SeaHorse will ask you to choose which
  PGP to use , if you don't have one then you will be prompted to make
  one , let's say that we have made the PGP key and we encrypted the key
  but we didn't save the passphrase in the password manager so you will
  be prompted to put the password so you can decrypt the file and see
  the content

  But when you get prompted to put the passphrase to decrypt, then you
  decide not to put the passphrase but to cancel the process, you will
  be prompted second time to put the password automatically , I cancel
  it again and then the PC works just fine , but the whole menu is stuck
  , I can't click on Applications/Places/System , but I am able to click
  on the icons in the panel

  But it's frozen , I need to logout and login again to be able to use
  the panel again

  UPDATE : Even if not cancelling , putting the passphrase and unlocking
  the encryption will result in having the unencrypted file but still
  the panel freezes, And a logout/restart is needed to get it back
  working.

  If I'm missing any information please tell me I would update

  Thanks.

  Ubuntu Mate 18.04.1 LTS
  4.15.0-39-generic
  Traditional Panel
  Marco as Window Manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1803586/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-04-06 Thread Jack Howarth

Matthew, do you see the same corruption if you boot the same machine
with the Logitech C270 camera under a Fedora 36 Beta live image? It
would be interesting to know if their Fedora cheese 41.1 package doesn't
show the same artifact like it doesn't on my hardware.

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in cheese package in Ubuntu:
  In Progress
Status in cheese source package in Jammy:
  In Progress

Bug description:
  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line,
  cheese produces repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


-- 
Mailing list:

[Desktop-packages] [Bug 1968046] Re: No printer found after libreoffice version snap update

** Tags added: snap

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

Title:
  No printer found after libreoffice version snap update

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After the last update of the LibreOffice snap (ver. 7.3.2.2), LibreOffice 
can't find any printer in my system and I can't print. 
  Other applications continue to print correctly in my network installed 
printer.

  I'm attaching a screenshot where you can see the LibreOffice interface
  where no printer can be find and my system printer

  -Ubuntu release.
  Ubuntu 20.04.4 LTS

  -Updated LibreOffice.
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968046/+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 1968046] [NEW] No printer found after libreoffice version snap update

2022-04-06 Thread Hernan

Public bug reported:

After the last update of the LibreOffice snap (ver. 7.3.2.2), LibreOffice can't 
find any printer in my system and I can't print. 
Other applications continue to print correctly in my network installed printer.

I'm attaching a screenshot where you can see the LibreOffice interface
where no printer can be find and my system printer

-Ubuntu release.
Ubuntu 20.04.4 LTS

-Updated LibreOffice.
Version: 7.3.2.2 / LibreOffice Community
Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: it-IT (en_US.UTF-8); UI: en-US
Calc: threaded

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


** Tags: printing

** Attachment added: "screenshot no printer found"
   
https://bugs.launchpad.net/bugs/1968046/+attachment/5577652/+files/2022-04-06_15-42.png

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

Title:
  No printer found after libreoffice version snap update

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After the last update of the LibreOffice snap (ver. 7.3.2.2), LibreOffice 
can't find any printer in my system and I can't print. 
  Other applications continue to print correctly in my network installed 
printer.

  I'm attaching a screenshot where you can see the LibreOffice interface
  where no printer can be find and my system printer

  -Ubuntu release.
  Ubuntu 20.04.4 LTS

  -Updated LibreOffice.
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968046/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread qwach

Ok, got it. Thanks for the really quick response!

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)

This bug was fixed in the package zsys - 0.5.9

---
zsys (0.5.9) jammy; urgency=medium

  [ Gabriel Nagy ]
  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Take patched libzfs binding compatible with zfs 2.1 (LP: #1967585)

 -- Didier Roche   Wed, 06 Apr 2022 10:44:54 +0200

** Changed in: zsys (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Failed to start ZSYS daemon service (panic: runtime error)

Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 0.5.8 to 0.5.8build2 this bug started appearing.

  Previously I was facing bug 1966818

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zsys 0.5.8build2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 02:04:01 2022
  InstallationDate: Installed on 2022-02-23 (37 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  Mounts: Error: [Errno 40] Zu viele Ebenen aus symbolischen Links: 
'/proc/mounts'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro nvidia-drm.modeset=1 
pci=realloc,assign-busses,hpbussize=0x33
  RelatedPackageVersions:
   zfs-initramfs  2.1.2-1ubuntu3
   zfsutils-linux 2.1.2-1ubuntu3
  SourcePackage: zsys
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  ZFSImportedPools:
   NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
   bpool  1.88G  1.08G   816M- -10%57%  1.00xONLINE 
 -
   qpool  7.27T  1.08M  7.27T- - 0% 0%  1.00xONLINE 
 -
   rpool  1.84T   315G  1.54T- - 4%16%  1.00xONLINE 
 -
  ZFSListcache-bpool:
   bpool/boot   off on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT   noneoff on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT/ubuntu_m9rbzq /boot   on  on  on  off on  
off on  off -   none-   -   -   -   -   
-   -   -
  ZFSListcache-qpool: qpool /qpool  on  on  on  on  on  
off on  off qpool   file:///run/keystore/rpool/system.key   -   
-   -   -   -   -   -   -
  ZSYSDump: Error: command ['zsysctl', 'service', 'dump'] failed with exit code 
1: level=error msg="couldn't connect to zsys daemon: connection error: desc = 
\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection 
refused\""

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


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

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking

Attaching my journal for the current boot, where I have observed the
issue a few times already.

I'm seeing some critical error messages for gnome-session-binary and one
segfault, unsure whether this is related to the problem though.

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968040/+attachment/5577651/+files/journal.log

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

Title:
  Blanked screen doesn't wake up after locking

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

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


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

[Desktop-packages] [Bug 1968040] [NEW] Blanked screen doesn't wake up after locking

Public bug reported:

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

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

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

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

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

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

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


** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session

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

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

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

Title:
  Blanked screen doesn't wake up after locking

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

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


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

[Desktop-packages] [Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)

Done: bug #1968040.

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

Title:
  Login screen sometimes unresponsive to mouse clicks (after waking from
  sleep)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is sometimes unresponsive to mouse clicks (after
  waking from sleep).

  I can generally get it working again either by hitting Tab, or by
  switching VTs.

  Seems to happen with either Wayland or Xorg greeters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 14:07:16 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+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 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)

I read again the description and it says the login screen is
unresponsive, not that the screen doesn't wake up. Additionally the tab
key doesn't work to wake the screen for me, only Ctrl+Alt+F1. So it is a
different bug after all. I'll file a new one.

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

Title:
  Login screen sometimes unresponsive to mouse clicks (after waking from
  sleep)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is sometimes unresponsive to mouse clicks (after
  waking from sleep).

  I can generally get it working again either by hitting Tab, or by
  switching VTs.

  Seems to happen with either Wayland or Xorg greeters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 14:07:16 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+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 1875202] Re: When Firefox titlebar is turned off windows controls are impacted.

The configuration option described no longer seems to be available. That
said, since Ubuntu MATE 22.04 the Ambiant/Radiant themes are no longer
supported and not installed by default.

** No longer affects: ubuntu-mate

** Also affects: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: marco (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Incomplete

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

Title:
  When Firefox titlebar is turned off windows controls are impacted.

Status in firefox package in Ubuntu:
  Incomplete
Status in marco package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Incomplete

Bug description:
  When you go to Firefox --> Customize --> Uncheck Titlebar, the window
  controls in the upper left are cutoff and impacted by this change. In
  addition to the windows control any video played in the browser
  present some tearing due to the change in the pixel height.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875202/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

udev is built by src:systemd

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1966178] Re: Screen-privacy couldn't work

2022-04-06 Thread Treviño

> Marco, do we have a way to hide the UI if the kernel support is
missing?

Ah, I missed the question... Indeed if the feature is not supported,
there's no UI visible.

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

Title:
  Screen-privacy couldn't work

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

Bug description:
  On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c
  couldn't control it.

  From the GUI, I click 'Restrict Viewing Angle' on and off, there are
  no change at screen.

  From Fn+D, it could let screen change, and the GUI could follow the
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966178/+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 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

** Changed in: marco (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

Status in marco package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu 
boots normally to the display manager (login screen) as expected. But once I 
log in, everything on the screen is cut up into horizontal slices, with each 
slice offset farther right than the slice above, and squares of random colors 
running diagonally across the screen. I've attached a picture of my monitor 
showing the issue for reference.
  My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 
3 2200G APU, and using that APU's integrated graphics.
  In terms of software I'm running Ubuntu 20.04, which I just upgraded to and 
did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems 
fixed in the new kernel. I don't believe they're related but I figure it's 
worth mentioning.
  I tried adding the nomodeset kernel option at boot, and it's an effective 
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if 
this was caused by some quirk of my particular software setup, and successfully 
reproduced the bug, proving it wasn't.
  If you'd like me to, I can provide log files, system information, etc. or 
help narrow it down by testing workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun  8 06:41:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
  InstallationDate: Installed on 2019-10-20 (231 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+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 1947210] Re: Firefox Snap can't copy&paste or drag&drop in Wayland

2022-04-06 Thread Kevin Keijzer

Copy/paste works for me, but drag/drop does not. I can't even rearrange
tabs or bookmarks.

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

Title:
  Firefox Snap can't copy&paste or drag&drop in Wayland

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

Bug description:
  I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via
  snap. I could not copy and paste to and from the browser. I logged out
  of Wayland and into Xorg and copy & paste works.

  Already reported at
  https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known
  issue.

  I wanted to report it here so it gets into the Impish release notes or
  wherever along with the workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1947210/+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 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

I am seeing this happen about 1 in 5 times the desktop session is
initialised. I don't think this is an issue with the Metacity theme
since it does work, most of the time.

Looks like it might be related to the Marco issue:

 - https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1943289

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Invalid

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1967507/+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 1897988] Re: GitKraken Flatpak doesn't display Icon in task switcher

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

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

Title:
  GitKraken Flatpak doesn't display Icon in task switcher

Status in Ubuntu MATE:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  Fix Released
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  The GitKraken or any other flatpak doesn't display the icon on top of
  the window in the task switcher like other applications. I have
  attached a screenshot. It's the same for the bottom task bar too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phillipsj   1317 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 20:33:37 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint 
sensor
   Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 1199:9079 Sierra Wireless, Inc. Sierra Wireless 
EM7455 Qualcomm Snapdragon X7 LTE-A
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20F6006FUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5a1e3d3b-2e79-426e-9641-1447dcd64341 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6006FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F6006FUS:pvrThinkPadX260:rvnLENOVO:rn20F6006FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6006FUS
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1897988/+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 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

Typical! I've just seen this issue on an installed system using Intel
integrated graphics.

This might be a race condition with Marco, the window manager, and the
settings daemon because it didn't happen on a session restart.

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

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

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1967507/+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 1947210] Re: Firefox Snap can't copy&paste or drag&drop in Wayland

2022-04-06 Thread Thomas M Steenholdt

Still a problem here. I'm on 22.04 with all updates (including proposed)
installed, latest firefox snap (99.0-2, rev 1188).

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

Title:
  Firefox Snap can't copy&paste or drag&drop in Wayland

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

Bug description:
  I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via
  snap. I could not copy and paste to and from the browser. I logged out
  of Wayland and into Xorg and copy & paste works.

  Already reported at
  https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known
  issue.

  I wanted to report it here so it gets into the Impish release notes or
  wherever along with the workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1947210/+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 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

Ubuntu MATE 22.04 onwards use the Metacity theme from upstream Yaru,
which I maintain.

I have tried reproducing this issue and can only do so in one scenario:

 - In the Live Session while using the nouveau driver for NVIDIA GPUs.

@Simon Morgan: Please provide more details about your iGPU/dGPU and
drivers.

## Work around

 - Press Alt+F2
 - Run: marco --replace

Or, use MATE Tweak to set the DPI to HiDPI.

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Invalid

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in marco package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1967507/+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 1967507] Re: Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

** Summary changed:

- Yaru mate artwork broken HiDPI support
+ Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI displays

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Yaru Metacity theme has incorrectly scaled windows buttons on HiDPI
  displays

Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
   HiDPI scaling is broken in Mate 1.26 produced unscaled/corrputed
  Windows buttons

  Steps to reproduce:

  Mate Tweak > Windows > HiDPI change from "auto" to "HiDPI"
  Result: A lot of flickering then everything looks fine at 200%
  Reboot & login: Window title buttons are all of a sudden unscaled again while 
the rest is as expected (see image)
  Default wallpaper is grainy at 200% // No workaround

  Workaround 1: Mate Tweak > Windows > HiDPI change from "HiDPI" to "auto" and 
back to "HiDPI"
  Workaround 2:  Change theme from Yaru Light to something else and back to 
Yaru light

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1967507/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-04-06 Thread Umair Iqbal

I still see this issue even after the suggested change

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been 
called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:260: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been 
called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:260: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

in my docker file I have 
RUN echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' 
>> /etc/apt/sources.list && \
apt-get update -q -y && \
apt-get install -y --fix-missing --no-install-recommends \
libx11-6 && \
apt-get purge -y pm-utils xscreensaver* && \
apt-get autoremove -y && \
apt-get clean -y && \
rm -rf /var/lib/apt/lists/*

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LX

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread qwach

I made a new report in the proper place (i.e. udev package):
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1968036. It's a
really easy backport so I hope it's through soon.

Edit: Didn't see your message beforehand, sorry. Anyway the file is part
of the udev package per dpkg-query, so if at all it should be reassigned
to that, and the second issue I just created closed.

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Well, I can reassign to see if the maintainer of systemd/udev could
backport the patch for this.

** Package changed: xf86-input-wacom (Ubuntu) => systemd (Ubuntu)

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1267360] Re: Can not be installed because of unresolved dependencies

14.04 is EOL long ago

** Changed in: xserver-xorg-video-qxl (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Can not be installed because of unresolved dependencies

Status in oVirt:
  New
Status in spice-vdi:
  New
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid

Bug description:
  I can't install it because of unresolved dependencies.

  Output from terminal:

  sudo apt-get install xserver-xorg-video-qxl
  [sudo] password for amr: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   xserver-xorg-video-qxl : Depends: xorg-video-abi-11
Depends: xserver-xorg-core (>= 2:1.10.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-qxl (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,move,place,gnomecompat,imgpng,compiztoolbox,regex,snap,resize,grid,session,mousepoll,animation,expo,fade,workarounds,scale,unityshell,scaleaddon]
  CompositorRunning: compiz
  Date: Thu Jan  9 09:20:57 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=4be19319-aab7-4fcb-8c9d-f9b7b12d9e73 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.7.12-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ovirt/+bug/1267360/+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 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."

this is caused by a build issue, it doesn't detect qxl_drm.h which then
means the driver doesn't have support for KMS

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [qxl] Xorg fails to start with "Screen(s) found, but none have a
  usable configuration."

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Jammy 20220405

  It fails to boot to the live session in virt-manager and gnome-boxes.
  ubiquity-dm starts fine but the live session does. The graphical session 
keeps dying. 

  If I switch from QXL to Virtio then it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-06 Thread qwach

I ran into the same issue. It's a misconfiguration in the systemd/udev
hardware database (bug: https://github.com/systemd/systemd/issues/17953)
that has been fixed upstream
(https://github.com/systemd/systemd/commit/2d8840eb6632a43956b73a1042e8b8244623494a)
by just removing the entry and deferring to libwacom.

Unfortunately the first systemd release after that (250) is one above
even the version in 22.04 (249) and, simple as it is, it seems the fix
has not been backported yet, so I guess you'd have to change the file
yourself and do it again each time the package is updated, which is my
approach right now and does work.

@tjaalton can you do something about it?

** Bug watch added: github.com/systemd/systemd/issues #17953
   https://github.com/systemd/systemd/issues/17953

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in xf86-input-wacom package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1926860/+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 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)

I'm seeing the same symptoms as Corrado (comment #4). After I lock my
screen and let it blank, moving the mouse or pressing any key on the
keyboard won't wake it up. The only reliable workaround I've found is to
press Ctrl+Alt+F1.

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

Daniel, I can file a separate bug if you think it deserves one, but it
has enough similarities with the description that I thought I'd first
comment here. I'm also happy to help debugging the problem and/or test
potential fixes.

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

Title:
  Login screen sometimes unresponsive to mouse clicks (after waking from
  sleep)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is sometimes unresponsive to mouse clicks (after
  waking from sleep).

  I can generally get it working again either by hitting Tab, or by
  switching VTs.

  Seems to happen with either Wayland or Xorg greeters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 14:07:16 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+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 1958019]

2022-04-06 Thread cam

The issue appears to be that the Nvidia kernel module is failing to
build and therefore you do not have working Nvidia support with this
kernel. I'm not sure how you configured your kernel so I suspect you
have one OR both of the following issues:

1. Nvidia's drivers do not yet support 5.18-rc1. Either Nvidia hasn't
added support yet or your distribution's drivers are a little behind.
Given that this is an rc1, it could be Nvidia that's behind.

2. Something in your kernel config is incompatible with the Nvidia
drivers.

I strongly suspect it's #1 as others are having the same problem.

try:
lsmod | grep nvidia

You likely won't see anything.

At this point, it depends what's more important to you... Gaming or
sound. You can revert to an older kernel or remove the Nvidia drivers
for now. Eventually, newer kernels will be supported. In my experience,
Nvidia usually isn't too far behind the curve on newer kernel support.

On a related note, brightness control with Nvidia in discrete mode has
never worked for me on my Lenovo Legion 7i 16ITHg6.

(In reply to Darin Miller from comment #594)
> Currently the 5.18-rc1 kernel throws an error when attempting install 510
> drivers:
> 
>dpkg: error processing package nvidia-driver-510 (--configure):
>  dependency problems - leaving unconfigured
> 
> Subsequently, laptop refuses to boot discrete graphics when prime-select =
> nvidia.  However, on-demand "works" (but no perf tests to support). 
> 
> Regardless, brightness control have always worked in on-demand or "intel"
> (built-in vega) graphics mode. 
> 
> As soon as I can fully install the 510 driver, I will check brightness
> controls and report back. (We need another thread for this discussion other
> this bug report... any suggestions?)

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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

[Desktop-packages] [Bug 1968026] [NEW] right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo does work. All works with a PS2 keyboard

2022-04-06 Thread Peter Burnett

Public bug reported:

Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), 
('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
  does work. All works with a PS2 keyboard

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Left-Alt always works.
  This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
  r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 09:45:00 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968026/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-04-06 Thread Stefan Fleischmann

How can this be sitting around here for 3 years unassigned with *high*
priority? And then apparently it's not even considered a blocker for
replacing Firefox in Ubuntu 22.04 with the snap. Is it really that hard
to fix or is just nobody paying attention to it?

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

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

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in firefox package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776800/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2022-04-06 Thread James Henstridge

> Is there any option to do this via portals - ie can evince use
> org.freedesktop.portal.OpenURI to open the URI? Would then this
> allow to avoid going via xdg-open?

Evince is using g_app_info_launch_default_for_uri(), which can use the
portal interface:

https://gitlab.gnome.org/GNOME/evince/-/blob/main/shell/ev-
window.c#L6775-6778

However, it only does this as a fallback if no desktop file supports the
URI. This is intended to allow a confined app to handle some file types
within the sandbox before falling back to portals for everything else.

In the case of Evince running on the host system and seeing all the
desktop files in /usr/share/applications and other locations, it likely
won't ever call the portal API.

It'd be possible to code in explicit portal API calls, but it isn't
something that Evince packaged as a flatpak or snap would need. So it
might end up as a distro patch we'd be on the hook to maintain forever.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in evince package in Debian:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1961558] Re: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish

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

** This bug has been marked a duplicate of bug 1958267
   "Connection failed" for WPA Enterprise network eduroam

-- 
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 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-04-06 Thread Jack Howarth

It is very odd that Fedora 36 beta also uses a build of cheese 41.1 with
minimal patching and the apparently the same optimizations yet it
doesn't exhibit this artifact.

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in cheese package in Ubuntu:
  In Progress
Status in cheese source package in Jammy:
  In Progress

Bug description:
  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line,
  cheese produces repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)

I bisected mutter and gnome-shell until I identified the revision in
mutter that caused the regression:
https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.

More specifically, the changes to src/core/events.c. Indeed I rebuilt
mutter in jammy with the following patch, and the issue with the firefox
snap was gone:

--- a/src/core/events.c
+++ b/src/core/events.c
@@ -523,10 +523,6 @@ meta_display_handle_event (MetaDisplay
 #ifdef HAVE_WAYLAND
   if (wayland_compositor && !bypass_wayland)
 {
-  if (window && event->type == CLUTTER_MOTION &&
-  event->any.time != CLUTTER_CURRENT_TIME)
-meta_window_check_alive_on_event (window, event->any.time);
-
   if (meta_wayland_compositor_handle_event (wayland_compositor, event))
 bypass_clutter = TRUE;
 }

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

Title:
  Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell
  42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+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 1943768] Re: gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale

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

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  gsd defaults to wrong keymap for Sinhala (Sri Lanka) locale

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in localechooser package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Committed

Bug description:
  Per https://lists.ubuntu.com/archives/ubuntu-
  devel/2021-September/041616.html, Sri Lanka has a national keyboard
  standard, wijesekera, which is implemented by ibus-m17n but which is
  not being used by default.  We should add si_LK to the list of locales
  for which we use m17n.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1943768/+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 1956603] Re: > Internal error: Could not resolve keysym ...

2022-04-06 Thread madigal

M bad, it is 1.7.5-1 version indeed, but post #26 above is not editable
: yellow icon seems inactive.

-- 
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:
  > 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 installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Intel Corporati

[Desktop-packages] [Bug 1956603] Re: > Internal error: Could not resolve keysym ...

2022-04-06 Thread madigal

Just got 1.75-1 version from jammy-proposed. After a reboot, all the
previous errors reported above are now gone.

Thanks for the upload; this is fixed for me.

-- 
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:
  > 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 installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built

[Desktop-packages] [Bug 1968007] [NEW] $HOME/.local/bin not added to PATH env variable

2022-04-06 Thread DK

Public bug reported:

Although the path $HOME/.local/bin exists, it is not added to the path
environment variable in Ubuntu 22.04. Re-logging or rebooting does not
fix the problem.

Manually running
if [ -d "$HOME/.local/bin" ] ; then
PATH="$HOME/.local/bin:$PATH"
fi
works as expected. The aboth lines ARE included in the .profile script.

I know that there were already some issued with the mentioned path in
previous versions of Ubuntu, however, until now installing some program
with pip install --user and re-logging always fixed the issue.

I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but I
don't think this is of any relevance.

Output of ubuntu-bug bash:

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  6 10:11:13 2022
Dependencies:
 base-files 12ubuntu3
 bash-completion 1:2.11-5ubuntu1
 debianutils 5.5-1ubuntu2
 gcc-12-base 12-20220319-1ubuntu1
 libc6 2.35-0ubuntu3
 libcrypt1 1:4.4.27-1
 libgcc-s1 12-20220319-1ubuntu1
 libidn2-0 2.3.2-2build1
 libtinfo6 6.3-2
 libunistring2 1.0-1
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-30 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
Package: bash 5.1-6ubuntu1
PackageArchitecture: amd64
ProcCpuinfoMinimal:
 processor  : 3
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 158
 model name : Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
 stepping   : 10
 cpu MHz: 2904.002
 cache size : 12288 KB
 physical id: 0
 siblings   : 4
 core id: 3
 cpu cores  : 4
 apicid : 3
 initial apicid : 3
 fpu: yes
 fpu_exception  : yes
 cpuid level: 22
 wp : yes
 flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 
cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor 
lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase avx2 invpcid rdseed 
clflushopt md_clear flush_l1d
 bugs   : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds
 bogomips   : 5808.00
 clflush size   : 64
 cache_alignment: 64
 address sizes  : 39 bits physical, 48 bits virtual
 power management:
ProcEnviron:
 LC_TIME=de_DE.UTF-8
 LD_LIBRARY_PATH=
 LC_MONETARY=de_DE.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LC_ADDRESS=de_DE.UTF-8
 LANG=en_US.UTF-8
 LC_TELEPHONE=de_DE.UTF-8
 SHELL=/usr/bin/zsh
 LC_NAME=de_DE.UTF-8
 LC_MEASUREMENT=de_DE.UTF-8
 LC_IDENTIFICATION=de_DE.UTF-8
 LC_NUMERIC=de_DE.UTF-8
 LC_PAPER=de_DE.UTF-8
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
SourcePackage: bash
Tags:  wayland-session jammy
Uname: Linux 5.15.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True

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


** Tags: jammy

** Tags added: jammy

** Package changed: cheese (Ubuntu) => bash (Ubuntu)

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

Title:
  $HOME/.local/bin not added to PATH env variable

Status in bash package in Ubuntu:
  New

Bug description:
  Although the path $HOME/.local/bin exists, it is not added to the path
  environment variable in Ubuntu 22.04. Re-logging or rebooting does not
  fix the problem.

  Manually running
  if [ -d "$HOME/.local/bin" ] ; then
  PATH="$HOME/.local/bin:$PATH"
  fi
  works as expected. The aboth lines ARE included in the .profile script.

  I know that there were already some issued with the mentioned path in
  previous versions of Ubuntu, however, until now installing some
  program with pip install --user and re-logging always fixed the issue.

  I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but
  I don't think this is of any relevance.

  Output of ubuntu-bug bash:

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 10:11:13 2022
  Dependencies:
   base-files 12ubuntu3
   bash-completion 1:2.11-5ubuntu1
   debianutils 5.5-1ubuntu2
   gcc-12-base 12-20220319-1ubuntu1
   libc6 2.35-0ubuntu3
   libcrypt1 1:4.4.27-1
   libgcc-s1 12-20220319-1ubuntu1
   libidn2-0 2.3.2-2build1
   libtinfo6 6.3-2
   libunistring2 1.0-1
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Package: bash 5.1-6ubuntu1
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model

[Desktop-packages] [Bug 1968004] Re: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail

2022-04-06 Thread Thomas Bechtold

recreating the account worked (after the login.ubuntu.com page, I got
redirected to the accounts.google.com page to allow thunderbird to
access mail & calendar, that was not happening with my existing account
after the package update)

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

Title:
  Thunderbird opens new window (login.ubuntu.com for me) when trying to
  open any mail

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Since the latest update:

  Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 
1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 
(1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1)
  End-Date: 2022-04-05  06:36:02

  Thunderbird opens a new window (title is "Enter credentials for 
thomas.becht...@canonical.com on imap.gmail.com", url is 
https://login.ubuntu.com) when I select any new message in thunderbird.
  Even if I do login, nothing happens and the page reopens when I select 
another message.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:91.8.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BuildID: 20220401203107
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 10:05:04 2022
  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/thunderbird/omni.ja:greprefs.js:359
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-21 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  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/thunderbird/omni.ja:greprefs.js:359
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.8.0/20220401203107 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to jammy on 2022-03-21 (15 days ago)
  dmi.bios.date: 12/23/2021
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET68W(1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD0013GE
  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.37
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET68W(1.37):bd12/23/2021:br1.37:efr1.37:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1968004/+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 1968005] [NEW] Extensions app crashes on startup

2022-04-06 Thread Vidvranjek

Public bug reported:

When trying to open the 'Extensions' app nothing happens, crashes on
startup. Ubuntu 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-prefs 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  6 10:13:39 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-21 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Extensions app crashes on startup

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When trying to open the 'Extensions' app nothing happens, crashes on
  startup. Ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 10:13:39 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-21 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968005/+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 1968004] [NEW] Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail

2022-04-06 Thread Thomas Bechtold

Public bug reported:

Since the latest update:

Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 
1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 
(1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1)
End-Date: 2022-04-05  06:36:02

Thunderbird opens a new window (title is "Enter credentials for 
thomas.becht...@canonical.com on imap.gmail.com", url is 
https://login.ubuntu.com) when I select any new message in thunderbird.
Even if I do login, nothing happens and the page reopens when I select another 
message.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:91.8.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
BuildID: 20220401203107
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  6 10:05:04 2022
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/thunderbird/omni.ja:greprefs.js:359
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2022-03-21 (15 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
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/thunderbird/omni.ja:greprefs.js:359
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=91.8.0/20220401203107 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to jammy on 2022-03-21 (15 days ago)
dmi.bios.date: 12/23/2021
dmi.bios.release: 1.37
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET68W(1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD0013GE
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.37
dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET68W(1.37):bd12/23/2021:br1.37:efr1.37:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD0013GE
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO

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


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

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

Title:
  Thunderbird opens new window (login.ubuntu.com for me) when trying to
  open any mail

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Since the latest update:

  Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 
1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 
(1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1)
  End-Date: 2022-04-05  06:36:02

  Thunderbird opens a new window (title is "Enter credentials for 
thomas.becht...@canonical.com on imap.gmail.com", url is 
https://login.ubuntu.com) when I select any new message in thunderbird.
  Even if I do login, nothing happens and the page reopens when I select 
another message.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:91.8.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BuildID: 20220401203107
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 10:05:04 2022
  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/thunderbird/omni.ja:greprefs.js:359
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Inst

desktop-packages@lists.launchpad.net

2022-04-06 Thread Chris Guiver

I'll mark this incomplete then  (assumption I jumped the gun)

Thanks @Rick Tzschichholz/ricotz

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

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

Title:
  libreoffice help isn't opening - "Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex&Language=en-
  US&System=UNIX&Version=7.3."

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu jammy live test on
  - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000)

  ISOs builds have been failing, so this is an older ISO with upgrades
  applied. Purpose was exploration of an libreoffice update to fix
  confinement issue
  (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210)

  Libreoffice package

  lubuntu@lubuntu:~$   apt-cache policy libreoffice
  libreoffice:
    Installed: 1:7.3.2-0ubuntu1
    Candidate: 1:7.3.2-0ubuntu1
    Version table:
   *** 1:7.3.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ** to re-create

  To re-create, open libreoffice & hit F1 or use menu to open
  Help->Libreoffice.Help

  ** Expected outcome

  Firefox opens & help page is shown in windows

  ** Actual outcome

  Firefox opens, but error instead

  ---
  File not found

  Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex&Language=en-
  US&System=UNIX&Version=7.3.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: LXQt
  Date: Wed Apr  6 01:46:35 2022
  LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+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 1967963] Re: Firefox snap cannot be set as default browser

The report suggests the desktop environment used is KDE. Under GNOME the
settings correctly list firefox as a choice

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

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

Title:
  Firefox snap cannot be set as default browser

Status in firefox package in Ubuntu:
  New

Bug description:
  I was unable to set Firefox as the default browser by going to
  Settings -> Applications -> Default Applications -> Web browser. It
  was set to Other... and web links opened in Kate.

  In addition, I was unable to report a bug against Firefox because "it
  is provided by a snap provided by Mozilla."

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:54:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20L50067US
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L50067US
  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.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L50067US
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967963/+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 1967999] Re: Cound not scroll in 'Show applications' when resolution is changed to 800x600

Thank you for your bug report, could you try on the current Ubuntu serie if 
that's still an issue there? 
Could you add your journalctl log after getting the issue?
How do you scroll? Can you switch pages by clicking on the dots at the bottom 
of the screen?

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

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

Title:
  Cound not scroll in 'Show applications' when resolution is changed to
  800x600

Status in OEM Priority Project:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1.Install Ubuntu
  2.Go to Setting->display to change the resolution to 800x600
  3. Click show applications and go click all

  Expected result:
  The page should be scroll up and down

  Actual result:
  It cannot scroll

  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967999/+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 1967826] Re: Search entry border is jagged and clipped (when using Yaru theme)

** Changed in: yaru
   Status: Unknown => Fix Released

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

Title:
  Search entry border is jagged and clipped (when using Yaru theme)

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Search entry border is jagged and clipped (when using Yaru theme). I
  use scale 200%.

  This doesn't seem to be a problem in the default GNOME theme though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1967826/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

This still requires a snapd 2.55.3 release. See
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/comments/14

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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@lists.launchpad.net

This still requires a snapd 2.55.3 release. See
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/comments/14

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

Title:
  libreoffice help isn't opening - "Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex&Language=en-
  US&System=UNIX&Version=7.3."

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Lubuntu jammy live test on
  - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000)

  ISOs builds have been failing, so this is an older ISO with upgrades
  applied. Purpose was exploration of an libreoffice update to fix
  confinement issue
  (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210)

  Libreoffice package

  lubuntu@lubuntu:~$   apt-cache policy libreoffice
  libreoffice:
    Installed: 1:7.3.2-0ubuntu1
    Candidate: 1:7.3.2-0ubuntu1
    Version table:
   *** 1:7.3.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ** to re-create

  To re-create, open libreoffice & hit F1 or use menu to open
  Help->Libreoffice.Help

  ** Expected outcome

  Firefox opens & help page is shown in windows

  ** Actual outcome

  Firefox opens, but error instead

  ---
  File not found

  Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex&Language=en-
  US&System=UNIX&Version=7.3.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: LXQt
  Date: Wed Apr  6 01:46:35 2022
  LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+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 1967999] Re: Cound not scroll in 'Show applications' when resolution is changed to 800x600

2022-04-06 Thread Bin Li

When I removed gnome-shell-extension-ubuntu-dock, the original gnome-
shell works fine.

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

Title:
  Cound not scroll in 'Show applications' when resolution is changed to
  800x600

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

Bug description:
  Steps to reproduce:
  1.Install Ubuntu
  2.Go to Setting->display to change the resolution to 800x600
  3. Click show applications and go click all

  Expected result:
  The page should be scroll up and down

  Actual result:
  It cannot scroll

  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967999/+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 1967999] [NEW] Cound not scroll in 'Show applications' when resolution is changed to 800x600

2022-04-06 Thread Bin Li

Public bug reported:

Steps to reproduce:
1.Install Ubuntu
2.Go to Setting->display to change the resolution to 800x600
3. Click show applications and go click all

Expected result:
The page should be scroll up and down

Actual result:
It cannot scroll

gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-1966028 sutton

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

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

Title:
  Cound not scroll in 'Show applications' when resolution is changed to
  800x600

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

Bug description:
  Steps to reproduce:
  1.Install Ubuntu
  2.Go to Setting->display to change the resolution to 800x600
  3. Click show applications and go click all

  Expected result:
  The page should be scroll up and down

  Actual result:
  It cannot scroll

  gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967999/+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