[Desktop-packages] [Bug 1950912]

[Gordon Lack]

The **NOT** part was feedback on my comment 4:

> I'll wait to see whether 91.3.2+ also fixes the drop-down menus.

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

Title:
  [upstream] Drop-down Calendar menus unreadable in Thunderbird

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

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

[Desktop-packages] [Bug 1950912]

[Wls220spring]

(In reply to Gordon Lack from comment #11)
> Indeed, I've just downloaded 91.3.2 from thunderbird.net, dropped it in place 
> as `/usr/lib/thunderbird` and copied across Ubuntu's `thunderbird.sh` 
> start-up script.
> 
> The problems with drop-down menus are *still present*.
> So 91.3.2 *does* **NOT** fix the issue.

Nobody said it was fixed. Bug 1741095 is about something entirely unrelated.
This bug won't be fixed until assigned to someone, a patch is applied, a new 
version is built, and the report is resolved as fixed.

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

Title:
  [upstream] Drop-down Calendar menus unreadable in Thunderbird

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

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

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

[bluppfisk]

I'm sure the discussion has been held elsewhere, and there's been made a
case against sandboxing them or handling their crashes, as lack of
freedom would defeat the very purpose of these extensions?

At any rate I'm happy to have reached a solution. 3 monitor unplugs
without crashes convinces me that that was the problem. Many thanks for
your intervention!

I don't miss the Dock very much but it'd be interesting to see where it
has been patched and when to expect it in a release. Is there any info
on that? On the bug you shared, it only says "fix committed" but I am
too dumb to find out where I can see the code change.

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

Title:
  Disconnecting monitor crashes shell (wayland, gnome)

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

  Dmesg doesn't seem to contain anything useful.

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

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


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

[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11

[Launchpad Bug Tracker]

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

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

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is too fast

[Daniel van Vugt]

I consider this bug a priority for Ubuntu 22.04 and was hoping to get to
it by the new year break. Time to at least put all the bug links in one
place...

** Summary changed:

- Touchpad scrolling is 1.5x faster on Wayland than on X11
+ Touchpad scrolling is too fast

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

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

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11

[Launchpad Bug Tracker]

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

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

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11

[Daniel van Vugt]

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1610477
   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/1922047

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


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

[Desktop-packages] [Bug 736253] Re: Screensaver does not work intermittently

[Launchpad Bug Tracker]

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

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

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

Title:
  Screensaver does not work intermittently

Status in gnome-screensaver package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-screensaver

  Occasionally, the screensaver won't kick in.  This is a very
  intermittent problem.  It is a potential security threat if you leave
  your machine expecting screensaver lockup but don't get it and expose
  sensitive content, like bank/brokerage sites and accounts.  The only
  user app running was Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13
  Uname: Linux 2.6.32-29-generic i686
  Architecture: i386
  Date: Wed Mar 16 13:01:29 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

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


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

[Desktop-packages] [Bug 1036440] Re: image viewer hangs

[Launchpad Bug Tracker]

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

** Changed in: eog (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  image viewer hangs

Status in eog package in Ubuntu:
  Expired

Bug description:
  Image Viewer hangs.  Hard disk activity light always on.  System very
  unresponsive due to image viewer hang.

  System monitor shows
  - eog 96% cpu
  - gnome-system-monitor 12% cpu
  - other processes (that I can see in 1 window without scrolling, sort on cpu 
column) at 0% cpu
  ( I thought these needed to add to 100% ???)

  To reproduce the problem:
  - download 
http://mars.jpl.nasa.gov/images/pia16051_figure_1_raw_smaller-full.jpg (52.6 MB)
  - double click on jpg file

  My system RAM is 1 GB, so should be enough.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eog 3.4.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  Date: Mon Aug 13 19:23:44 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/eog
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:2031): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed

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


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

[Desktop-packages] [Bug 1207512] Re: Closing calculator window takes a few seconds

[Launchpad Bug Tracker]

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

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

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

Title:
  Closing calculator window takes a few seconds

Status in gnome-calculator package in Ubuntu:
  Expired

Bug description:
  Clicking on the X in the upper left corner of the GUI window has no
  immediate effect.

  After a delay of a few seconds, the window finally closes.

  This is reproducible and annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-calculator 1:3.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Thu Aug  1 16:23:45 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2013-05-14 (79 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1568425] Re: gedit freezes up entire OS

[Launchpad Bug Tracker]

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

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gedit freezes up entire OS

Status in gedit package in Ubuntu:
  Expired

Bug description:
  Recently, gedit has completely frozen up Ubuntu 14.04.

  The problem is random and not reproducible.

  This has happened 2x in about 1 week.

  Most recent trigger was clicking on X to close the gedit window.  The
  previous trigger was clicking on a line for text editing.

  Only solution is to hold power button until system shuts down.  Then
  restart to continue using the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16
  Uname: Linux 3.19.0-58-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Apr  9 20:08:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-29 (711 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1809558] Re: libreoffice calc cannot parse csv

[Launchpad Bug Tracker]

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

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  libreoffice calc cannot parse csv

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  On Fri, Dec 21 2018 04:30:23 AM, calc properly parsed a csv file on
  this pc.

  It can no longer do this (see screenshot).

  Input test.csv file is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial4
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 22 16:48:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-11-14 (37 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  ProcEnviron:
   PATH=(custom, 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/ubuntu/+source/libreoffice/+bug/1809558/+subscriptions


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

[Desktop-packages] [Bug 1953547] Re: Screen lock doesn't work

[Daniel van Vugt]

I just noticed you're using Budgie. I wonder how that changes things
compared to GNOME.

** Summary changed:

- Screen lock doesn't work
+ Screen does not lock when suspended

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

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

Title:
  Screen does not lock when suspended

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

[Daniel van Vugt]

Extensions have free reign to do anything, including crash the shell.
They are the causes of lots of our bugs. The alternative would be to
disallow extensions which would be more stable but probably less
popular.

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

Title:
  Disconnecting monitor crashes shell (wayland, gnome)

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

  Dmesg doesn't seem to contain anything useful.

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

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


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

[Desktop-packages] [Bug 1953694] [NEW] wayland clipboard handing locks up in certain corner cases

[Kain]

Public bug reported:

There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy
paste from/to various apps fails based on something related to type
handling.

I've run into this on Ubuntu 21.10, with multiple apps under the ubuntu
wayland session.

I have not found a matching bug in the Debian BTS, but there is a
matching upstream bug and merged fix in upstream gtk+-3 from GNOME as of
20211206.

References:
https://gitlab.gnome.org/GNOME/gtk/-/issues/4340
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058

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

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  wayland clipboard handing locks up in certain corner cases

Status in evince package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy
  paste from/to various apps fails based on something related to type
  handling.

  I've run into this on Ubuntu 21.10, with multiple apps under the
  ubuntu wayland session.

  I have not found a matching bug in the Debian BTS, but there is a
  matching upstream bug and merged fix in upstream gtk+-3 from GNOME as
  of 20211206.

  References:
  https://gitlab.gnome.org/GNOME/gtk/-/issues/4340
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058

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


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

[Desktop-packages] [Bug 1953685] Re: [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

[Kevin Keijzer]

** Description changed:

  I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
- the update to Firefox 95, it's been verry laggy; especially noticeable
+ the update to Firefox 95, it's been very laggy; especially noticeable
  while scrolling, for instance on about:support.
  
  Strangely, the bug is less present when the browser window is smaller. A
  maximized window lags very badly, but when resizing the window to under
  ~75% of the screen, it becomes a lot better.
  
  I have tried completely clean profiles by renaming ~/snap/firefox, but
  this made no difference.
  
  I have a feeling that EGL has something to do with it. When I force the
  Firefox snap to run on Xwayland by running `WAYLAND_DISABLE=1 snap run
  firefox`, the bug is *not* present.
  
  When I run the Firefox 95 deb (from jammy) on Wayland, by running
  `MOZ_ENABLE_WAYLAND=1 firefox`, the bug is also present. (When I run the
  deb without that environment variable, it falls back to Xwayland, which
  works normally.)
  
  However, when I set gfx.x11-egl.force-enabled to true in about:config,
  it also lags.
  
  One may assume that EGL is simply broken on this chipset, but that is
  not the case. When I run the Firefox *94* deb (from focal) with
  `MOZ_ENABLE_WAYLAND=1`, it works fine. Also, when I run `snap revert
  firefox` to go back to 94.0.2-2, the bug is not present, even when
  running on Wayland, using EGL.
  
  I have tested the snap both on focal and jammy on the same hardware. The
  bug is identical in both cases.
  
- 
- tl;dr: On old Intel graphics Firefox 94 was working well with GLX and EGL, 
while EGL seems broken on Firefox 95.
+ tl;dr: On old Intel graphics Firefox 94 was working well with GLX and
+ EGL, while EGL seems broken on Firefox 95.

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

Title:
  [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
  the update to Firefox 95, it's been very laggy; especially noticeable
  while scrolling, for instance on about:support.

  Strangely, the bug is less present when the browser window is smaller.
  A maximized window lags very badly, but when resizing the window to
  under ~75% of the screen, it becomes a lot better.

  I have tried completely clean profiles by renaming ~/snap/firefox, but
  this made no difference.

  I have a feeling that EGL has something to do with it. When I force
  the Firefox snap to run on Xwayland by running `WAYLAND_DISABLE=1 snap
  run firefox`, the bug is *not* present.

  When I run the Firefox 95 deb (from jammy) on Wayland, by running
  `MOZ_ENABLE_WAYLAND=1 firefox`, the bug is also present. (When I run
  the deb without that environment variable, it falls back to Xwayland,
  which works normally.)

  However, when I set gfx.x11-egl.force-enabled to true in about:config,
  it also lags.

  One may assume that EGL is simply broken on this chipset, but that is
  not the case. When I run the Firefox *94* deb (from focal) with
  `MOZ_ENABLE_WAYLAND=1`, it works fine. Also, when I run `snap revert
  firefox` to go back to 94.0.2-2, the bug is not present, even when
  running on Wayland, using EGL.

  I have tested the snap both on focal and jammy on the same hardware.
  The bug is identical in both cases.

  tl;dr: On old Intel graphics Firefox 94 was working well with GLX and
  EGL, while EGL seems broken on Firefox 95.

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


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

[Desktop-packages] [Bug 1953685] Re: [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

[Kevin Keijzer]

I have also tested the tarball releases from
https://www.mozilla.org/firefox/

The problems are identical with those releases. I tested 94.0.2, 95.0,
96.0b2 and 97.0a1.

I ran all of them with `MOZ_ENABLE_WAYLAND=1`.

94.0.2 works perfectly fine, and all the other releases show lag while
scrolling, and the GNOME Shell / Mutter process even seems to lock up
when Firefox starts a download, prior to the "Save file" popup window.

When run on Xwayland (without the environment variable), all releases
run fine.

So "something" has changed between 94.0.2 and 95.0, breaking the Wayland
backend at least on gen4 Intel graphics. My only other devices are
Pinebook Pro's, using the Panfrost driver. I don't seem to be able to
reproduce this on there. But those are arm64 builds, so maybe not the
best comparison.

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

Title:
  [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
  the update to Firefox 95, it's been verry laggy; especially noticeable
  while scrolling, for instance on about:support.

  Strangely, the bug is less present when the browser window is smaller.
  A maximized window lags very badly, but when resizing the window to
  under ~75% of the screen, it becomes a lot better.

  I have tried completely clean profiles by renaming ~/snap/firefox, but
  this made no difference.

  I have a feeling that EGL has something to do with it. When I force
  the Firefox snap to run on Xwayland by running `WAYLAND_DISABLE=1 snap
  run firefox`, the bug is *not* present.

  When I run the Firefox 95 deb (from jammy) on Wayland, by running
  `MOZ_ENABLE_WAYLAND=1 firefox`, the bug is also present. (When I run
  the deb without that environment variable, it falls back to Xwayland,
  which works normally.)

  However, when I set gfx.x11-egl.force-enabled to true in about:config,
  it also lags.

  One may assume that EGL is simply broken on this chipset, but that is
  not the case. When I run the Firefox *94* deb (from focal) with
  `MOZ_ENABLE_WAYLAND=1`, it works fine. Also, when I run `snap revert
  firefox` to go back to 94.0.2-2, the bug is not present, even when
  running on Wayland, using EGL.

  I have tested the snap both on focal and jammy on the same hardware.
  The bug is identical in both cases.

  
  tl;dr: On old Intel graphics Firefox 94 was working well with GLX and EGL, 
while EGL seems broken on Firefox 95.

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


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

[Desktop-packages] [Bug 1940467] Re: [snap] Nitrokey FIDO2 does not work with Chromium snap

[Kevin Keijzer]

** Changed in: snapd
   Status: Fix Committed => Fix Released

** No longer affects: chromium-browser (Ubuntu)

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

Title:
  [snap] Nitrokey FIDO2 does not work with Chromium snap

Status in snapd:
  Fix Released

Bug description:
  I have a Nitrokey FIDO2, which works fine with the Firefox deb
  package. However, it does not work at all with the Chromium snap. I
  have libu2f-udev installed.

  This problem can be fixed by adding the following lines to
  /etc/udev/rules.d/70-snap.chromium.rules:

  # u2f-devices
  # Nitrokey FIDO2
  SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="20a0", 
ATTRS{idProduct}=="42b1", TAG+="snap_chromium_chromium"
  TAG=="snap_chromium_chromium", RUN+="/usr/lib/snapd/snap-device-helper 
$env{ACTION} snap_chromium_chromium $devpath $major:$minor"

  and then running sudo udevadm control --reload-rules && sudo udevadm
  trigger.

  After that, it works perfectly well.

  The Yubico YubiKey is already present with a very similar line, so
  this is merely a case of a missing rule.

  It would be very nice if support for the Nitrokey FIDO2 could be
  upstreamed.

  More background here: https://support.nitrokey.com/t/nitrokey-
  fido2-funktioniert-nicht-mit-firefox-und-chromium-unter-
  ubuntu-20-04/2651

  Also hereby the required fluff:

  kevin@vanadium:~$  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  kevin@vanadium:~$  snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 08:05 CEST
  channels:
    latest/stable:92.0.4515.159 2021-08-17 (1708) 148MB -
    latest/candidate: 92.0.4515.159 2021-08-17 (1708) 148MB -
    latest/beta:  93.0.4577.42  2021-08-13 (1699) 149MB -
    latest/edge:  94.0.4603.0   2021-08-14 (1700) 153MB -
  installed:  92.0.4515.159(1708) 148MB -

  What I expected to happen: My FIDO2 security key should work.

  What happened instead: It didn't work, due to a missing udev rule.

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


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

[Desktop-packages] [Bug 1953685] [NEW] [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

[Kevin Keijzer]

Public bug reported:

I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
the update to Firefox 95, it's been verry laggy; especially noticeable
while scrolling, for instance on about:support.

Strangely, the bug is less present when the browser window is smaller. A
maximized window lags very badly, but when resizing the window to under
~75% of the screen, it becomes a lot better.

I have tried completely clean profiles by renaming ~/snap/firefox, but
this made no difference.

I have a feeling that EGL has something to do with it. When I force the
Firefox snap to run on Xwayland by running `WAYLAND_DISABLE=1 snap run
firefox`, the bug is *not* present.

When I run the Firefox 95 deb (from jammy) on Wayland, by running
`MOZ_ENABLE_WAYLAND=1 firefox`, the bug is also present. (When I run the
deb without that environment variable, it falls back to Xwayland, which
works normally.)

However, when I set gfx.x11-egl.force-enabled to true in about:config,
it also lags.

One may assume that EGL is simply broken on this chipset, but that is
not the case. When I run the Firefox *94* deb (from focal) with
`MOZ_ENABLE_WAYLAND=1`, it works fine. Also, when I run `snap revert
firefox` to go back to 94.0.2-2, the bug is not present, even when
running on Wayland, using EGL.

I have tested the snap both on focal and jammy on the same hardware. The
bug is identical in both cases.


tl;dr: On old Intel graphics Firefox 94 was working well with GLX and EGL, 
while EGL seems broken on Firefox 95.

** Affects: firefox (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/1953685

Title:
  [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
  the update to Firefox 95, it's been verry laggy; especially noticeable
  while scrolling, for instance on about:support.

  Strangely, the bug is less present when the browser window is smaller.
  A maximized window lags very badly, but when resizing the window to
  under ~75% of the screen, it becomes a lot better.

  I have tried completely clean profiles by renaming ~/snap/firefox, but
  this made no difference.

  I have a feeling that EGL has something to do with it. When I force
  the Firefox snap to run on Xwayland by running `WAYLAND_DISABLE=1 snap
  run firefox`, the bug is *not* present.

  When I run the Firefox 95 deb (from jammy) on Wayland, by running
  `MOZ_ENABLE_WAYLAND=1 firefox`, the bug is also present. (When I run
  the deb without that environment variable, it falls back to Xwayland,
  which works normally.)

  However, when I set gfx.x11-egl.force-enabled to true in about:config,
  it also lags.

  One may assume that EGL is simply broken on this chipset, but that is
  not the case. When I run the Firefox *94* deb (from focal) with
  `MOZ_ENABLE_WAYLAND=1`, it works fine. Also, when I run `snap revert
  firefox` to go back to 94.0.2-2, the bug is not present, even when
  running on Wayland, using EGL.

  I have tested the snap both on focal and jammy on the same hardware.
  The bug is identical in both cases.

  
  tl;dr: On old Intel graphics Firefox 94 was working well with GLX and EGL, 
while EGL seems broken on Firefox 95.

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


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

[Desktop-packages] [Bug 1953678] Re: Recommended package, `fonts-droid-fallback` is missing many common glyphs making it useless as a fallback font.

[Launchpad Bug Tracker]

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

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

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

Title:
  Recommended package, `fonts-droid-fallback` is missing many common
  glyphs making it useless as a fallback font.

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  Ghostscripts dependency on fonts-droid-fallback is flawed since the
  newest version of the package is no longer suitable as a fallback font
  due to missing so many glyphs.

  Context:

  The ghostscript ubuntu package strips out the vendored file and adds a
  symlink that is compatible with the fonts-droid-fallback package.
  Likely because the font is large enough to have a convenient way of
  opting out, esp. since the font is already available via the fonts-
  droid-fallback pacakage.
  
https://git.launchpad.net/ubuntu/+source/ghostscript/tree/debian/rules?h=ubuntu/focal-
  updates#n138

  In 2014, as a way of saving space, the fallback font removed common
  glyphs
  
https://android.googlesource.com/platform/frameworks/base/+/034b20c102ee2e7ec1da09e2b080f35be4a5cf54

  At some point fonts-droid-fallback pulled in that upstream change, and
  now when you install ghostscript alongside fonts-droid-fallback, the
  fallback font is actually missing those characters.

  
  Credit to s...@benchling.com for figuring this out.

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


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

[Desktop-packages] [Bug 1953678] [NEW] Recommended package, `fonts-droid-fallback` is missing many common glyphs making it useless as a fallback font.

[Piyush Kancharlawar]

Public bug reported:

Ghostscripts dependency on fonts-droid-fallback is flawed since the
newest version of the package is no longer suitable as a fallback font
due to missing so many glyphs.

Context:

The ghostscript ubuntu package strips out the vendored file and adds a
symlink that is compatible with the fonts-droid-fallback package. Likely
because the font is large enough to have a convenient way of opting out,
esp. since the font is already available via the fonts-droid-fallback
pacakage.
https://git.launchpad.net/ubuntu/+source/ghostscript/tree/debian/rules?h=ubuntu/focal-
updates#n138

In 2014, as a way of saving space, the fallback font removed common
glyphs
https://android.googlesource.com/platform/frameworks/base/+/034b20c102ee2e7ec1da09e2b080f35be4a5cf54

At some point fonts-droid-fallback pulled in that upstream change, and
now when you install ghostscript alongside fonts-droid-fallback, the
fallback font is actually missing those characters.


Credit to s...@benchling.com for figuring this out.

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

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

Title:
  Recommended package, `fonts-droid-fallback` is missing many common
  glyphs making it useless as a fallback font.

Status in ghostscript package in Ubuntu:
  New

Bug description:
  Ghostscripts dependency on fonts-droid-fallback is flawed since the
  newest version of the package is no longer suitable as a fallback font
  due to missing so many glyphs.

  Context:

  The ghostscript ubuntu package strips out the vendored file and adds a
  symlink that is compatible with the fonts-droid-fallback package.
  Likely because the font is large enough to have a convenient way of
  opting out, esp. since the font is already available via the fonts-
  droid-fallback pacakage.
  
https://git.launchpad.net/ubuntu/+source/ghostscript/tree/debian/rules?h=ubuntu/focal-
  updates#n138

  In 2014, as a way of saving space, the fallback font removed common
  glyphs
  
https://android.googlesource.com/platform/frameworks/base/+/034b20c102ee2e7ec1da09e2b080f35be4a5cf54

  At some point fonts-droid-fallback pulled in that upstream change, and
  now when you install ghostscript alongside fonts-droid-fallback, the
  fallback font is actually missing those characters.

  
  Credit to s...@benchling.com for figuring this out.

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


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

[Desktop-packages] [Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists

[Launchpad Bug Tracker]

This bug was fixed in the package deja-dup - 37.1-2fakesync1ubuntu0.2

---
deja-dup (37.1-2fakesync1ubuntu0.2) bionic; urgency=medium

  * debian/patches/invalid_password_handling.patch:
- handle correctly when an invalid password is entered
  (lp: #918489)

 -- Sebastien Bacher   Thu, 25 Nov 2021 17:53:50
+0100

** Changed in: deja-dup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  duplicity allows a new, different passphrase if an archive cache
  exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  Fix Released
Status in duplicity source package in Trusty:
  Won't Fix
Status in deja-dup source package in Xenial:
  Fix Released
Status in duplicity source package in Xenial:
  Won't Fix
Status in deja-dup source package in Yakkety:
  Fix Released
Status in duplicity source package in Yakkety:
  Won't Fix
Status in deja-dup source package in Bionic:
  Fix Released
Status in duplicity source package in Bionic:
  Won't Fix

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

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


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

[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Kippykip]

Still appears to be here, although it works on arm64?
Basically I tested Ubuntu Server 20.04 for the RPi 400, on arm64 (64-bit) 
typing in "sudo apt install xubuntu-desktop" has a distro that works perfectly 
fine.

However on Ubuntu Server 20.04 for armhf (32-bit), doing the same "sudo apt 
install xubuntu-desktop" I get the same black screen thing you guys are talking 
about.
Makes sense as xubuntu uses lightdm by default.

Although installing slick-greeter also worked around the issue for me.

** Changed in: lightdm (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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


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

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Christian Ehrhardt ]

** Tags removed: server-triage-discuss

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions


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

[Desktop-packages] [Bug 1951738] Re: [SRU] libreoffice 7.2.3 for impish

[Rico Tzschichholz]

** Changed in: libreoffice (Ubuntu)
   Status: New => 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/1951738

Title:
   [SRU] libreoffice 7.2.3 for impish

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.2.3 is in its third bugfix release of the 7.2 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.3_release

   * Version 7.2.2 is currently released in impish. For a list of fixed bugs 
compared to 7.2.2 see the list of bugs fixed in the release candidates of 7.2.3 
(that's a total of 112 bugs):
   https://wiki.documentfoundation.org/Releases/7.2.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.2.3/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_72/1116/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211121_122557_220e4@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211121_140906_e9b32@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211121_135011_ebc4d@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211121_121636_a621c@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211121_120225_a0cce@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 112 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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


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

[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04

[Sebastien Bacher]

** Tags removed: rls-ff-incoming rls-gg-incoming

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

Title:
  Location services work with location services off, 20.04

Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-2.0 source package in Focal:
  Triaged
Status in geoclue-2.0 source package in Groovy:
  Won't Fix

Bug description:
  * Impact

  Disabling the location service in settings isn't reflection on
  traditional deb applications

  * Test case

  - Log in an Ubuntu desktop session
  - install geoclue-2-demo
  - go to gnome-control-center, privacy, location and ensure the service is 
disabled
  - $ /usr/libexec/geoclue-2.0/demos/where-am-i

  the script should return a permission error and not a location

  * Regression potential

  [racb] Users who are currently relying on a working location service
  despite having a setting disabling it will find that the location
  service will stop working because the setting will start to be
  honoured.

  The change is in the client library, try a few applications, deb and
  snap or flatpak and make sure the status is correct respected

  -

  Not sure if this is the right package, but in the privacy -> location
  settings, in 18.04 I had to have my application be approved by user to
  access location with Geoclue. Now it seems this is working without the
  location services "enabled"??

  My application is repeater-START:
  https://sourceforge.net/projects/repeater-start/

  Steps to see issue:
  1) install Repeater-START and click the locate me button circle to the left. 
It goes to your rough location on map.

  2) Go to settings, privacy, location, note that location is turned
  off!?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Aug  8 19:38:12 2020
  InstallationDate: Installed on 2017-07-29 (1106 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago)

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


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

[Desktop-packages] [Bug 1953629] Re: Failied to mount Windows share: Invalid argument

[Tony Pursell]

** Description changed:

  When trying to access my NAS using Files or to do a backup which saves
  on my NAS I get this error message.
  
- Failied to mount Windows share: Invalid argument
+ Failed to mount Windows share: Invalid argument
  
- I would expect access my NAS.
+ I would expect access to my NAS.
  
  I am using Ubuntu version 21.10
  
  Note that /etc/samba/smb.conf was updated yesterday.
  
  samba:
-   Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3
-   Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3
-   Version table:
-  *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500
- 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  2:4.13.5+dfsg-2ubuntu2 500
- 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
+   Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3
+   Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3
+   Version table:
+  *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500
+ 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  2:4.13.5+dfsg-2ubuntu2 500
+ 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  
  NOTE:
  
  Previously when I had the same problem, I added
  
  client min protocol = NT1
  
  to smb.conf but it has not cured this problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 
70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 
70-snap.chromium.rules 70-snap.easy-openvpn.rules 
70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 
70-snap.firefox.rules
  Date: Wed Dec  8 14:16:35 2021
  InstallationDate: Installed on 2015-06-21 (2362 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2014
  dmi.bios.release: 1.68
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O07KT44AUS
  dmi.board.name: Aptio CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00:
  dmi.product.family: IdeaCentre
  dmi.product.name: 90BX0018UK
  dmi.product.sku: LENOVO_PN_Lenovo E50-00
  dmi.product.version: Lenovo E50-00
  dmi.sys.vendor: LENOVO

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

Title:
  Failied to mount Windows share: Invalid argument

Status in samba package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  When trying to access my NAS using Files or to do a backup which saves
  on my NAS I get this error message.

  Failed to mount Windows share: Invalid argument

  I would expect access to my NAS.

  I am using Ubuntu version 21.10

  Note that /etc/samba/smb.conf was updated yesterday.

  samba:
    Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3
    Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3
    Version table:
   *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500
  500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu impish-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:4.13.5+dfsg-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages

  NOTE:

  Previously when I had the same problem, I added

  client min protocol = NT1

  to smb.conf but it has not cured this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 
70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 
70-snap.chromium.rules 70-snap.easy-openvpn.rules 
70-snap.gnome-system-monitor.rules 

[Desktop-packages] [Bug 1953629] [NEW] Failied to mount Windows share: Invalid argument

[Tony Pursell]

Public bug reported:

When trying to access my NAS using Files or to do a backup which saves
on my NAS I get this error message.

Failied to mount Windows share: Invalid argument

I would expect access my NAS.

I am using Ubuntu version 21.10

Note that /etc/samba/smb.conf was updated yesterday.

samba:
  Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3
  Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3
  Version table:
 *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500
500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu impish-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2:4.13.5+dfsg-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages

NOTE:

Previously when I had the same problem, I added

client min protocol = NT1

to smb.conf but it has not cured this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: udisks2 2.9.4-1
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 
70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 
70-snap.chromium.rules 70-snap.easy-openvpn.rules 
70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 
70-snap.firefox.rules
Date: Wed Dec  8 14:16:35 2021
InstallationDate: Installed on 2015-06-21 (2362 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 90BX0018UK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2014
dmi.bios.release: 1.68
dmi.bios.vendor: LENOVO
dmi.bios.version: O07KT44AUS
dmi.board.name: Aptio CRB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0F82993 WIN
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00:
dmi.product.family: IdeaCentre
dmi.product.name: 90BX0018UK
dmi.product.sku: LENOVO_PN_Lenovo E50-00
dmi.product.version: Lenovo E50-00
dmi.sys.vendor: LENOVO

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

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


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

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

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

Title:
  Failied to mount Windows share: Invalid argument

Status in samba package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  When trying to access my NAS using Files or to do a backup which saves
  on my NAS I get this error message.

  Failied to mount Windows share: Invalid argument

  I would expect access my NAS.

  I am using Ubuntu version 21.10

  Note that /etc/samba/smb.conf was updated yesterday.

  samba:
Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3
Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3
Version table:
   *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500
  500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu impish-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:4.13.5+dfsg-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages

  NOTE:

  Previously when I had the same problem, I added

  client min protocol = NT1

  to smb.conf but it has not cured this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 
70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 
70-snap.chromium.rules 70-snap.easy-openvpn.rules 
70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 
70-snap.firefox.rules
  Date: Wed Dec  8 14:16:35 2021
  InstallationDate: Installed on 2015-06-21 (2362 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: 

[Desktop-packages] [Bug 1945368]

[Worcester12345]

(In reply to Anje from comment #101)
> (In reply to Wayne Mery (:wsmwk) from comment #98)
...
> I suggest it is modified and used  - if you feel a separate bug is required.
> 
> Some work was undertaken regarding the null entry - so it is possible the 
> local.sqlite issue could have been resolved in bug 1729664 but I suppose time 
> will tell if it works.

How much time? I'd say it should be pretty quick to know one way or the
other.

"FIXED/WORKSFORME/REOPEN"?

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

Title:
  Thunderbird 91 forgets default calendar

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

Bug description:
  Upon upgrading from Thunderbird 78 to 91, the default calendar for new
  events that I selected has been forgotten. I has Google set as the
  default, but Thunderbird 91 has changed the default to a local
  calendar that I rarely use.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 28 22:11:42 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (441 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1953611] Re: Wlan is not detected sometimes

[Sami Pietila]

Dmesg when wlan is not found.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546242/+files/dmesg.txt

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

Title:
  Wlan is not detected

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu does not always find the wlan device. A reboot might sometimes
  remedy the situation.

  ip a does not show any wlan devices, but lspci does show the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1953611] Re: Wlan is not detected sometimes

[Sami Pietila]

** Attachment added: "lspci when the wlan device is not found by ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546244/+files/pci-devices.txt

** Summary changed:

- Wlan is not detected sometimes
+ Wlan is not detected

** Description changed:

- Ubuntu does not always find the wlan device.
+ Ubuntu does not always find the wlan device. A reboot might sometimes
+ remedy the situation.
  
  ip a does not show any wlan devices, but lspci does show the device.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
-  default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600 
-  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
-  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 
600 
-  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+  default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
+  192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Wlan is not detected

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu does not always find the wlan device. A reboot might sometimes
  remedy the situation.

  ip a does not show any wlan devices, but lspci does show the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1953611] Re: Wlan is not detected sometimes

[Sami Pietila]

** Attachment added: ""ip a" when the wlan device is not found"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1953611/+attachment/5546243/+files/ipa.txt

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

Title:
  Wlan is not detected

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu does not always find the wlan device. A reboot might sometimes
  remedy the situation.

  ip a does not show any wlan devices, but lspci does show the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1953611] [NEW] Wlan is not detected

[Sami Pietila]

Public bug reported:

Ubuntu does not always find the wlan device. A reboot might sometimes
remedy the situation.

ip a does not show any wlan devices, but lspci does show the device.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: network-manager 1.32.12-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  8 13:40:43 2021
InstallationDate: Installed on 2021-11-06 (32 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  Wlan is not detected

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu does not always find the wlan device. A reboot might sometimes
  remedy the situation.

  ip a does not show any wlan devices, but lspci does show the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.32.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  8 13:40:43 2021
  InstallationDate: Installed on 2021-11-06 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto dhcp metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.30 metric 600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

[wgroiss]

I have same problem:
Ubuntu 21.10
Gnome 40.4.40
Wayland
Thunderbird 91.3.1, 

and miss the ALT+TAB-Switch really !!!

But the work around of #54 (which is new for me, thanks!!!) is fine and
helpful:

I take ALT+ESC instead of ALT+TAB (which switches directly to the next
window(s).

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

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

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

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

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


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

[Desktop-packages] [Bug 1354582] Re: Keyboard shortcuts like Ctrl-C do not work in non-english keyboard layout

[Paul White]

Thanks for the feedback Oleg, belatedly closing as issue fixed by an
unknown update.

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

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

Title:
  Keyboard shortcuts like Ctrl-C do not work in non-english keyboard
  layout

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  When my keyboard layout is different from English (I use Russian quite 
often), keyboard shortcuts do not work in any applications. For example, Ctrl-C 
and Ctrl-V do not work. They work only in English keyboard layout.
  This has never happened in previous distros before 14.04. I doubt it very 
much that it is related to my hardware or nondefault settings, because a friend 
of mine suffered from the same problem and decided to switch to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug  8 23:37:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2014-05-01 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 232
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 22:51:48 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 721 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

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


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

[Desktop-packages] [Bug 1369270] Re: unable to reset key storage

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  unable to reset key storage

Status in Ubuntu:
  Incomplete

Bug description:
  I am unable to access certificate/ key storage. Please suggest remedy.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 14 20:20:45 2014
  DistUpgraded: 2014-08-15 01:14:08,508 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-34-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ea]
  InstallationDate: Installed on 2014-05-25 (112 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=4ffa5340-61a4-4ab9-8e6f-994622ca85ba ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (30 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 01TCR4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn01TCR4:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Sep 14 19:47:04 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 939 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

[bluppfisk]

After a few more disconnects with the Ubuntu Dock disabled and no
crashes, it sounds like the culprit may be the Ubuntu Dock. The solution
should be relatively simple then (although I'm a bit shocked that it can
take down mutter)

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

Title:
  Disconnecting monitor crashes shell (wayland, gnome)

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

  Dmesg doesn't seem to contain anything useful.

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

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


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

[Desktop-packages] [Bug 1687372] Re: This error are occures

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  This error are occures

Status in Ubuntu:
  Incomplete

Bug description:
  plz tell me how to resolve this error

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May  1 13:05:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2017-05-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: LENOVO 20236
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=6827b158-7150-43fb-b29b-6e56548bc52c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN24WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500
  dmi.modalias: 
dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500:
  dmi.product.name: 20236
  dmi.product.version: Lenovo G500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon May  1 12:43:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5543 
   vendor CMO
  xserver.version: 2:1.15.1-0ubuntu2.7

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


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

[Desktop-packages] [Bug 1689902] Re: ?

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  ?

Status in Ubuntu:
  Incomplete

Bug description:
  I dont cnov

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 10 21:18:33 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:01fe]
 Subsystem: Dell Device [1028:01fe]
  InstallationDate: Installed on 2017-02-26 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude D830
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic 
root=UUID=3ddd7aa4-1147-4abb-88ba-80b2e8782e5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: DENB166367
  dmi.board.name: 0HN341
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: DENB166367
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/20/2008:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed May 10 20:58:13 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13136 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.7

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


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

[Desktop-packages] [Bug 1689322] Re: error

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  error

Status in Ubuntu:
  Incomplete

Bug description:
  error

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon May  8 18:01:17 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.36, 4.4.0-75-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ab]
  InstallationDate: Installed on 2017-03-20 (49 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3551
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-75-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 04XH5N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd07/07/2015:svnDellInc.:pnInspiron3551:pvrA04:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3551
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.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
  xserver.bootTime: Mon May  8 17:55:58 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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


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

[Desktop-packages] [Bug 1597885] Re: settings lack slider to adjust screen brightnes

[Paul White]

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

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

Title:
  settings lack slider to adjust screen brightnes

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

Bug description:
  xorg was suggested by system, I'm not sure, Thanks a lot!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun 30 11:56:41 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]
  InstallationDate: Installed on 2016-06-20 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Pavilion ZV6100 (EC356UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=16cac4e3-e299-44cf-9a9e-0afed08ab81b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1C
  dmi.board.name: 3085
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 42.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd08/24/2006:svnHewlett-Packard:pnPavilionZV6100(EC356UA#ABA):pvrF.1C:rvnHewlett-Packard:rn3085:rvr42.3B:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Pavilion ZV6100 (EC356UA#ABA)
  dmi.product.version: F.1C
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun 30 11:51:50 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1953547] GsettingsChanges.txt

[Nicolò Bianchetto]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1953547/+attachment/5546213/+files/GsettingsChanges.txt

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

Title:
  Screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1953547] ProcEnviron.txt

[Nicolò Bianchetto]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1953547/+attachment/5546215/+files/ProcEnviron.txt

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

Title:
  Screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1953547] ProcCpuinfoMinimal.txt

[Nicolò Bianchetto]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1953547/+attachment/5546214/+files/ProcCpuinfoMinimal.txt

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

Title:
  Screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1953547] ShellJournal.txt

[Nicolò Bianchetto]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1953547/+attachment/5546216/+files/ShellJournal.txt

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

Title:
  Screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1953547] Re: Screen lock doesn't work

[Nicolò Bianchetto]

apport information

** Tags added: apport-collected

** Description changed:

- Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still
- works but there is no password required anymore when the laptop awakes
- out of suspend. I did not change any settings and I still see "lock
- screen on suspend" = YES in the settings.
+ Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: Budgie:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-09-29 (69 days ago)
+ InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
+ Package: gnome-shell 40.5-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
+ RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
+ Tags:  impish
+ Uname: Linux 5.13.0-22-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1953547/+attachment/5546212/+files/Dependencies.txt

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

Title:
  Screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but 
there is no password required anymore when the laptop awakes out of suspend. I 
did not change any settings and I still see "lock screen on suspend" = YES in 
the settings.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-29 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-12-06 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1653666] Re: know not what to put here

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  know not what to put here

Status in Ubuntu:
  Incomplete

Bug description:
  post initramfs ??? error satus 1, or something like that new to ubuntu
  and don't know much about commandline and how to find and repair
  problems; please help thank you much James Street

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-51.72-lowlatency 4.4.30
  Uname: Linux 4.4.0-51-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan  3 06:02:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:1526]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:1526]
  InstallationDate: Installed on 2016-11-20 (44 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  MachineType: Hewlett-Packard HP 620
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PVI Ver. F.20
  dmi.board.name: 1526
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.0E
  dmi.chassis.asset.tag: 5CG104013Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PVIVer.F.20:bd12/12/2011:svnHewlett-Packard:pnHP620:pvrF.20:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP 620
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan  3 05:38:23 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9196 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Desktop-packages] [Bug 1662738] Re: Error on boot login

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  Error on boot login

Status in Ubuntu:
  Incomplete

Bug description:
  I get an error every time I login after a boot.  It started after an
  update and I am not sure what is causing it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb  7 20:13:06 2017
  DistUpgraded: 2016-04-19 22:45:47,223 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a3]
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF106GLM [Quadro 2000M] [1028:14a3]
  InstallationDate: Installed on 2015-11-15 (450 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Precision M4600
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-20 (293 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Feb  7 20:07:24 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21576 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Desktop-packages] [Bug 1657426] Re: bug utility gathered the errors submitted

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

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

Title:
  bug utility gathered the errors submitted

Status in Ubuntu:
  Incomplete

Bug description:
  Not known

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jan 18 16:20:11 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4350/4550] [1002:9555] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company ProBook 4720s GPU (Mobility Radeon HD 
4350) [103c:1411]
  InstallationDate: Installed on 2016-10-16 (93 days ago)
  InstallationMedia: It
  MachineType: Hewlett-Packard HP ProBook 4520s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=ecdec579-f3a0-492d-b0df-7973c01885c9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.20
  dmi.board.name: 1411
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.20:bd09/08/2011:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jan 18 16:15:44 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1670035] Re: Error while updating OS

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

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

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

Title:
  Error while updating OS

Status in Ubuntu:
  Incomplete

Bug description:
  Error BrokenCount>0...states that this usually means that installed
  packages have unmet dependencies. So, every time I attempt to install
  updates, I receive an error message and there is this error symbol on
  the top status bar, next to the clock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar  4 13:05:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-53-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:83a2]
  InstallationDate: Installed on 2016-12-07 (87 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/30/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar  4 10:26:32 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Laser Mouse MOUSE, id 8
   inputLogitech Logitech USB Keyboard KEYBOARD, id 9
   inputLogitech Logitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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


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

[Desktop-packages] [Bug 1674163] Re: imposibilidad de instalar una impresora

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.

** Description changed:

  Cada vez que intento instalarla marca error del sistema.
  No admite otra forma de instalarla
+ 
+ Google translates as:
+ Every time I try to install it, it shows a system error.
+ It does not support any other way to install it
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
-  [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
-  See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
+  [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
+  See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar 19 17:40:15 2017
  DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
-Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
+  Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
+    Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
  InstallationDate: Installed on 2016-11-12 (127 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  LANGUAGE=es_AR:es
-  PATH=(custom, no user)
-  LANG=es_AR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es_AR:es
+  PATH=(custom, no user)
+  LANG=es_AR.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=8bc8c59a-fb09-421e-99b0-9f139eff2ea1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-27 (81 days ago)
  dmi.bios.date: 07/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: G41M-GS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Mar 19 09:35:30 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id 739 
-  vendor SAM
+  product id 739
+  vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.2

** Summary changed:

- imposibilidad de instalar una impresora
+ imposibilidad de instalar una impresora (inability to install a printer)

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

** Changed