[Desktop-packages] [Bug 1918370] Re: 21.04 natural scrolling broken

2021-03-09 Thread Daniel van Vugt
Also the fix for that is proposed in:
https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu2

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

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

Title:
  21.04 natural scrolling broken

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
  follow the "push page up" that natural scrolling did...

  Super low priority, but here's my uname -a:

  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
  15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1918370/+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 1912246] Re: [nvidia] gnome-shell freezes randomly with "Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?"

2021-03-09 Thread Daniel van Vugt
It appears Marco snuck the fix for this bug into:
https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu2

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

Title:
  [nvidia] gnome-shell freezes randomly with "Window manager warning:
  MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1912246/+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 1918370] Re: 21.04 natural scrolling broken

2021-03-09 Thread Daniel van Vugt
Sounds like https://gitlab.gnome.org/GNOME/mutter/-/issues/1564 so I'll
link that one.

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

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

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1564
   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/1918370

Title:
  21.04 natural scrolling broken

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
  follow the "push page up" that natural scrolling did...

  Super low priority, but here's my uname -a:

  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
  15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1918370/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Rocko
The new mutter fixes things for me too, thanks for the quick turnaround
(Wayland still has some annoying issues)

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (ac

2021-03-09 Thread Frode Nordahl
I know, I was only suggesting possible reasons for why we're suddenly
seeing the crash now. Thx for providing the update, will take it for a
spin.

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8 
  https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c

  ---

  When clicking on the 'Clear' button in the notification panel, gnome-
  shell crashes.

  gnome-shell version: 3.38.3-3ubuntu1

  Logs:
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: **
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop polkitd(authority=local)[635]: 
Unregistered Authentication Agent for unix-session:5 (system bus name :1.226, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Main process exited, code=killed, status=6/ABRT
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Failed with result 'signal'.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Scheduled restart job, restart counter is at 3.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: Stopped GNOME Shell on X11.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.38.3-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  Tags: third-party-packages hirsute wayland-session
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lxd plugdev sudo vboxusers wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+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 1918370] Re: 21.04 natural scrolling broken

2021-03-09 Thread Daniel van Vugt
Some input issues have just been fixed in this proposed fix:

  https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu2

so please try it if you can.

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

Title:
  21.04 natural scrolling broken

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

Bug description:
  Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
  follow the "push page up" that natural scrolling did...

  Super low priority, but here's my uname -a:

  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
  15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1918370/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Daniel van Vugt
Verified all issues are fixed in
https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu2

** Tags removed: rls-hh-incoming

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (ac

2021-03-09 Thread Daniel van Vugt
Frode, this bug is really only about a crash. If the above update does
not resolve all of your issues then please open a new bug for the
recurring notification.

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8 
  https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c

  ---

  When clicking on the 'Clear' button in the notification panel, gnome-
  shell crashes.

  gnome-shell version: 3.38.3-3ubuntu1

  Logs:
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: **
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop polkitd(authority=local)[635]: 
Unregistered Authentication Agent for unix-session:5 (system bus name :1.226, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Main process exited, code=killed, status=6/ABRT
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Failed with result 'signal'.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Scheduled restart job, restart counter is at 3.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: Stopped GNOME Shell on X11.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.38.3-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  Tags: third-party-packages hirsute wayland-session
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lxd plugdev sudo vboxusers wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+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 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (ac

2021-03-09 Thread Daniel van Vugt
Everyone please test the proposed fix if you can:

https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu2

** Tags removed: rls-hh-incoming

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8 
  https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c

  ---

  When clicking on the 'Clear' button in the notification panel, gnome-
  shell crashes.

  gnome-shell version: 3.38.3-3ubuntu1

  Logs:
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: **
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop polkitd(authority=local)[635]: 
Unregistered Authentication Agent for unix-session:5 (system bus name :1.226, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Main process exited, code=killed, status=6/ABRT
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Failed with result 'signal'.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Scheduled restart job, restart counter is at 3.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: Stopped GNOME Shell on X11.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.38.3-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  Tags: third-party-packages hirsute wayland-session
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lxd plugdev sudo vboxusers wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+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 1918377] Re: In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock

2021-03-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1917939 ***
https://bugs.launchpad.net/bugs/1917939

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1917939, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1917939
   windows maximise underneath dock

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

Title:
  In Wayland after the screensaver, some maximized windows appear behind
  the ubuntu dock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Wayland, some maximized windows such as gnome-terminal and Eclipse
  get moved to behind the dock when the screensaver is unlocked, ie the
  window starts maximized and drawn next to the dock, but after locking
  and unlocking the screen it is now behind the dock (see attached
  screenshot).

  Other windows like nautilus don't have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 13:36:38 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918377/+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 1918377] [NEW] In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock

2021-03-09 Thread Rocko
Public bug reported:

In Wayland, some maximized windows such as gnome-terminal and Eclipse
get moved to behind the dock when the screensaver is unlocked, ie the
window starts maximized and drawn next to the dock, but after locking
and unlocking the screen it is now behind the dock (see attached
screenshot).

Other windows like nautilus don't have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-3ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 10 13:36:38 2021
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago)

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


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

** Attachment added: "Screenshot from 2021-03-10 13-35-14.png"
   
https://bugs.launchpad.net/bugs/1918377/+attachment/5475243/+files/Screenshot%20from%202021-03-10%2013-35-14.png

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

Title:
  In Wayland after the screensaver, some maximized windows appear behind
  the ubuntu dock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Wayland, some maximized windows such as gnome-terminal and Eclipse
  get moved to behind the dock when the screensaver is unlocked, ie the
  window starts maximized and drawn next to the dock, but after locking
  and unlocking the screen it is now behind the dock (see attached
  screenshot).

  Other windows like nautilus don't have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 13:36:38 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918377/+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 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (ac

2021-03-09 Thread Frode Nordahl
On my system, there is something creating a notification every 40 - 60
seconds, and it disappears before I get to see what it says. To stop it
from disturbing me I have turned on "Do not disturb".

I have no extensions installed.

If this crash is related to notifications, it could be that has been a
latent issue and that it surfaces now due to something spamming
notifications? I guess it depends on what others see.

Is there a way to accessing or enabling a log of notifications so that I
can help figure out the source of it?

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8 
  https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c

  ---

  When clicking on the 'Clear' button in the notification panel, gnome-
  shell crashes.

  gnome-shell version: 3.38.3-3ubuntu1

  Logs:
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: **
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop polkitd(authority=local)[635]: 
Unregistered Authentication Agent for unix-session:5 (system bus name :1.226, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Main process exited, code=killed, status=6/ABRT
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Failed with result 'signal'.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Scheduled restart job, restart counter is at 3.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: Stopped GNOME Shell on X11.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.38.3-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  Tags: third-party-packages hirsute wayland-session
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lxd plugdev sudo vboxusers wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+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 1905825] Re: [SRU] Disable CRTCs when system becomes headless

2021-03-09 Thread Rex Tsai
Macro do we have a plan when we can port the patches or upgrade to
3.36.8?

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

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

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1905825/+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 1890041] Re: Apport does not work without Chrome

2021-03-09 Thread Launchpad Bug Tracker
[Expired for xdg-utils (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xdg-utils (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Apport does not work without Chrome

Status in xdg-utils package in Ubuntu:
  Expired

Bug description:
  I cannot recall Apport ever working for me, but this time it fails
  because I don't have chromium installed on my machine.  I use Firefox
  instead.

  Besides, on the second screen, "I don't know" should realy be called
  "My bug is not listed".

  Error message:
  arcturus ~ > apport-bug 
  1276
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)
  non-network local connections being added to access control list
  sudo: chromium-browser: command not found

  Further information:
  Kubuntu 20.04.1 LTS

  apport:
Installed: 2.20.11-0ubuntu27.4
Candidate: 2.20.11-0ubuntu27.4
Version table:
   *** 2.20.11-0ubuntu27.4 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.11-0ubuntu27 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1890041/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Treviño
** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1917204] Re: VGA stuck at 1024x768 (no EDID detected)

2021-03-09 Thread Daniel van Vugt
Is this a recent regression (caused by updates) or has it always been
stuck at low resolution?

** Summary changed:

- high Resolution is not getting 
+ VGA stuck at 1024x768 (no EDID detected)

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

** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Summary changed:

- VGA stuck at 1024x768 (no EDID detected)
+ [i915] VGA stuck at 1024x768 (no EDID detected)

** Changed in: linux-signed-hwe-5.8 (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/1917204

Title:
  [i915] VGA stuck at 1024x768 (no EDID detected)

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  I'm not getting my Monitor supporting resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 28 14:40:41 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1019:7df5]
  InstallationDate: Installed on 2021-01-20 (38 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS H61H2-MV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=UUID=671d72b0-98f0-468f-a72f-910d30b2051a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-MV
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/13/2014:br4.6:svnECS:pnH61H2-MV:pvr1.0:rvnECS:rnH61H2-MV:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H61H2-MV
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917204/+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 1918370] Re: 21.04 natural scrolling broken

2021-03-09 Thread Daniel van Vugt
** Tags added: hirsute

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

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

Title:
  21.04 natural scrolling broken

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

Bug description:
  Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
  follow the "push page up" that natural scrolling did...

  Super low priority, but here's my uname -a:

  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
  15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1918370/+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 1915279] Re: about

2021-03-09 Thread Daniel van Vugt
Can you please attach a screenshot or photo of the problem?

** Package changed: xorg (Ubuntu) => chromium-browser (Ubuntu)

** Changed in: chromium-browser (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/1915279

Title:
  about

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  all chromium server have heavy issue in render

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 10 20:16:29 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
  InstallationDate: Installed on 2021-02-04 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. OptiPlex 760
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=136e728b-139d-400a-b333-620a8490dd1d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.release: 16.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0M858N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd08/06/2013:br16.0:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915279/+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 1918371] Re: super-tab or alt-tab only recognising two apps when more open

2021-03-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1917926, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: hirsute

** This bug has been marked a duplicate of bug 1917926
   Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

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

Title:
  super-tab or alt-tab  only recognising two apps when more open

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  21.04 - Super-tab or alt-tab app switching only seems to catch the
  first two open apps  even though more apps open... Super alone does
  show correct apps laid as expected (cascaded as nicely as Gnome always
  has)...

  Low priority...

  Gnome 3.38.4
  uname -a:
  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 
15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918371/+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 1918371] [NEW] super-tab or alt-tab only recognising two apps when more open

2021-03-09 Thread Rob Hendricks
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926

Public bug reported:

21.04 - Super-tab or alt-tab app switching only seems to catch the first
two open apps  even though more apps open... Super alone does show
correct apps laid as expected (cascaded as nicely as Gnome always
has)...

Low priority...

Gnome 3.38.4
uname -a:
Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 15:50:19 
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

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


** Tags: hirsute

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

Title:
  super-tab or alt-tab  only recognising two apps when more open

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  21.04 - Super-tab or alt-tab app switching only seems to catch the
  first two open apps  even though more apps open... Super alone does
  show correct apps laid as expected (cascaded as nicely as Gnome always
  has)...

  Low priority...

  Gnome 3.38.4
  uname -a:
  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 
15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918371/+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 1918370] [NEW] 21.04 natural scrolling broken

2021-03-09 Thread Rob Hendricks
Public bug reported:

Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
follow the "push page up" that natural scrolling did...

Super low priority, but here's my uname -a:

Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: 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/1918370

Title:
  21.04 natural scrolling broken

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not
  follow the "push page up" that natural scrolling did...

  Super low priority, but here's my uname -a:

  Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3
  15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918370/+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 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (ac

2021-03-09 Thread Daniel van Vugt
** Tags added: rls-hh-incoming

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8 
  https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c

  ---

  When clicking on the 'Clear' button in the notification panel, gnome-
  shell crashes.

  gnome-shell version: 3.38.3-3ubuntu1

  Logs:
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: **
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop gnome-shell[3639]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
  Mar 07 11:34:04 yushijinhun-laptop polkitd(authority=local)[635]: 
Unregistered Authentication Agent for unix-session:5 (system bus name :1.226, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Main process exited, code=killed, status=6/ABRT
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Failed with result 'signal'.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: org.gnome.Shell@x11.service: 
Scheduled restart job, restart counter is at 3.
  Mar 07 11:34:04 yushijinhun-laptop systemd[655]: Stopped GNOME Shell on X11.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.38.3-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
  Tags: third-party-packages hirsute wayland-session
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lxd plugdev sudo vboxusers wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Daniel van Vugt
** Summary changed:

- Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
+ Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926

This looks connected to bug 1917926 so let's track it there for now.

** Tags added: hirsute

** This bug has been marked a duplicate of bug 1917926
   Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

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

Title:
  I can't move the windows on Ubuntu 21.04

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

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1918224] Re: caps lock delay on ubuntu

2021-03-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1376903 ***
https://bugs.launchpad.net/bugs/1376903

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1376903, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1376903
   Caps lock delay

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

Title:
  caps lock delay on ubuntu

Status in xorg-server package in Ubuntu:
  New

Bug description:
  this bug has been around for ages and no one has fixed it until today,
  it has been ages since I last used Ubuntu and I have tried to use it
  now, on my new Laptop but I'm encountering the same issue so mostly it
  isn't a hardware issue, so I decided to look into it and realized that
  I'm not the only one encountering this issue

  https://forums.linuxmint.com/viewtopic.php?t=267964
  
https://www.reddit.com/r/Ubuntu/comments/9lo5if/is_there_a_solution_for_caps_lock_delay_yet/
  https://github.com/hexvalid/Linux-CapsLock-Delay-Fixer

  I understand that there is an issue with xorgserver and the developers
  there has not accepted or commited the patches yet

  hope this can be really look into cause to tell someone to use Shift
  does not make sense you are forcing someone to do it, I have been
  using caps lock my whole life

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1918224/+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 1918355] Re: Cannot get passed the recreation of an Unknown document

2021-03-09 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  Cannot get passed the recreation of an Unknown document

Status in libreoffice package in Ubuntu:
  New

Bug description:
  For some reason I can't seem to find a way to get passed the guide to
  recreate an Unknown document. The document got recreated successfully,
  but as soon as the main Libreoffice GUI appeared and I clicked to open
  Libreoffice Draw I'm back at having to recreate the same document
  again and it goes on and on and on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libreoffice-draw 1:7.0.3-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 02:11:27 2021
  InstallationDate: Installed on 2021-01-10 (58 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: gconf2
  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/1918355/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen

2021-03-09 Thread Daniel van Vugt
The closest upstream bug I can find is https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/933

If you think a new bug is required instead of that then please create
one and tell us the ID here.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #933
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/933

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

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

Title:
  Characters from dead keys shown in plan view in password field on
  login screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  2) apt-cache policy gdm3
  gdm3:
Installed: 3.38.1-2ubuntu1.1
Candidate: 3.38.1-2ubuntu1.1
Version table:
   *** 3.38.1-2ubuntu1.1 500
  500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.38.1-2ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

  3) I expect all characters, even those from dead keys, to be hidden
  the same ways as other characters

  4) When using dead keys to add accents to letters on the password
  prompt on the login screen, before the letter the dead key is intended
  for is typed, the special characters from the dead keys are displayed
  in plain sight, instead of being obscured by dots as other letters and
  characters are.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gdm3 3.38.1-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 12:51:19 2021
  InstallationDate: Installed on 2018-11-26 (770 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1910220/+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 1917801] Re: Multi monitor bug opening windows (not responsive to input in the location it is drawn)

2021-03-09 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

** Tags added: nvidia

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

Title:
  Multi monitor bug opening windows (not responsive to input in the
  location it is drawn)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When i open a window like Spotify or GitKracken, that should open in
  my second monitor (because i always use them there), Ubuntu draws it
  in my main monitor, but, if i try to move it, resize or press an area
  of the window, it selects the window that is under it (like if the
  windows does not logically exist there). If i click on the window
  title bar, it sometimes appears on the second monitor and is resized
  (also if i press the minimize button or others). Sometimes the window
  is not responding until i do not minimize it from the dock and re-
  maximize it. Once it does that everything works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  4 20:18:29 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.39, 5.8.0-43-generic, x86_64: installed
   nvidia, 460.39, 5.8.0-44-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2021-01-17 (46 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Daniel van Vugt
A full revert should also fix another regression -> bug 1918033

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

Title:
  Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1912246] Re: [nvidia] gnome-shell freezes randomly with "Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?"

2021-03-09 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-3.38.4 fixed-upstream

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

Title:
  [nvidia] gnome-shell freezes randomly with "Window manager warning:
  MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1912246/+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 1918335] Re: intermittent stalls of the user interface

2021-03-09 Thread Daniel van Vugt
1. What is the message you see?

2. Next time a stall happens, please open a Terminal and run:

   lspci -kv > lspci.txt
   journalctl -b0 > journal.txt

   and attach the resulting text files here.


** Tags added: performance

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

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

Title:
  intermittent stalls of the user interface

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Seeing intermittent stalls of the user interface and I noticed a
  coincidence with this message -- maybe not related.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  9 14:44:05 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-05 (32 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918335/+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 1319494] Re: Ubuntu installation image should come with mdadm

2021-03-09 Thread Yuan-Chen Cheng
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Fix Released

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

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

Title:
  Ubuntu installation image should come with mdadm

Status in OEM Priority Project:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  It would be great if the Ubuntu installation image came with mdadm. If
  was unlucky enough to be Internetless while installing Ubuntu, I
  wouldn't be able to install to or create a RAID array. I know that
  Ubuntu has lessened its restrictions on installation image size, and
  since mdadm's installed size is 1.2MB, I think it should be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  Date: Wed May 14 17:27:51 2014
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.4
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1319494/+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 1918355] [NEW] Cannot get passed the recreation of an Unknown document

2021-03-09 Thread Kristoffer Grundström
Public bug reported:

For some reason I can't seem to find a way to get passed the guide to
recreate an Unknown document. The document got recreated successfully,
but as soon as the main Libreoffice GUI appeared and I clicked to open
Libreoffice Draw I'm back at having to recreate the same document again
and it goes on and on and on.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libreoffice-draw 1:7.0.3-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 10 02:11:27 2021
InstallationDate: Installed on 2021-01-10 (58 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: gconf2
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy third-party-packages uec-images

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

Title:
  Cannot get passed the recreation of an Unknown document

Status in libreoffice package in Ubuntu:
  New

Bug description:
  For some reason I can't seem to find a way to get passed the guide to
  recreate an Unknown document. The document got recreated successfully,
  but as soon as the main Libreoffice GUI appeared and I clicked to open
  Libreoffice Draw I'm back at having to recreate the same document
  again and it goes on and on and on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libreoffice-draw 1:7.0.3-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 02:11:27 2021
  InstallationDate: Installed on 2021-01-10 (58 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: gconf2
  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/1918355/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Treviño
Paul such issues on 21.10 are tracked by bug #1917926

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

Title:
  I can't move the windows on Ubuntu 21.04

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

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Treviño
** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1793472] Re: [wishlist] Add mdadm into desktop by default

2021-03-09 Thread john liptrot
*** This bug is a duplicate of bug 1319494 ***
https://bugs.launchpad.net/bugs/1319494

** This bug has been marked a duplicate of bug 1319494
   Ubuntu installation image should come with mdadm

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

Title:
  [wishlist] Add mdadm into desktop by default

Status in OEM Priority Project:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Consider the situation that we have OEM systems with software raid
  devices and the desktop image will be installed on them as primary
  storage. Another work is to patch casper to support md (Please refer
  bug #1793444).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1793472/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2021-03-09 Thread Ákos Pintér
Note - I oftenly watch 4k HDR movies and I was trying Kodi but it was
pretty unsaturated. VLC was my savior. Then I just tried MPV. Pretty
good!

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2021-03-09 Thread Ákos Pintér
Hi everyone!

Just deleted 2 syslogs which sized 83GB altogether. The problem still
persists. Another things which I saw, after clearing the syslogs. The
recursive loop does not only appear when we go to suspend mode with
paused vlc or when switching users. For me, it created a bit more than
400 lines of code by just opening a movie with VLC and then pausing it
to check what's happening in syslog. I think that's a big problem
already, since I bought an ssd a year ago and the health already dropped
to 98% from 100%. I don't leave my partition full all the time if anyone
would wonder and I don't write / read a lot to it. So I can only imagine
that these big chunks of reading/writing of codes did damage to the
ssd's health.

I'm not going to risk it, I am changing vlc to something else. I will
begin the hunt now.

P.s: Rubo's workaround didn't work for me.

Have a good day!

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1915752] Re: Why does the package have a dependency on gnome-shell

2021-03-09 Thread fossfreedom
*** This bug is a duplicate of bug 1918336 ***
https://bugs.launchpad.net/bugs/1918336

** This bug has been marked a duplicate of bug 1918336
   Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

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

Title:
  Why  does the package have a dependency on gnome-shell

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Quick question - why does the binary package have a dependency on
  gnome-shell?

  This turns the package into a GNOME Shell specific package.  I was
  hoping the gnome-remote-desktop could be used on Ubuntu Budgie - but
  this dependency prevents this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-remote-desktop 0.1.9-4
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 15 19:26:54 2021
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  RebootRequiredPkgs: gnome-shell
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1915752/+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 1918335] [NEW] intermittent stalls of the user interface

2021-03-09 Thread Michaelian Ennis
Public bug reported:

Seeing intermittent stalls of the user interface and I noticed a
coincidence with this message -- maybe not related.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  9 14:44:05 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-05 (32 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  intermittent stalls of the user interface

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Seeing intermittent stalls of the user interface and I noticed a
  coincidence with this message -- maybe not related.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  9 14:44:05 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-05 (32 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918335/+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 1918336] [NEW] Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

2021-03-09 Thread fossfreedom
Public bug reported:

Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable
(main)

Changelog entries since current hirsute version 0.1.9-4build1:

gnome-remote-desktop (0.1.9-5) unstable; urgency=medium

  * Team upload

  [ David Mohammed ]
  * debian/control: add budgie-desktop as an alternate for gnome-shell
(Closes: #982937)

 -- Simon McVittie   Tue, 09 Mar 2021 10:31:04 +

** Affects: gnome-remote-desktop (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: gnome-remote-desktop (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable
  (main)

  Changelog entries since current hirsute version 0.1.9-4build1:

  gnome-remote-desktop (0.1.9-5) unstable; urgency=medium

* Team upload

[ David Mohammed ]
* debian/control: add budgie-desktop as an alternate for gnome-shell
  (Closes: #982937)

   -- Simon McVittie   Tue, 09 Mar 2021 10:31:04 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1918336/+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 1912854] Re: snap autorefresh breaks some fonts

2021-03-09 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1616650 ***
https://bugs.launchpad.net/bugs/1616650

** This bug has been marked a duplicate of bug 1616650
   snap refresh while command is running may cause issues

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

Title:
  snap autorefresh breaks some fonts

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  If the chromium snap happens to refresh when the browser is running,
  some fonts break and just display squares instead of text (see
  screenshot).

  Checking version reported by chromium itself and snap revision
  confirms that an update happened.

  Also snap changes confirms it:

  $ snap changes chromium
  ID   Status  Spawn   Ready   Summary
  399  Donetoday at 22:00 CET  today at 22:01 CET  Auto-refresh snap 
"chromium"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan 22 22:12:55 2021
  InstallationDate: Installed on 2020-10-18 (96 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  Snap: chromium 88.0.4324.96 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1912854/+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 1918327] Re: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build on hirsute 21.04

2021-03-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build
  on hirsute 21.04

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

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 21.04 installed
  2a. Launch Software & Updates, go to Additional Drivers tab, select 
nvidia-340 to install
  2b. Open terminal and execute `sudo apt-get install nvidia-340`

  Expected results:
  * nvidia-340 driver is installed

  Actual results:
  * nvidia-340 driver is not installed:

  $ dpkg -l | grep -i nvidia
  ii  libcuda1-340 340.108-0ubuntu7 
amd64NVIDIA CUDA runtime library
  ii  mate-optimus 20.10.0-1ubuntu2 
all  MATE Desktop applet for 
controlling NVIDIA Optimus graphics cards
  iF  nvidia-340   340.108-0ubuntu7 
amd64NVIDIA binary driver - version 
340.108
  ii  nvidia-opencl-icd-340340.108-0ubuntu7 
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime 0.8.16   
all  Tools to enable NVIDIA's Prime
  ii  nvidia-settings  460.39-0ubuntu1  
amd64Tool for configuring the 
NVIDIA graphics driver
  ii  screen-resolution-extra  0.18build2   
all  Extension for the 
nvidia-settings control panel

  ^^^ note "iF  nvidia-340" above.

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: nvidia-340 340.108-0ubuntu7
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.10.0-14-generic
  Date: Tue Mar  9 23:43:06 2021
  DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu7:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:368:40:
 error: passing argument 1 of ‘drm_prime_pages_to_sg’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-03-09 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210309)
  PackageVersion: 340.108-0ubuntu7
  Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.7.1ubuntu3
   apt  2.2.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1918327/+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 1918327] [NEW] nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build on hirsute 21.04

2021-03-09 Thread Norbert
Public bug reported:

Steps to reproduce:
1. Have Ubuntu MATE 21.04 installed
2a. Launch Software & Updates, go to Additional Drivers tab, select nvidia-340 
to install
2b. Open terminal and execute `sudo apt-get install nvidia-340`

Expected results:
* nvidia-340 driver is installed

Actual results:
* nvidia-340 driver is not installed:

$ dpkg -l | grep -i nvidia
ii  libcuda1-340 340.108-0ubuntu7   
  amd64NVIDIA CUDA runtime library
ii  mate-optimus 20.10.0-1ubuntu2   
  all  MATE Desktop applet for 
controlling NVIDIA Optimus graphics cards
iF  nvidia-340   340.108-0ubuntu7   
  amd64NVIDIA binary driver - version 
340.108
ii  nvidia-opencl-icd-340340.108-0ubuntu7   
  amd64NVIDIA OpenCL ICD
ii  nvidia-prime 0.8.16 
  all  Tools to enable NVIDIA's Prime
ii  nvidia-settings  460.39-0ubuntu1
  amd64Tool for configuring the NVIDIA 
graphics driver
ii  screen-resolution-extra  0.18build2 
  all  Extension for the 
nvidia-settings control panel

^^^ note "iF  nvidia-340" above.

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: nvidia-340 340.108-0ubuntu7
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
DKMSKernelVersion: 5.10.0-14-generic
Date: Tue Mar  9 23:43:06 2021
DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu7:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:368:40:
 error: passing argument 1 of ‘drm_prime_pages_to_sg’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-03-09 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210309)
PackageVersion: 340.108-0ubuntu7
Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.7.1ubuntu3
 apt  2.2.1
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-package hirsute

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

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

Title:
  nvidia-340 340.108-0ubuntu7: nvidia-340 kernel module failed to build
  on hirsute 21.04

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

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 21.04 installed
  2a. Launch Software & Updates, go to Additional Drivers tab, select 
nvidia-340 to install
  2b. Open terminal and execute `sudo apt-get install nvidia-340`

  Expected results:
  * nvidia-340 driver is installed

  Actual results:
  * nvidia-340 driver is not installed:

  $ dpkg -l | grep -i nvidia
  ii  libcuda1-340 340.108-0ubuntu7 
amd64NVIDIA CUDA runtime library
  ii  mate-optimus 20.10.0-1ubuntu2 
all  MATE Desktop applet for 
controlling NVIDIA Optimus graphics cards
  iF  nvidia-340   340.108-0ubuntu7 
amd64NVIDIA binary driver - version 
340.108
  ii  nvidia-opencl-icd-340340.108-0ubuntu7 
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime 0.8.16   
all  Tools to enable NVIDIA's Prime
  ii  nvidia-settings  460.39-0ubuntu1  
amd64Tool for configuring the 
NVIDIA graphics driver
  ii  screen-resolution-extra  0.18build2   
all  Extension for the 
nvidia-settings control panel

  ^^^ note "iF  nvidia-340" above.

  ProblemType: Package
  DistroRelea

[Desktop-packages] [Bug 1912854] Re: snap autorefresh breaks some fonts

2021-03-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  snap autorefresh breaks some fonts

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  If the chromium snap happens to refresh when the browser is running,
  some fonts break and just display squares instead of text (see
  screenshot).

  Checking version reported by chromium itself and snap revision
  confirms that an update happened.

  Also snap changes confirms it:

  $ snap changes chromium
  ID   Status  Spawn   Ready   Summary
  399  Donetoday at 22:00 CET  today at 22:01 CET  Auto-refresh snap 
"chromium"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan 22 22:12:55 2021
  InstallationDate: Installed on 2020-10-18 (96 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  Snap: chromium 88.0.4324.96 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1912854/+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 1918317] Re: nautilus crashed with SIGSEGV in g_application_impl_get_dbus_object_path()

2021-03-09 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1820859 ***
https://bugs.launchpad.net/bugs/1820859

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1820859, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1820859
   nautilus --version segfaults in g_application_impl_get_dbus_object_path

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

Title:
  nautilus crashed with SIGSEGV in
  g_application_impl_get_dbus_object_path()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I started up and gave me this bug. I haven't even opened nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  9 20:35:08 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-03-09 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  ProcCmdline: nautilus --version
  SegvAnalysis:
   Segfault happened at: 0x7f965192c414:mov0x20(%rdi),%rax
   PC (0x7f965192c414) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   update_dbus_opened_locations ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince3.39.2-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918317/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2021-03-09 Thread Dan Streetman
root@lp1880258-b:~# dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.44 amd64system and service manager
root@lp1880258-b:~# host jifaslrjfiudrlj.com
Host jifaslrjfiudrlj.com not found: 3(NXDOMAIN)
root@lp1880258-b:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
Mar 09 18:15:29 lp1880258-b systemd-resolved[786]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
Mar 09 18:25:51 lp1880258-b systemd-resolved[786]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.


(upgrade/reboot)

root@lp1880258-b:~# dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.45 amd64system and service manager
root@lp1880258-b:~# host jifaslrjfiudrlj.com
Host jifaslrjfiudrlj.com not found: 3(NXDOMAIN)
root@lp1880258-b:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
root@lp1880258-b:~# 


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

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

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

  [original description]

  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes

  Now make the hostname absolute with the trailing dot above and run:
     systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2021-03-09 Thread Dan Streetman
fixed in hirsute with:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2

at version 247.3-1ubuntu4

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

  [original description]

  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes

  Now make the hostname absolute with the trailing dot above and run:
     systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2021-03-09 Thread Dan Streetman
root@lp1880258-f:~# dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.4 amd64system and service manager
root@lp1880258-f:~# host gfjrisldfjrfj.com
Host gfjrisldfjrfj.com not found: 3(NXDOMAIN)
root@lp1880258-f:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
Mar 09 18:15:29 lp1880258-f systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
Mar 09 18:24:39 lp1880258-f systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
Mar 09 18:24:49 lp1880258-f systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.


(upgrade and reboot)

root@lp1880258-f:~# dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.5 amd64system and service manager
root@lp1880258-f:~# host gfjrisldfjrfj.com
Host gfjrisldfjrfj.com not found: 3(NXDOMAIN)
root@lp1880258-f:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
root@lp1880258-f:~#

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

  [original description]

  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes

  Now make the hostname absolute with the trailing dot above and run:
     systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Paul Goins
Attempting to attach a screen capture video.

** Attachment added: "simplescreenrecorder-2021-03-09_08.18.31.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+attachment/5475163/+files/simplescreenrecorder-2021-03-09_08.18.31.mkv

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

Title:
  I can't move the windows on Ubuntu 21.04

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

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Paul Goins
I've encountered the same problem today.

I did a little more testing, and I've observed other issues as well,
some which may be related, arguably some which may be separate bugs, but
I'll list them nonetheless:

* Cannot move gnome-terminal windows by dragging the title bar.
* Right clicking the gnome-terminal title bar opens the context menu, but it 
disappears as soon as the right mouse button is released.  (As a partial 
workaround for the first bullet: If I hold the right mouse button, go down to 
"Move", and then release it, it activates the Move option and I can move the 
window.)
* Other windows (firefox snap, emacs) won't switch focus back to gnome-terminal 
easily unless you resize the window a little bit, after which they'll allow you 
to do so.  Strangely, the same problem doesn't extend to switching between 
snapped firefox and emacs.
* alt-tab doesn't show any visual overlay, and only switches between the last 2 
windows.
* Toggling a VPN connection via the top right hand corner menu will cause a 
crash and reload of the UI.  (I just toggled my connection to the Canonical VPN 
twice, and each time I did so, this happened.)

I don't know if there's a shared underlying library that this is all
related to or not; maybe these issues need to be broken apart.
Nonetheless, reporting this so at least we have the info somewhere.

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

Title:
  I can't move the windows on Ubuntu 21.04

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

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2021-03-09 Thread Dan Streetman
with -release version of systemd:

root@lp1880258-g:~# host afhjisrfljsdirfj.com
Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN)

root@lp1880258-g:~# journalctl -b -u systemd-resolved --no-pager
...
Mar 09 18:07:46 lp1880258-g systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
Mar 09 18:09:11 lp1880258-g systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
Mar 09 18:09:14 lp1880258-g systemd-resolved[624]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.



root@lp1880258-g:~# dpkg -l systemd|grep systemd
ii  systemd246.6-1ubuntu1.2 amd64system and service manager
root@lp1880258-g:~# host afhjisrfljsdirfj.com
Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN)
root@lp1880258-g:~# host afhjisrfljsdirfj.com
Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN)
root@lp1880258-g:~# host afhjisrfljsdirfj.com
Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN)
root@lp1880258-g:~# journalctl -b -u systemd-resolved --no-pager | grep NXDOMAIN
root@lp1880258-g:~# 



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

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

  [original description]

  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes

  Now make the hostname absolute with the trailing dot above and run:
     systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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


Re: [Desktop-packages] [Bug 1917191]

2021-03-09 Thread John F. Godfrey
Good morning!
Are we any closer to getting this bug fixed?
Thanks!
john

On Mon, Mar 8, 2021 at 2:05 PM Petruta-rasa-z <1917...@bugs.launchpad.net>
wrote:

> *** Bug 1696411 has been marked as a duplicate of this bug. ***
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1917191
>
> Title:
>   firefox will not start after it crashed unexpectedly
>
> Status in Mozilla Firefox:
>   Fix Released
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   firefox crashed unexpectedly, and it will not start or restart.  I am
> running the latest ubuntu-20.04.2 LTS, all updates applied.  firefox
> 86.0+build3
>   ---
>   ProblemType: Bug
>   AddonCompatCheckDisabled: False
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  johnfg 1725 F pulseaudio
>/dev/snd/controlC1:  johnfg 1725 F pulseaudio
>   BuildID: 20210222142601
>   CasperMD5CheckResult: skip
>   Channel: Unavailable
>   CurrentDesktop: ubuntu:GNOME
>   DefaultProfileExtensions: extensions.sqlite corrupt or missing
>   DefaultProfileIncompatibleExtensions: Unavailable (corrupt or
> non-existant compatibility.ini or extensions.sqlite)
>   DefaultProfileLocales: extensions.sqlite corrupt or missing
>   DefaultProfilePrefErrors: Unexpected character ',' before close
> parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348
>   DefaultProfilePrefSources: prefs.js
>   DefaultProfileThemes: extensions.sqlite corrupt or missing
>   DistroRelease: Ubuntu 20.04
>   ForcedLayersAccel: False
>   InstallationDate: Installed on 2020-02-22 (371 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   IpRoute:
>default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600
>10.8.0.0/24 via 10.8.0.17 dev tun0
>10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18
>169.254.0.0/16 dev wlp10s0 scope link metric 1000
>192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8
> metric 600
>   NonfreeKernelModules: openafs
>   Package: firefox 86.0+build3-0ubuntu0.20.04.1
>   PackageArchitecture: amd64
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
>   Profile0Extensions: extensions.sqlite corrupt or missing
>   Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
>   Profile0Locales: extensions.sqlite corrupt or missing
>   Profile0PrefErrors: Unexpected character ',' before close parenthesis @
> /usr/lib/firefox/omni.ja:greprefs.js:348
>   Profile0PrefSources: prefs.js
>   Profile0Themes: extensions.sqlite corrupt or missing
>   Profiles:
>Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date)
>Profile0 - LastVersion=86.0/20210222142601
>   RunningIncompatibleAddons: False
>   Tags:  focal
>   Uname: Linux 5.4.0-66-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 07/05/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V4.00L12
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: CF52-4
>   dmi.board.vendor: Panasonic Corporation
>   dmi.board.version: 1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Panasonic Corporation
>   dmi.chassis.version: 001
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001:
>   dmi.product.family: CF52-4
>   dmi.product.name: CF-52SLGDD1M
>   dmi.product.sku: CF-52SLGDD1M
>   dmi.product.version: 004
>   dmi.sys.vendor: Panasonic Corporation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions
>


-- 
John F. Godfrey, Pastor
Belgrade Christian Assembly
Belgrade, Montana  USA
"Jesus said to him, 'I am the Way, the Truth, and the Life; no one comes to
the Father, except through Me'" (John 14:6).

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

Title:
  firefox will not start after it crashed unexpectedly

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

Bug description:
  firefox crashed unexpectedly, and it will not start or restart.  I am running 
the latest ubuntu-20.04.2 LTS, all updates applied.  firefox 86.0+build3
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS 

[Desktop-packages] [Bug 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Heather Ellsworth
on a focal vm (# deb cdrom:[Ubuntu 20.04 LTS _Focal Fossa_ - Release
amd64 (20200423)]/ focal main restricted) that has been updated, i had
6.4.6-0ubuntu0.20.04.1 installed and upgraded to
6.4.7-0ubuntu0.20.04.1~lo3 and it brought in jre:
https://paste.ubuntu.com/p/zrmBgYwy9d/

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1916488] Re: SRU 1.64.5 to focal

2021-03-09 Thread Brian Murray
Hello Marco, or anyone else affected,

Accepted gjs into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.64.5-0ubuntu0.20.04.01 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU 1.64.5 to focal

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some performance 
improvements and crash fixes backported from the development branch.
  https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.5

  [ Test case ]

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

  GNOME Shell and its components should continue working with no
  javascript related errors, as well other gjs based apps like polari

  [ Regression potential ]

  GJS based GTK4 should work properly, resolution of GI types was
  changed and so exported GI types should continue working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1916488/+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 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Rico Tzschichholz
The proposed fix for this problem
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h
=ubuntu-hirsute-7.1=300a88e9703130591af5ca1c4477d4dc9e53918e

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1918310] [NEW] evince doesn't represent transparency in PDFs

2021-03-09 Thread Morten Nissov
Public bug reported:

Transparency in pdfs isn't represented by the standard checkered, gray
pattern. Instead evince just sets the background to white.

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

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

Title:
  evince doesn't represent transparency in PDFs

Status in evince package in Ubuntu:
  New

Bug description:
  Transparency in pdfs isn't represented by the standard checkered, gray
  pattern. Instead evince just sets the background to white.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1918310/+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 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Rik Mills
A more complete link for that commit:
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h
=ubuntu-hirsute-7.1=887b7543b90368901ade31725b8cb522d86fa7f8

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Rik Mills
Dependency to ure-java added in debian/control?

https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/control?h
=ubuntu-hirsute-7.1=887b7543b90368901ade31725b8cb522d86fa7f8

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb

2021-03-09 Thread Heather Ellsworth
Turns out the current fix (just adding libreoffice-sdbc-hsqldb) causes
openjdk to be pulled in on ISOs:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308

Changing the status of this bug until an alternative solution is found.

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

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

Title:
  weak dependency to libreoffice-sdbc-hsqldb

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  The user can't create a new Base file with the wizard if the
  libreoffice-sdbc-hsqldb package isn't installed. The package
  libreoffice-base-drivers has only a "suggests" dependency to
  libreoffice-sdbc-hsqldb. It should have a "depends" dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 24 18:32:22 2021
  InstallationDate: Installed on 2020-10-12 (134 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1916786/+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 1918308] [NEW] Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-09 Thread Heather Ellsworth
Public bug reported:

Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
ure-jave/jdk/jre.

Build log:
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

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

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+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 1916476] Re: [MIR] power-profiles-daemon

2021-03-09 Thread Didier Roche
./change-override -c main -S power-profiles-daemon
Override component to main
power-profiles-daemon 0.1-1~fakesync2 in hirsute: universe/admin -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute amd64: 
universe/admin/optional/100% -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute arm64: 
universe/admin/optional/100% -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute armhf: 
universe/admin/optional/100% -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute ppc64el: 
universe/admin/optional/100% -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute riscv64: 
universe/admin/optional/100% -> main
power-profiles-daemon 0.1-1~fakesync2 in hirsute s390x: 
universe/admin/optional/100% -> main
Override [y|N]? y
7 publications overridden.

** Changed in: power-profiles-daemon (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] power-profiles-daemon

Status in power-profiles-daemon package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  It's available on the Ubuntu supported architectures
  https://launchpad.net/ubuntu/+source/power-profiles-daemon/0.1-1~fakesync2

  The package is in sync with Debian (currently fakesynced to bypass NEW
  delays)

  * Rationale

  The new GNOME version integrates with the service to allow the users
  to select a power profile

  The binary to promote is power-profiles-daemon

  Ideally we would like to integrate the feature in the desktop this
  cycle

  * Security

  There is no known security issues

  
https://security-tracker.debian.org/tracker/source-package/power-profiles-daemon
  
https://people.canonical.com/~ubuntu-security/cve/pkg/power-profiles-daemon.html
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=power-profiles-daemon

  * Quality assurance

  The desktop team is going to subscribe to the package

  https://launchpad.net/ubuntu/+source/power-profiles-daemon/+bugs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=power-profiles-daemon

  There are no bugs reported but the component is new.

  The package build is doing the upstream 'make test'

  > 1/1 power-profiles-daemon-integration-test OK 1.57s
  >
  > Ok: 1'

  The upstream integration tests are set as autopkgtest
  https://autopkgtest.ubuntu.com/packages/p/power-profiles-daemon/hirsute/amd64

  * Dependencies

  The dependencies are in main (libc, libglib, libgudev, libupower-glib)

  * Standards compliance

  current 4.5.1 standards-version, debhelper compat 13, dh style simple
  rules

  * Maintenance

  Upstream is active, the package is maintained in Debian and desktop
  team is going to sign up for Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1916476/+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 1918186] ThreadStacktrace.txt

2021-03-09 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1918186/+attachment/5475143/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

** Tags removed: need-amd64-retrace

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  New

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

2021-03-09 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1918186/+attachment/5475142/+files/StacktraceSource.txt

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  New

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1918186/+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 1918186] tracker-store crashed with signal 5 in g_printerr()

2021-03-09 Thread Apport retracing service
StacktraceTop:
 g_printerr (format=0x7f13295419c0 "\001") at ../../../glib/gmessages.c:3369
 sqlite3MemMalloc (nByte=693369344) at sqlite3.c:23772
 ?? ()
 ?? ()
 ?? ()

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  New

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

2021-03-09 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1918186/+attachment/5475141/+files/Stacktrace.txt

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  New

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1918186/+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 1908082] Re: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark

2021-03-09 Thread Olivier Tilloy
Similarly, I'm seeing better performance for the snap version of firefox
than with the deb, on Ubuntu 20.10:

  deb: 85.1 ± 1.4
  snap: 108 ± 1.5

This could very well be explained by the toolchain and default build
options used to build each package: the snap is built from an upstream
binary, compiled with a very recent toolchain and likely many
optimizations turned on, whereas the deb uses the toolchain available in
the corresponding Ubuntu series, and often not with full optimizations
to work around hardware limitations in the Launchpad build farm or
toolchain bugs.

This is not to say that we cannot research turning on more optimizations
though.

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

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

Title:
  Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer
  benchmark

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  I installed Firefox Flatpak
  (https://flathub.org/apps/details/org.mozilla.firefox) and Chrome.

  I executed closed all apps and processes and one by one I executed
  Speedometer test (https://browserbench.org/Speedometer2.0/) in each
  browser 3 times. I took the max score for reach browser out of the 3
  executions of the test.

  Actual results:

  Results
  100.3 - Firefox Flatpak
  85.42 - FIrefox DEB (pre-installd from the store)
  100.3 - Google Chrome

  The preinstalled DEB package Firefox was slower than both Firefox
  Flatpak and Chrome

  Expected results:

  I expected Firefox DEB and Firefox Flatpak to have the same results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908082/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Leo
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Hello
  
  I'm trying to move the windows pulling it with the mouse, but is not
- possible. I need to use the righ click of the mouse on the border and
- select "Move"
+ possible. I need to use the righ click of the mouse on the upper border
+ and select "Move"

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

Title:
  I can't move the windows on Ubuntu 21.04

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

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1916881] Re: Thunderbird unable to access external pgp keys

2021-03-09 Thread Olivier Tilloy
According to the release notes (https://www.thunderbird.net/en-
US/thunderbird/78.8.1/releasenotes/), the 78.8.1 update has several GPG-
related bug fixes, I wonder if those would help.

I am currently working on the update for all supported Ubuntu releases.

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

Title:
  Thunderbird unable to access external pgp keys

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading thunderbird to the latest ubuntu package
  1:78.7.1+build1-0ubuntu0.20.04.1 (and thus throwing out enigmail) I
  cannot use encryption anymore.

  The 78 version of thunderbird has replaced enigmail with its own
  implementation of PGP encryption, and it is still able to decrypt
  messages accessing the pgp agent.

  But the access to gnupg seems to be completely broken. The keyring is
  completely empty, it does not now any public key and needs to learn
  from scratch.

  Even then, I cannot reply to an encrypted mail with an encrypted
  (unsigned!) answer, since thunderbird cannot find my key.

  To enable PGP functions at all, thunderbird requires to enter the settings 
and configure which pgp key belongs to the mailbox account, and offers to
   
  * create a new key
  * import from a file
  * use an external gnupg key (e.g. on smartcard)

  Since I'm using a smartcard key, I've chosen the third option and
  entered the key id, which is accepted, but not listed in the key
  manager. Even if my own key is technically not required to send an
  encrypted list (except for making the Sent folder readable for
  myself), I can't send the message. Thunderbird raises an error message
  because the configured key cannot be found on the keyring.

  Which is technically correct, since the import from gnupg didn't work,
  both with the smartcard and a regular soft key.

  Obviously, thunderbird has some problem accessing the gnupg keys.

  My first guess was that apparmor causes problems, but that's not the
  case. I've used strace to verify that thunderbird has access to
  ~/.gnupg , and indeed it can and does read the files, therefore I'm
  not sure, why it actually doesn't work.

  Nevertheless, it doesn't work and I currently can't send encrypted
  messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 1759 F pulseaudio
   /dev/snd/pcmC0D0p:   hadmut 1759 F...m pulseaudio
  BuildID: 20210203182138
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  Date: Thu Feb 25 12:22:09 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-06-12 (257 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-42a938ea-d29a-4ad6-95cd-df43e0210213
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-42a938ea-d29a-4ad6-95cd-df43e0210213
   bp-cd2c713c-37b0-4b60-9b06-b94130210125
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2021-03-09 Thread Sebastien Bacher
** No longer affects: network-manager (Ubuntu Groovy)

** No longer affects: network-manager (Ubuntu Focal)

** No longer affects: network-manager (Ubuntu Bionic)

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in network-manager source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  systemd-resolved emits a disturbingly large amount of NXDOMAIN log
  messages that do not actually indicate any real problem

  [test case]

  see original description, or look at any log from any recent Ubuntu
  system, or search google for endless complaints about NXDOMAIN
  messages logged by Ubuntu

  [regression potential]

  any regression would likely be isolated to systemd-resolved handling
  of a NXDOMAIN response from its upstream nameserver, including
  possibly failing to resolve a hostname or delays in resolving
  hostnames

  [scope]

  this is needed for all releases; the patch is not upstream, but
  carried by Ubuntu

  [original description]

  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes

  Now make the hostname absolute with the trailing dot above and run:
     systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

2021-03-09 Thread Sebastien Bacher
** Changed in: geoclue-2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: geoclue-2.0 (Ubuntu Groovy)
   Status: Triaged => Won't Fix

-- 
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:
  Fix Committed
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 1918273] Re: I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Leo
I'm not sure what the package associated with the problem might be, but
it's something related to window management.

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

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

Title:
  I can't move the windows on Ubuntu 21.04

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the border and
  select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918273/+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 1918273] [NEW] I can't move the windows on Ubuntu 21.04

2021-03-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello

I'm trying to move the windows pulling it with the mouse, but is not
possible. I need to use the righ click of the mouse on the border and
select "Move"

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


** Tags: bot-comment move window
-- 
I can't move the windows on Ubuntu 21.04
https://bugs.launchpad.net/bugs/1918273
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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


[Desktop-packages] [Bug 1918269] Re: moving tabs to a new window no longer works.

2021-03-09 Thread rew
Nope Not fixed But I think the behaviour changed from last time
I tested it (my machine crashed inbetween... Grrr..).

So now, when I drag a tab it shows as a new window, and stays "attached
to the mouse" until it snaps into an existing window when I come close
to the tab bar in the other window.

Then on the next click anywhere on any of my screens, the tab that
was just parked as a tab in a window is suddenly detached and placed
randomly (i.e. as far as I can see: Not where I released the drag
nor where I clicked).

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

Title:
  moving tabs to a new window no longer works.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Somewhat similar to bug #999632, but different and quite new.

  When I have a tab that I want to move to a NEW window, I used to be
  able to drag the tab and then when releasing it near the tab bar of
  another chromium window, it would snap into that window's tab list.
  This still works.

  But when I release the tab NOT near the tab bar of another window, it
  used to create a new window. This is convenient: I have multiple
  screens so when I decide I need to view this tab alongside something
  in my existing window, I drag the tab to create a new window on the
  other screen.

  Workaround: create a new window first then drag the tab there. But
  this "used to work". It is not necessary to do it like this. I liked
  it the old way.

  This changed somewhere in the last week. The behaviour swapped on my home 
computer yesterday (but it was still normal at work) and today I had to restart 
chromium (because all new tabs were reporting "aw snap!", reported in another 
bugreport) and now it's here too. Package: chromium
  Versions: 

  Reverse Depends: 
chromium-bsu,chromium 0.9.14
x2gothinclient-minidesktop,chromium
webext-ublock-origin,chromium
webext-proxy-switcher,chromium
webext-privacy-badger,chromium
webext-bulk-media-downloader,chromium
webext-browserpass,chromium
polymake,chromium
gnome-core,chromium
djview-plugin,chromium
cinnamon-desktop-environment,chromium
chromium-tt-rss-notifier,chromium
chromium-lwn4chrome,chromium
chromium-bsu,chromium 0.9.14
chrome-gnome-shell,chromium
chrome-gnome-shell,chromium
  Dependencies: 
  Provides: 
  Reverse Provides: 

  
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  
  % apt-cache policy chromium
  chromium:
Installed: (none)
Candidate: (none)
Version table:
  % []

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918269/+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 1918269] Re: moving tabs to a new window no longer works.

2021-03-09 Thread rew
% chromium --version
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 89.0.4389.82 snap
%

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

Title:
  moving tabs to a new window no longer works.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Somewhat similar to bug #999632, but different and quite new.

  When I have a tab that I want to move to a NEW window, I used to be
  able to drag the tab and then when releasing it near the tab bar of
  another chromium window, it would snap into that window's tab list.
  This still works.

  But when I release the tab NOT near the tab bar of another window, it
  used to create a new window. This is convenient: I have multiple
  screens so when I decide I need to view this tab alongside something
  in my existing window, I drag the tab to create a new window on the
  other screen.

  Workaround: create a new window first then drag the tab there. But
  this "used to work". It is not necessary to do it like this. I liked
  it the old way.

  This changed somewhere in the last week. The behaviour swapped on my home 
computer yesterday (but it was still normal at work) and today I had to restart 
chromium (because all new tabs were reporting "aw snap!", reported in another 
bugreport) and now it's here too. Package: chromium
  Versions: 

  Reverse Depends: 
chromium-bsu,chromium 0.9.14
x2gothinclient-minidesktop,chromium
webext-ublock-origin,chromium
webext-proxy-switcher,chromium
webext-privacy-badger,chromium
webext-bulk-media-downloader,chromium
webext-browserpass,chromium
polymake,chromium
gnome-core,chromium
djview-plugin,chromium
cinnamon-desktop-environment,chromium
chromium-tt-rss-notifier,chromium
chromium-lwn4chrome,chromium
chromium-bsu,chromium 0.9.14
chrome-gnome-shell,chromium
chrome-gnome-shell,chromium
  Dependencies: 
  Provides: 
  Reverse Provides: 

  
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  
  % apt-cache policy chromium
  chromium:
Installed: (none)
Candidate: (none)
Version table:
  % []

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918269/+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 1908921] Re: No system tray detected by hp-systray

2021-03-09 Thread Paolo Pustorino
I'm also affected.
Sleep workaround works, but I choose to downgrade to the working version.

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

Title:
  No system tray detected by hp-systray

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  I have hp-systray -x as one of the startup applications when I login.
  This app exits with the following error:

  HPLIP Status service
  No system tray detected on this system.
  Unable to start, exiting.

  Once logged in, if I start hp-systray -x from the terminal it works
  fine. This started happening after updating gnome-shell-extension-
  appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 11:41:23 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-10 (1655 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+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 1917300] Re: updated firefox 86.0 (64 bit)

2021-03-09 Thread Olivier Tilloy
Oh, that's unfortunate, apport-collect tries to open the default
browser, which is firefox, so the debugging info collection process is
halted.

Can you install another web browser (if you don't have one already), and
temporarily change the default browser to that new one, then run again
"apport-collect 1917300" ?

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1918269] Re: moving tabs to a new window no longer works.

2021-03-09 Thread Olivier Tilloy
What version of chromium are you running? (please share the output of
"chromium --version")

I suspect this might be a regression in the 89.0.4389.72 stable update,
that was subsequently fixed in 89.0.4389.82, and is now available in the
stable channel of the snap store.

If your version is 89.0.4389.72, please close all chromium windows,
upgrade to 89.0.4389.82 (run "sudo snap refresh") and let us know
whether the latest update helps. Thanks!

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  moving tabs to a new window no longer works.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Somewhat similar to bug #999632, but different and quite new.

  When I have a tab that I want to move to a NEW window, I used to be
  able to drag the tab and then when releasing it near the tab bar of
  another chromium window, it would snap into that window's tab list.
  This still works.

  But when I release the tab NOT near the tab bar of another window, it
  used to create a new window. This is convenient: I have multiple
  screens so when I decide I need to view this tab alongside something
  in my existing window, I drag the tab to create a new window on the
  other screen.

  Workaround: create a new window first then drag the tab there. But
  this "used to work". It is not necessary to do it like this. I liked
  it the old way.

  This changed somewhere in the last week. The behaviour swapped on my home 
computer yesterday (but it was still normal at work) and today I had to restart 
chromium (because all new tabs were reporting "aw snap!", reported in another 
bugreport) and now it's here too. Package: chromium
  Versions: 

  Reverse Depends: 
chromium-bsu,chromium 0.9.14
x2gothinclient-minidesktop,chromium
webext-ublock-origin,chromium
webext-proxy-switcher,chromium
webext-privacy-badger,chromium
webext-bulk-media-downloader,chromium
webext-browserpass,chromium
polymake,chromium
gnome-core,chromium
djview-plugin,chromium
cinnamon-desktop-environment,chromium
chromium-tt-rss-notifier,chromium
chromium-lwn4chrome,chromium
chromium-bsu,chromium 0.9.14
chrome-gnome-shell,chromium
chrome-gnome-shell,chromium
  Dependencies: 
  Provides: 
  Reverse Provides: 

  
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  
  % apt-cache policy chromium
  chromium:
Installed: (none)
Candidate: (none)
Version table:
  % []

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918269/+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 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re

2021-03-09 Thread Bug Watch Updater
Launchpad has imported 22 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=140700.

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


On 2021-02-27T13:53:05+00:00 PascalC wrote:

Description:
calc crash often observed upon exit after having saved a modified sheet

Steps to Reproduce:
1.open an existing sheet
2.modify some cells
3.press SAVE icon
4.close the window with X on the top right corner

Actual Results:
calc crash

Expected Results:
nothing should crash


Reproducible: Sometimes


User Profile Reset: No


Additional Info:
Version: 7.0.3.1
Build ID: 00(Build:1)
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Ubuntu package version: 1:7.0.3-0ubuntu0.20.10.1
Calc: threaded

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/15


On 2021-02-27T13:53:33+00:00 PascalC wrote:

profile has been reset and bug is still here

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/16


On 2021-02-27T13:54:26+00:00 PascalC wrote:

Created attachment 170116
debug trace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/17


On 2021-02-27T14:14:19+00:00 Miguelangelrv wrote:


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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/18


On 2021-02-27T15:39:57+00:00 julien2412 wrote:

Mariosv: why do you consider this as a dup?
Indeed debug trace seems pure qt5 pb whereas tdf#140677 can be reproduced in 
gtk3 (I don't reproduce tdf#104677 myself).
I've updated my local repo and it's building right now but I'll give a try to 
this one with kf5 rendering.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/19


On 2021-02-27T17:09:23+00:00 julien2412 wrote:

Pascal: on pc Debian x86-64 with master sources updated today + kf5
rendering, I don't reproduce this.

Do you reproduce this with a brand new file?
Do you reproduce this with an existing file which just contains "test" in A1?

Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?
If you still reproduce this, could you try this:
- open terminal/console
- export SAL_USE_VCLPLUGIN=gen
- launch Calc and give a new try
?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/20


On 2021-02-27T19:38:28+00:00 Miguelangelrv wrote:

Too much similarity, but only a supposition on my side.

You can know better than me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/21


On 2021-02-27T19:51:25+00:00 julien2412 wrote:

I don't reproduce this with kf5 rendering too.
I can't help here=>uncc myself.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/22


On 2021-02-27T20:58:35+00:00 PascalC wrote:

well since I have installed dbg packages to complete symbol resolution in 
backtrace, I cannot reproduce the crash anymore...  
putting in standby until I can.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/23


On 2021-02-28T09:05:52+00:00 Telesto wrote:

Adding bug 137139 to see also

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/24


On 2021-03-01T08:29:58+00:00 PascalC wrote:

Created attachment 170140
same crash but with writer

I had 3 crash with writer closing a modified saved doc this morning, one of 
which is the same as the one I send yesterday with closing calc.
The 2 other crashes are identical to each other but not the same as the one 
here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897784/comments/25


On 2021-03-01T10:16:42+00:00 Michael Weghorn wrote:

Does that happen with specific documents only? Can you share one and try
to give more hints on how to potentially reproduce more reliably?

While 

[Desktop-packages] [Bug 1918256] Re: cups wrong default driver on Epson SX420W in ubuntu-mate 20.04

2021-03-09 Thread Daniel Manrique
** Project changed: canonical-identity-provider => cups (Ubuntu)

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

Title:
  cups wrong default driver on Epson SX420W in ubuntu-mate 20.04

Status in cups package in Ubuntu:
  New

Bug description:
  Problem:
Wrong driver gets installed by default called "Epson-Stylus-SX420". 
  Symptoms:
Driver prints images incorrectly though text is ok(b/w) or fails(color 
mode).
CMY color displacement by a row or two rows depending on color(colors 
printed
sequentially instead of correct position)
  Wrong Driver: STP01724.PPD
  Wrong Driver Version: 5.3.3

  Corrections to get proper printing:

  epson-inkjet-printer-escpr/now 1.7.5-1lsb3.2 amd64

Now install printer and it is reported as "EPSON-Epson-Stylus-SX420W".
  Driver: ESCPR.PPD
  Driver Version: 1.1

  
  $ lsusb
  ..
  Bus 001 Device 002: ID 04b8:0864 Seiko Epson Corp. ME OFFICE 560W Series
  ..
  $ lsusb -v
  Bus 001 Device 002: ID 04b8:0864 Seiko Epson Corp. ME OFFICE 560W Series
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x04b8 Seiko Epson Corp.
idProduct  0x0864 ME OFFICE 560W Series
bcdDevice1.00
iManufacturer   1 EPSON
iProduct2 EPSON Epson Stylus SX420W Series
iSerial 3 4D4343503032353032
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   0x004e
  bNumInterfaces  3
  bConfigurationValue 1
  iConfiguration  4 USB2.0 MFP(Hi-Speed)
  bmAttributes 0xc0
Self Powered
  MaxPower2mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass   255 Vendor Specific Class
bInterfaceSubClass255 Vendor Specific Subclass
bInterfaceProtocol255 Vendor Specific Protocol
iInterface  5 EPSON Scanner
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x01  EP 1 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber1
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass 7 Printer
bInterfaceSubClass  1 Printer
bInterfaceProtocol  2 Bidirectional
iInterface  6 USB2.0 Printer
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x04  EP 4 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x85  EP 5 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber2
bAlternateSetting   0
bNumEndpoints   2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass  6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface  7 USB2.0 Mass Storage
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x07  EP 7 OUT
  bmAttributes2
Transfer TypeBulk

[Desktop-packages] [Bug 1918256] [NEW] cups wrong default driver on Epson SX420W in ubuntu-mate 20.04

2021-03-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Problem:
  Wrong driver gets installed by default called "Epson-Stylus-SX420". 
Symptoms:
  Driver prints images incorrectly though text is ok(b/w) or fails(color mode).
  CMY color displacement by a row or two rows depending on color(colors printed
  sequentially instead of correct position)
Wrong Driver: STP01724.PPD
Wrong Driver Version: 5.3.3

Corrections to get proper printing:

epson-inkjet-printer-escpr/now 1.7.5-1lsb3.2 amd64

  Now install printer and it is reported as "EPSON-Epson-Stylus-SX420W".
Driver: ESCPR.PPD
Driver Version: 1.1


$ lsusb
..
Bus 001 Device 002: ID 04b8:0864 Seiko Epson Corp. ME OFFICE 560W Series
..
$ lsusb -v
Bus 001 Device 002: ID 04b8:0864 Seiko Epson Corp. ME OFFICE 560W Series
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x04b8 Seiko Epson Corp.
  idProduct  0x0864 ME OFFICE 560W Series
  bcdDevice1.00
  iManufacturer   1 EPSON
  iProduct2 EPSON Epson Stylus SX420W Series
  iSerial 3 4D4343503032353032
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x004e
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  4 USB2.0 MFP(Hi-Speed)
bmAttributes 0xc0
  Self Powered
MaxPower2mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  5 EPSON Scanner
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 7 Printer
  bInterfaceSubClass  1 Printer
  bInterfaceProtocol  2 Bidirectional
  iInterface  6 USB2.0 Printer
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04  EP 4 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber2
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  7 USB2.0 Mass Storage
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x07  EP 7 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88  EP 8 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Device Qualifier (for other device speed):

[Desktop-packages] [Bug 1915336] Re: mozilla thunderbird update ubuntu 20.04 LTS

2021-03-09 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1895643 ***
https://bugs.launchpad.net/bugs/1895643

** This bug has been marked a duplicate of bug 1895643
   Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

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

Title:
  mozilla thunderbird update ubuntu 20.04 LTS

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  mozilla thunderbird not update long time linux ubuntu 20.04 LTS 
  last mozilla thunderbird update last year summer now is not
  update mozilla thunderbird 78 update linux soon please

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1915336/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen

2021-03-09 Thread Marc Deslauriers
I can reproduce this on Ubuntu 20.04 and Ubuntu 20.10

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

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

Title:
  Characters from dead keys shown in plan view in password field on
  login screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  2) apt-cache policy gdm3
  gdm3:
Installed: 3.38.1-2ubuntu1.1
Candidate: 3.38.1-2ubuntu1.1
Version table:
   *** 3.38.1-2ubuntu1.1 500
  500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.38.1-2ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

  3) I expect all characters, even those from dead keys, to be hidden
  the same ways as other characters

  4) When using dead keys to add accents to letters on the password
  prompt on the login screen, before the letter the dead key is intended
  for is typed, the special characters from the dead keys are displayed
  in plain sight, instead of being obscured by dots as other letters and
  characters are.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gdm3 3.38.1-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 12:51:19 2021
  InstallationDate: Installed on 2018-11-26 (770 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+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 1915279] Re: about

2021-03-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  about

Status in xorg package in Ubuntu:
  New

Bug description:
  all chromium server have heavy issue in render

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 10 20:16:29 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
  InstallationDate: Installed on 2021-02-04 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. OptiPlex 760
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=136e728b-139d-400a-b333-620a8490dd1d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.release: 16.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0M858N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd08/06/2013:br16.0:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915279/+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 1915336] Re: mozilla thunderbird update ubuntu 20.04 LTS

2021-03-09 Thread Marc Deslauriers
** Package changed: linux (Ubuntu) => thunderbird (Ubuntu)

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

** Information type changed from Private Security to Public Security

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

Title:
  mozilla thunderbird update ubuntu 20.04 LTS

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  mozilla thunderbird not update long time linux ubuntu 20.04 LTS 
  last mozilla thunderbird update last year summer now is not
  update mozilla thunderbird 78 update linux soon please

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1915336/+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 1916712] Re: Mozilla Firefox Multiple Vulnerabilities

2021-03-09 Thread Marc Deslauriers
** Information type changed from Private Security to Public Security

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

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

Title:
  Mozilla Firefox Multiple Vulnerabilities

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  CVE Numbers

  CVE‑2021‑23969  , CVE‑2021‑23968
   ,
  CVE‑2021‑23978  , CVE‑2021‑23974
   ,
  CVE‑2021‑23971  , CVE‑2021‑23979
  

  Multiple vulnerabilities have been reported in Mozilla Firefox, which
  can be exploited by malicious people to conduct cross-site scripting
  attacks, disclose sensitive information, and compromise a vulnerable
  system.

  1

  Some errors related to memory safety can be exploited to corrupt
  memory.

  2

  Some further errors related to memory safety can be exploited to
  corrupt memory.

  3

  An error when handling redirects when submitting a Content Security
  Policy violation report can be exploited to disclose the URL of a
  redirect.

  4

  An error when blocking frame navigation when submitting a Content
  Security Policy violation report can be exploited to disclose the URL
  of a redirect.

  5

  An error when handling noscript elements can be exploited to bypass
  HTML Sanitizers and subsquently conduct cross-site scripting attacks.

  6

  An error when processing redirects with a conflicting Referrer-Policy
  can be exploited to disclose the URL to the destination of the
  redirect.

  The vulnerabilities are reported in versions prior to 86.

  
  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  Mozilla Firefox 85.x

  
  Solution

  Upgrade to version 86.

  
  Please take appropriate measures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916712/+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 1918269] [NEW] moving tabs to a new window no longer works.

2021-03-09 Thread rew
Public bug reported:

Somewhat similar to bug #999632, but different and quite new.

When I have a tab that I want to move to a NEW window, I used to be able
to drag the tab and then when releasing it near the tab bar of another
chromium window, it would snap into that window's tab list. This still
works.

But when I release the tab NOT near the tab bar of another window, it
used to create a new window. This is convenient: I have multiple screens
so when I decide I need to view this tab alongside something in my
existing window, I drag the tab to create a new window on the other
screen.

Workaround: create a new window first then drag the tab there. But this
"used to work". It is not necessary to do it like this. I liked it the
old way.

This changed somewhere in the last week. The behaviour swapped on my home 
computer yesterday (but it was still normal at work) and today I had to restart 
chromium (because all new tabs were reporting "aw snap!", reported in another 
bugreport) and now it's here too. Package: chromium
Versions: 

Reverse Depends: 
  chromium-bsu,chromium 0.9.14
  x2gothinclient-minidesktop,chromium
  webext-ublock-origin,chromium
  webext-proxy-switcher,chromium
  webext-privacy-badger,chromium
  webext-bulk-media-downloader,chromium
  webext-browserpass,chromium
  polymake,chromium
  gnome-core,chromium
  djview-plugin,chromium
  cinnamon-desktop-environment,chromium
  chromium-tt-rss-notifier,chromium
  chromium-lwn4chrome,chromium
  chromium-bsu,chromium 0.9.14
  chrome-gnome-shell,chromium
  chrome-gnome-shell,chromium
Dependencies: 
Provides: 
Reverse Provides: 


Description:Ubuntu 20.04.2 LTS
Release:20.04


% apt-cache policy chromium
chromium:
  Installed: (none)
  Candidate: (none)
  Version table:
% []

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

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

Title:
  moving tabs to a new window no longer works.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Somewhat similar to bug #999632, but different and quite new.

  When I have a tab that I want to move to a NEW window, I used to be
  able to drag the tab and then when releasing it near the tab bar of
  another chromium window, it would snap into that window's tab list.
  This still works.

  But when I release the tab NOT near the tab bar of another window, it
  used to create a new window. This is convenient: I have multiple
  screens so when I decide I need to view this tab alongside something
  in my existing window, I drag the tab to create a new window on the
  other screen.

  Workaround: create a new window first then drag the tab there. But
  this "used to work". It is not necessary to do it like this. I liked
  it the old way.

  This changed somewhere in the last week. The behaviour swapped on my home 
computer yesterday (but it was still normal at work) and today I had to restart 
chromium (because all new tabs were reporting "aw snap!", reported in another 
bugreport) and now it's here too. Package: chromium
  Versions: 

  Reverse Depends: 
chromium-bsu,chromium 0.9.14
x2gothinclient-minidesktop,chromium
webext-ublock-origin,chromium
webext-proxy-switcher,chromium
webext-privacy-badger,chromium
webext-bulk-media-downloader,chromium
webext-browserpass,chromium
polymake,chromium
gnome-core,chromium
djview-plugin,chromium
cinnamon-desktop-environment,chromium
chromium-tt-rss-notifier,chromium
chromium-lwn4chrome,chromium
chromium-bsu,chromium 0.9.14
chrome-gnome-shell,chromium
chrome-gnome-shell,chromium
  Dependencies: 
  Provides: 
  Reverse Provides: 

  
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  
  % apt-cache policy chromium
  chromium:
Installed: (none)
Candidate: (none)
Version table:
  % []

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918269/+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 1917204] Re: high Resolution is not getting

2021-03-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  high Resolution is not getting

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not getting my Monitor supporting resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 28 14:40:41 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1019:7df5]
  InstallationDate: Installed on 2021-01-20 (38 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS H61H2-MV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=UUID=671d72b0-98f0-468f-a72f-910d30b2051a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-MV
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/13/2014:br4.6:svnECS:pnH61H2-MV:pvr1.0:rvnECS:rnH61H2-MV:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H61H2-MV
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1917204/+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 1917225] Re: [MS-14Y1, Realtek ALC269VB, Black Headphone Out, Right] Background noise or low volume

2021-03-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [MS-14Y1, Realtek ALC269VB, Black Headphone Out, Right] Background
  noise or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound has become cut at once and the quality become low or the os
  become hanged and then low quality bug happen. two or three times per
  day.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asal   2994 F pulseaudio
asal   6769 F alsamixer
   /dev/snd/pcmC0D0c:   asal   2994 F...m pulseaudio
   /dev/snd/pcmC0D0p:   asal   2994 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 28 19:23:17 2021
  InstallationDate: Installed on 2020-09-16 (164 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: High background noise, or volume is too low
  Title: [MS-14Y1, Realtek ALC269VB, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14Y1IMS.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: MS-14Y1
  dmi.board.vendor: Micro-Star INT'L CO., LTD.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Micro-Star INT'L CO., LTD.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14Y1IMS.209:bd09/09/2011:br4.6:svnMicro-StarINT'LCO.,LTD.:pnMS-14Y1:pvr1.0:rvnMicro-StarINT'LCO.,LTD.:rnMS-14Y1:rvr1.0:cvnMicro-StarINT'LCO.,LTD.:ct9:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: MS-14Y1
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star INT'L CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1917225/+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 1917801] Re: Multi monitor bug opening windows (not responsive to input in the location it is drawn)

2021-03-09 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

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

Title:
  Multi monitor bug opening windows (not responsive to input in the
  location it is drawn)

Status in mutter package in Ubuntu:
  New

Bug description:
  When i open a window like Spotify or GitKracken, that should open in
  my second monitor (because i always use them there), Ubuntu draws it
  in my main monitor, but, if i try to move it, resize or press an area
  of the window, it selects the window that is under it (like if the
  windows does not logically exist there). If i click on the window
  title bar, it sometimes appears on the second monitor and is resized
  (also if i press the minimize button or others). Sometimes the window
  is not responding until i do not minimize it from the dock and re-
  maximize it. Once it does that everything works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  4 20:18:29 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.39, 5.8.0-43-generic, x86_64: installed
   nvidia, 460.39, 5.8.0-44-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2021-01-17 (46 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Desktop-packages] [Bug 1918224] Re: caps lock delay on ubuntu

2021-03-09 Thread Colin Watson
** Project changed: launchpad => xorg-server (Ubuntu)

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

Title:
  caps lock delay on ubuntu

Status in xorg-server package in Ubuntu:
  New

Bug description:
  this bug has been around for ages and no one has fixed it until today,
  it has been ages since I last used Ubuntu and I have tried to use it
  now, on my new Laptop but I'm encountering the same issue so mostly it
  isn't a hardware issue, so I decided to look into it and realized that
  I'm not the only one encountering this issue

  https://forums.linuxmint.com/viewtopic.php?t=267964
  
https://www.reddit.com/r/Ubuntu/comments/9lo5if/is_there_a_solution_for_caps_lock_delay_yet/
  https://github.com/hexvalid/Linux-CapsLock-Delay-Fixer

  I understand that there is an issue with xorgserver and the developers
  there has not accepted or commited the patches yet

  hope this can be really look into cause to tell someone to use Shift
  does not make sense you are forcing someone to do it, I have been
  using caps lock my whole life

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1918224/+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 1918224] [NEW] caps lock delay on ubuntu

2021-03-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

this bug has been around for ages and no one has fixed it until today,
it has been ages since I last used Ubuntu and I have tried to use it
now, on my new Laptop but I'm encountering the same issue so mostly it
isn't a hardware issue, so I decided to look into it and realized that
I'm not the only one encountering this issue

https://forums.linuxmint.com/viewtopic.php?t=267964
https://www.reddit.com/r/Ubuntu/comments/9lo5if/is_there_a_solution_for_caps_lock_delay_yet/
https://github.com/hexvalid/Linux-CapsLock-Delay-Fixer

I understand that there is an issue with xorgserver and the developers
there has not accepted or commited the patches yet

hope this can be really look into cause to tell someone to use Shift
does not make sense you are forcing someone to do it, I have been using
caps lock my whole life

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

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

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


[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2021-03-09 Thread Julien Saggiotto
Same problem here, with a Acer Swift 314-42. 
Hdajackretask does not work for me. 
:/

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1918249] Re: Icons in folder pane don't scale for hidpi, breaks rendering

2021-03-09 Thread ts
OK, re-enabling userChrome.css according to

http://forums.mozillazine.org/viewtopic.php?f=30=3064381=6

and creating a userChrome.css as follows:


/* Thunderbird userChrome.css */

@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul;);

#folderTree > treechildren::-moz-tree-image {
  width: 10px !important;
  height: 10px !important;
}

#folderTree > treechildren::-moz-tree-cell-text {
  padding-bottom: 1px !important;
}


provides a temporary solution!

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

Title:
  Icons in folder pane don't scale for hidpi, breaks rendering

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Ever since the update to 78.7.1 (64-bit) Thunderbird attempts at
  showing icons next to the folders in the folder pane. Hidpi settings
  cause the font to scale, but the icons don't scale (at the same level?
  at all?). This entirely breaks the rendering of the folder pane on
  high resolution displays with downscaled fonts.

  Screenshot attached.

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

  
  $ apt-cache policy thunderbird
  thunderbird:
Installed: 1:78.7.1+build1-0ubuntu0.20.04.1
Candidate: 1:78.7.1+build1-0ubuntu0.20.04.1
Version table:
   *** 1:78.7.1+build1-0ubuntu0.20.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:68.10.0+build1-0ubuntu0.20.04.1 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:68.7.0+build1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  I expect Thunderbird to show a neat folder pane

  It doesn't, rendering is broken due to failed scaling of the icons

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210203182138
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Mar  9 07:58:06 2021
  InstallationDate: Installed on 2020-03-26 (347 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200322)
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1918249/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-09 Thread Riccardo Battistini
I agree that is a problem with Network Manager, maybe also affects
different vpn besides OpenVPN; this same problem is present in CentOS 7
and 8.

Which config do you need?

I tried to draw the network scheme to help understanding my setup.

Regards
Riccardo

** Attachment added: "Network Scheme"
   
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1917887/+attachment/5475052/+files/Network%20Manager%20OpenVPN%20nested%20connections%20fail%20to%20setup%20routes%20correctly%20-%20bug%201917887%20-%201.jpg

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1917887/+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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-09 Thread Andreas Schultz
for wireshark the problem can be worked around with this:

diff -up wireshark-3.4.3/debian/rules.orig wireshark-3.4.3/debian/rules
--- wireshark-3.4.3/debian/rules.orig   2021-03-09 10:09:58.184967210 +0100
+++ wireshark-3.4.3/debian/rules2021-03-09 09:58:39.497405512 +0100
@@ -31,7 +31,8 @@ override_dh_auto_configure-indep:
 
 override_dh_auto_configure-arch:
echo "#define VCSVERSION \"$(GIT_VERSION)\"" > version.h
-   dh_auto_configure
+   dh_auto_configure -- 
-DCMAKE_CXX_FLAGS="-DGLIB_VERSION_MIN_REQUIRED=0x024200" \
+
-DCMAKE_C_FLAGS="-DGLIB_VERSION_MIN_REQUIRED=0x024200"
 
 override_dh_auto_build-arch:
# regenerate ASN.1 dissectors

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged
Status in wireshark package in Ubuntu:
  Confirmed

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It 

[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged
Status in wireshark package in Ubuntu:
  Confirmed

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It must be something else.

  The difference were ~340 packages I was upgrading them to spot what broke it.
  I eventually found glib 2.66 -> 2.67 to break it.

  libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
  libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

  Old:
  /*
   * We can 

[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: open-vm-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged
Status in wireshark package in Ubuntu:
  Confirmed

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It must be something else.

  The difference were ~340 packages I was upgrading them to spot what broke it.
  I eventually found glib 2.66 -> 2.67 to break it.

  libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
  libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

  Old:
  /*
   * We 

[Desktop-packages] [Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

2021-03-09 Thread Daniel van Vugt
Confirmed the clicking on a window problem is fixed by adding in
4d54c3c556d753c0b981406937948895141dc1d4.

But I can't figure out exactly what is causing the Alt-Tab issue. It
looks like it's somewhere in this massive commit:

  https://salsa.debian.org/gnome-
team/mutter/-/commit/c4e7908058149f2efbe4c8d306d14da51cc80f5f

I recommend reverting that because it's obvious now we can't maintain it
or vouch for its stability. Even if I bisected the series file, making
changes to such a large patch series is not something I would endorse or
want to support. Instead I recommend dropping debian/patches/input-
thread-backports/*


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

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

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

Title:
  Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

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


  1   2   >