[Desktop-packages] [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

2020-06-18 Thread Timo Aaltonen
Hello Per-Inge, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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: gnome-shell (Ubuntu Focal)
   Status: Fix Released => 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1877760

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Started the computer from suspend. Started Gmail from Dash to Panel.

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 18:30:48 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu 
(%rdi),%ymm1
   PC (0x7fe9fdcc3e41) ok
   source "(%rdi)" (0xf0250) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
   g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1881973] Re: Update to 3.36.3 and SRU it

2020-06-18 Thread Timo Aaltonen
Hello Marco, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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: gnome-shell (Ubuntu Focal)
   Status: New => 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1881973

Title:
  Update to 3.36.3 and SRU it

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.3

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

   - All desktop components should be continue running as per systemd unit 
updates
   - extensions updates should work as expected 
   - Do not disturb is preserved

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

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


[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

2020-06-18 Thread Timo Aaltonen
Hello Alfred, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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.

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

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions

2020-06-18 Thread Timo Aaltonen
Hello Jeremy, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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.

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

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

Title:
  Do Not Disturb setting does not persist across login sessions

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

Bug description:
  [ Impact ]

  Selecting do not disturb from settings does not persist across login
  sessions.

  [ Test case ]

  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar

  [ Regresion potential ]

  Togglingg the do not disturb toggle doesn't work anymore

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  gnome-control-center:
    Installed: 1:3.36.1-1ubuntu5
    Candidate: 1:3.36.1-1ubuntu5
    Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  - Do Not Disturb is reset to disabled on each new login

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

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

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


[Desktop-packages] [Bug 1872026] Re: App icon aspect ratio in the panel is broken

2020-06-18 Thread Timo Aaltonen
Hello Mark, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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.

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

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

Title:
  App icon aspect ratio in the panel is broken

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

Bug description:
  [ Impact ]

  The aspect ratio of the icon on the top left of the screen (Activites
  bar?) is broken so it looks taller and thinner than normal.

  See attached screenshot.

  [ Test case ]

  - Run an application such as update-manager
  - The application icon on the top panel should have correct propotions

  [ Regression potential ]

  Icons may have wrong vertical aligment

  -

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:10:09 2020
  InstallationDate: Installed on 2020-01-24 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-04-10 09:03:51.154471
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2020-04-03T20:22:43.358127

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

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


[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

2020-06-18 Thread Timo Aaltonen
Hello Per-Inge, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.3-1ubuntu1~20.04.2 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: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/184

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen] [usually due to
  dash-to-panel]

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled

2020-06-18 Thread Timo Aaltonen
Hello Mario, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.3-0ubuntu0.20.04.1 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: mutter (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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596

Title:
  [Focal regression] On-screen keyboard (OSK) does not appear on touch
  under Xorg on convertible laptops in tablet mode when physical
  keyboard disabled

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  OSK doesn't appear in X11 when disabling physical keyboard

  [ Test case ]

  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this
 disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as
 gnome-shell > Activities > Search:
 - The OSK appear
  4. Swipe from bottom of screen in order to summon OSK on demand:
 - occurred on Ubuntu 18.04 through 19.10)

  [ Regression potential ]

  The OSK shows when not needed in setup with no touch-screen or with
  touch screen but when not required.

  ---

  Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
  Related upstream bugs:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1242

  [Note: Please someone add a bug watch for
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
  for the other and then Launchpad somehow did not let me again]

  Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS 
9575 2-in-1:
  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as  
gnome-shell > Activities > Search
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text
  4. Swipe from bottom of screen in order to summon OSK on demand:
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text 
fields of foreign toolkits that are expected not to trigger the OSK 
automatically)

  Note that the EXPECTED RESULT still happens under Wayland in 20.04.
  Only the Xorg session is affected by the issue described in this bug.

  Also note that Accessibility was NOT necessary to be enabled in 19.10
  and before. (When enabling it in 20.04, the OSK does appear under
  Xorg, but this should not be necessary)

  (On Wayland there is a different changed behavior with the OSK not appearing 
in the device's laptop mode, i.e. with the physical keyboard enabled. This 
seems intended and a different issue as per 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )

  This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
  I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this 
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
  It probably also worked with 19.04 and possibly 18.10, but I ran mostly 
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)

  Other hardware reported to reproduce the issue (and in part are said
  to have been working in 19.10 and before, down to 18.04) include:

  In bug #1866556;
  Lenovo ThinkPad L390 Yoga

[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout

2020-06-18 Thread Bug Watch Updater
** Changed in: ecryptfs-utils (Debian)
   Status: Unknown => New

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

Title:
  encrypted home-directory is not unmounted on logout

Status in GNOME Session Shutdown:
  New
Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Debian:
  New

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions

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


[Desktop-packages] [Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed

2020-06-18 Thread Timo Aaltonen
Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.3-0ubuntu0.20.04.1 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: mutter (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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1877075

Title:
  gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost'' failed

Status in Mutter:
  Unknown
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 Released

Bug description:
  [Impact]

  This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's
  duplicated across multiple problem reports according to locale:

  https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c
  https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b
  https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7
  https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0

  [Test Case]

  None known. The plan is to just continue monitoring crash reports.
  Still, we are confident this is the fix because:

   * The offending source code in libx11 tells us it is :) and
   * The crash only started in Ubuntu with gnome-shell 3.34, which is the
     exact release in which XInitThreads was removed from mutter.

  [Regression Potential]

  Low. We add a single function call that tells libX11 to enable thread
  safety. This same function call as one we had in bionic, cosmic and
  disco.

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

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


[Desktop-packages] [Bug 1881971] Re: Update to 3.36.3 and SRU it

2020-06-18 Thread Timo Aaltonen
Hello Marco, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.3-0ubuntu0.20.04.1 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: mutter (Ubuntu Focal)
   Status: New => 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1881971

Title:
  Update to 3.36.3 and SRU it

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.3

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been updates to the clipboard and X11 updates in
  screencasting and touch-interaction, so ensure there are no problems
  with those.

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

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


[Desktop-packages] [Bug 1879234] Re: Clicking Activities does nothing - screen appears to freeze

2020-06-18 Thread Abir
this is also resolve because as you say 'try super key to solve this '
it work thanks

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

Title:
  Clicking Activities does nothing - screen appears to freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Clicking Activities does nothing - screen appears to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout

2020-06-18 Thread Klaus Bielke
See for workaround:

 - https://wiki.ubuntuusers.de/ecryptfs/Einrichten/#Problembehebung

 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854#107

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

Title:
  encrypted home-directory is not unmounted on logout

Status in GNOME Session Shutdown:
  New
Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Debian:
  Unknown

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions

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


[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout

2020-06-18 Thread Klaus Bielke
** Bug watch added: Debian Bug tracker #765854
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854

** Also affects: ecryptfs-utils (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854
   Importance: Unknown
   Status: Unknown

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

Title:
  encrypted home-directory is not unmounted on logout

Status in GNOME Session Shutdown:
  New
Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Debian:
  Unknown

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions

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


[Desktop-packages] [Bug 1870926] Re: rygel / mx-extract freezes Ubuntu 20.04

2020-06-18 Thread Launchpad Bug Tracker
[Expired for rygel (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  rygel / mx-extract freezes Ubuntu 20.04

Status in rygel package in Ubuntu:
  Expired

Bug description:
  Hi, I installed Ubuntu 20.04 (Beta) on a new partition. At first,
  everything worked okay. Then I did my standard scripts after a fresh
  install like creating users, installing apps (like sambe, ...) etc.
  Then, after a while the whole desktops freezes. But the computer disc
  LED is on, so I do not reset the "crashed" thing. I notice that every
  once in a while (every few minutes) the computer proceeds for a split
  second. After many many minutes it is back to "normal" just to
  "freeze" again after a few seconds/minutes.

  I managed to open a terminal to identify the process: it is "mx-
  extract". This is a process of the package "rygel" which is something
  like UPNP Server. I wonder if this process is somehow scanning my
  whole 2 TB data to somehow look for files to UPnP to the net???

  Anyway: i had to uninstell rygel

 sudo apt remove rygel

  to get this problem "solved" (... worked around).

  This is a major bug in Ubuntu 20.04 (Beta) that "freezes" the whole
  computer!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rygel (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 15:37:10 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-04-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: rygel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself

2020-06-18 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1306
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1306

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

Title:
  Wayland windows does not redraw itself

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  I'm not sure, if it is not a bug of certain Wayland applications.

  Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications,
  namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves
  unless I change their size, or switch to another window or overview.
  For example, audacity does not redraw current position marker, and I
  need to click with a mouse, or resize the window to see it. Firefox
  sometimes just freeze, until I click or until I resize its window, or
  I switch to overview.

  What kind of trace shoud I perform to obtain more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 17:27:24 2020
  InstallationDate: Installed on 2019-11-16 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago)

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

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


[Desktop-packages] [Bug 1883718] Re: zoom in/out problem

2020-06-18 Thread Abir
Yes sir #15 you said small problem with my keyboard I am also think now
because sticky keys already trun of.

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1883718] Re: zoom in/out problem

2020-06-18 Thread Daniel van Vugt
It's also possible there's no problem with the keyboard hardware and you
just have the "Sticky Keys" feature turned on by accident. To turn that
off you will need to follow the instructions mentioned above, or shown
in the attached pictured.

** Attachment added: "sticky.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1883718/+attachment/5385173/+files/sticky.jpg

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1883718] Re: zoom in/out problem

2020-06-18 Thread Daniel van Vugt
Great! It sounds like there's a small problem with your keyboard so that
might need replacing. Unless you can remove the keycaps and clean under
them.

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

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1883718] Re: zoom in/out problem

2020-06-18 Thread Abir
thanks , this problem again happen today than i trying to solve it and press 
the control key .after 
that find it solve ,thanks a lot sir.

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

Title:
  zoom in/out problem

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  zoom in/out problem ,mouse scroll not work ,i seen all type of
  application same problem like chromium,fireffox,files all software
  same kind of problem ,please solve it .also send a video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 19:58:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1884049] Re: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable

2020-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405

Thanks for the bug report.

The attachment 'ShellJournal.txt' seems to show this is a duplicate of
bug 1880405. But also, we find most high CPU issues are caused by
unsupported gnome-shell extensions and you have a few:

  'impatie...@gfxmonk.net',
  'TaskBar@zpydr',
  'bettervol...@tudmotu.com'

so please try disabling those via gnome-shell-extension-prefs.


** Tags added: performance

** This bug has been marked a duplicate of bug 1880405
   High CPU and journal flooded with: JS ERROR: TypeError: null has no 
properties  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

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

Title:
  gnome-shell is taking more and more CPU over time, UI becomes slowly
  unusable

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm a relatively heavy desktop user, having multiple browsers running
  at any given time, lots of terminal windows, etc.However, my
  browsers don't use a lot of CPU as most of the tabs are suspended at
  any given moment.

  On a regular basis, over time, my desktop becomes less and less
  usable.  It starts with becoming noticeably slower, laggy, and
  eventually absolutely requiring a reboot since it becomes totally
  unusable.

  At the same time my my system load is low, and remains low, while
  gnome-shell appears only to take more and more CPU. I often see it
  using 30, 50, 90, and sometimes 100% CPU, while the rest is idle.

  It reaches the point where terminals don't easily

  The only "fix" is rebooting, or restarting X.

  I must admit that I've been seeing this on my laptop for years now,
  and there is no improvement in sight even though I upgrade Ubuntu to
  the next version every time an update is out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 18 11:53:00 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago)

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

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


[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

2020-06-18 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  High CPU and journal flooded with: JS ERROR: TypeError: null has no
  properties
  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

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

Bug description:
  O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I 
did face these problems. The sometimes I have to wait 10 seconds to see if a 
window reacts or not. It is hard to use. 
Installiert:   3.36.1-5ubuntu2
Installationskandidat: 3.36.2-1ubuntu1~20.04.1
Versionstabelle:
   3.36.2-1ubuntu1~20.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 3.36.1-5ubuntu2 100
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun May 24 15:43:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago)

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

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


[Desktop-packages] [Bug 1873725] Re: Folder under applications menu doesn't show text below last line of icons.

2020-06-18 Thread Daniel van Vugt
Fixed upstream. Though the upstream fix involves a major redesign so
that's not a fix that's useful to focal, only groovy.


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

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

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

Title:
  Folder under applications menu doesn't show text below last line of
  icons.

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

Bug description:
  Under the applications menu the "Utilities" folder does not show the
  last line of text below the icons. If you launch one of the
  applications on the last line ie terminal then it will reveal the text
  below the icon.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  nautilus:
Installed: 1:3.36.1.1-1ubuntu2
Candidate: 1:3.36.1.1-1ubuntu2
Version table:
   *** 1:3.36.1.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 22:46:39 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created

2020-06-18 Thread Nathan Griffin
Patrick Wu,

I am experiencing the same issue with the installation of WSL 2 and
bionic on Win10. I recently updated everything. This could be unrelated,
but how do you know when it is fixed?

https://www.screencast.com/t/hqSkdKpypO9o


** Attachment added: "Errors received after starting Ubuntu Terminal"
   
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+attachment/5385167/+files/2020-06-18_2005.png

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

Title:
  wsl-integration.sh shows error when .cache/ can't be created

Status in wslu package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * When $HOME/.cache can't be created an error is shown:
 mkdir: cannot create directory ‘//.cache’: Permission denied

  [Test Case]
   * TODO

  [Regression Potential]
   * TODO
  [Other Info]

  Originally reported to:
  https://github.com/wslutilities/wslu/issues/101

  In addition to suppressing the error message it would probably be also
  useful to disable the detection by default for system users.

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

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


[Desktop-packages] [Bug 1884126] Re: Trying to add google account fails with AUTH-1140

2020-06-18 Thread Joe Barnett
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
   Importance: Unknown
   Status: Unknown

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+subscriptions

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


[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep

2020-06-18 Thread Joel Lisenby
With the latest updates installed for Ubuntu 20.04 I am no longer seeing
this double mouse cursor issue after two sleeps in a row. Will report
back if the issue returns.

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

Title:
  Extra frozen / stuck mouse cursor after auto screen lock / sleep

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Expected:

  After my computer had gone to sleep and I log in I should see only a
  single active mouse cursor.

  
  What happened instead:

  After my computer had gone to sleep and I logged in I noticed a second
  frozen/stuck mouse cursor was on screen and was rendered in one place
  over any active application windows.

  

  I recently upgraded to 20.04 from 19.10 but the same issue was
  occurring in 19.10 as well.

  Logging out completely then logging back in again removed the extra
  frozen cursor.

  

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy mutter
  mutter:
Installed: 3.36.1-3ubuntu3
Candidate: 3.36.1-3ubuntu3
Version table:
   *** 3.36.1-3ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 19:53:03 2020
  InstallationDate: Installed on 2019-03-09 (415 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)

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

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


[Desktop-packages] [Bug 1878921] Re: USB 3 NVMe SSD dongle doesn't flip

2020-06-18 Thread Sebastien Bacher
did you get the error before the updated pacakge? why do you mean by
having similar services?

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

Title:
  USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  I have a AM8180 AMicro adapter. It is an adapter for an M.2 SSD NVMe
  disk to USB 3. It works fine on Windows, but on Ubuntu, when I plug it
  in, the drive shows for a second then disappears. If I try to do fdisk
  or gparted, it seems to lock something and I can't shutdown the laptop
  (it is stuck on the Disk Management Unmounting step.

  My info:
  1) Release:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2) Package version:
  usb-modeswitch:
Installed: 2.5.2+repack0-2ubuntu3
Candidate: 2.5.2+repack0-2ubuntu3
Version table:
   *** 2.5.2+repack0-2ubuntu3 500
  500 http://th.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What I expect to happen:
  I expect the drive to stay mounted

  4) What happened instead:
  The disk is mounted then immediately unmount. Before I create the partitions 
in Windows, nothing mounted but the disk briefly appeared in the Disk Manager.

  
  Attached is my (filtered) syslog when I plug to the USB-C (notice the message 
advising to tell the developers about the model. Maybe it's just vendor info 
missing).

  I have modified 2 flags in /etc/usb_modeswitch.conf:
  - DisableSwitching=0 changed to 1
  - #SetStorageDelay=4 changed to un-commented
  then restarted. That didn't help.

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

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


[Desktop-packages] [Bug 1884142] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()

2020-06-18 Thread Apport retracing service
*** This bug is a duplicate of bug 1858320 ***
https://bugs.launchpad.net/bugs/1858320

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1858320, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385101/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385103/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385107/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385108/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385109/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385110/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1884142/+attachment/5385111/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1858320

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory crashed with signal 5 in g_thread_new()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it crashed in the background.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 18 21:41:28 2020
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
  InstallationDate: Installed on 2017-10-13 (979 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_data_factory_spawn_subprocess_backend () at 
/usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10
   () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1884142/+subscriptions

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


[Desktop-packages] [Bug 1884056] Re: Package Homepage links to a 404 error

2020-06-18 Thread Sebastien Bacher
** Changed in: wslu (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Package Homepage links to a 404 error

Status in wslu package in Ubuntu:
  New

Bug description:
  Package info provides

  Homepage: https://wslu.patrickwu.space/

  It leads to a Github Pages 404 error.

  Appears to affect all versions.

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread Sebastien Bacher
** Changed in: rhythmbox (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1884101] Re: jackdbus produces high cpu load

2020-06-18 Thread Erich Eickmeyer
Please install the version of jackd2 in the Ubuntu Studio Backports PPA
found at https://launchpad.net/~ubuntustudio-
ppa/+archive/ubuntu/backports/+packages to see if that fixes the
problem. If it does, then I might be able to set-up a Stable Release
Update (SRU) to get it into 20.04.

Setting as "Incomplete" for now simply to ensure a response happens in
the next 60 days or this bug expires since this is critical to
troubleshooting this problem.

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

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

Title:
  jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu
  load. jackd tends to take all availabl CPU power bringing the system
  to slow down remarkably. Killing jackd and jackdbus frees cpu and
  system load drops from 100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1884101] Re: jackdbus produces high cpu load

2020-06-18 Thread Sebastien Bacher
** Package changed: pulseaudio (Ubuntu) => jackd2 (Ubuntu)

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

Title:
  jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu
  load. jackd tends to take all availabl CPU power bringing the system
  to slow down remarkably. Killing jackd and jackdbus frees cpu and
  system load drops from 100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.

2020-06-18 Thread Andreas Buslehner
@cpg100: did you made an update-initramfs -u  ?

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

Title:
  initramfs unpacking failed: Decoding failed", message appears on boot
  up.

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  OS : Ubuntu 20.04(20200401)

  Problem: "initramfs unpacking failed: Decoding failed", message
  appears on boot up

  solution: 
If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to 
COMPRESS=gzip 
  then the error is fixing .

  Expected solution:
  This but in there from a long time I have seen this from 
Ubuntu 18.04,19.04,19.10
  now in 20.04 So please fix it or change it from lz4 to gzip.
  an early reply is highly appreciated 
  Thank you .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamal  1451 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-da0xxx
  Package: ubuntu-meta
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 5AY34PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1884126] Re: Trying to add google account fails with AUTH-1140

2020-06-18 Thread Sebastien Bacher
Thank you for your bug report, could you report it upstream on
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues ?

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

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

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


[Desktop-packages] [Bug 1883702] Re: [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem

2020-06-18 Thread Paulo Flabiano Smorigo
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/1883702

Title:
  [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  input mic does not work.  It worked after for a day and become muted
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyu3620 F pulseaudio
   /dev/snd/pcmC0D0c:   kyu3620 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyu3620 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 21:35:26 2020
  InstallationDate: Installed on 2020-05-28 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.30
  dmi.board.name: 0693
  dmi.board.vendor: FF40
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.30:bd12/09/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-008001:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P55W-C
  dmi.product.sku: PSPVTU
  dmi.product.version: PSPVTU-008001
  dmi.sys.vendor: TOSHIBA

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

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


[Desktop-packages] [Bug 1884135] [NEW] [LE_WH-1000XM3, playback] Playback problem: BT headset only plays gnome-terminal's bell (Ctrl-G), any media/audio is still output via builtin intel audio

2020-06-18 Thread Bernhard Gabler
Public bug reported:

After today's update, no audio can be played via connected Bluetooth
headset (Sony LE_WH-1000XM3). The sound setting offers internal speakers
or wireless headset, but either way any media (RhythmBox, Web video,
...) plays through the internal speakers.

The notable exception is gnome-console's ping (played as output of a
BELL character, like from hitting the backspace key on an empty bash
command line, or from

  echo -e \\007

which does play through wireless headset (or internal speaker) as set by
the sound setting.


Before today's update, the Bluetooth headset did play audio (yet not 
immediately upon connecting; for though the sound setting had switched to the 
external headset, any sound was still output to via internal speakers. But 
switching once to the internal speakers and back to the BT headset was a viable 
workaround to get sound out to the BT headset.)

>From apt log:
Start-Date: 2020-06-18  17:19:14
Commandline: aptdaemon role='role-commit-packages' sender=':1.315'
Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), 
alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1), bind9-host:amd64 
(1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), dnsutils:amd64 
(1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), initramfs-tools-bin:amd64 
(0.136ubuntu6, 0.136ubuntu6.1), busybox-static:amd64 (1:1.30.1-4ubuntu6, 
1:1.30.1-4ubuntu6.1), bind9-libs:amd64 (1:9.16.1-0ubuntu2.1, 
1:9.16.1-0ubuntu2.2), initramfs-tools-core:amd64 (0.136ubuntu6, 
0.136ubuntu6.1), initramfs-tools:amd64 (0.136ubuntu6, 0.136ubuntu6.1), 
gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1), 
busybox-initramfs:amd64 (1:1.30.1-4ubuntu6, 1:1.30.1-4ubuntu6.1)
Remove: linux-image-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-modules-extra-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-headers-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-modules-5.3.0-55-generic:amd64 (5.3.0-55.49), 
linux-headers-5.3.0-55:amd64 (5.3.0-55.49)
End-Date: 2020-06-18  17:20:14

Could the issue be caused by one of these packages?
  alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1)
  gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bernhard   2078 F pulseaudio
 /dev/snd/pcmC0D0c:   bernhard   2078 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 18 18:42:49 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-12-11 (919 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: LE_WH-1000XM3
Symptom_Type: Only some of outputs are working
Title: [LE_WH-1000XM3, playback] Playback problem
UpgradeStatus: Upgraded to focal on 2020-06-05 (13 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01.
dmi.board.name: Woody_KL
dmi.board.vendor: KBL
dmi.board.version: V1.01.
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01.
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01.:bd09/13/2017:svnAcer:pnSpinSP513-52N:pvrV1.01.:rvnKBL:rnWoody_KL:rvrV1.01.:cvnAcer:ct31:cvrV1.01.:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-52N
dmi.product.sku: 
dmi.product.version: V1.01.
dmi.sys.vendor: Acer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-18T18:32:11.193118

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [LE_WH-1000XM3, playback] Playback problem: BT headset only plays
  gnome-terminal's bell (Ctrl-G), any media/audio is still output via
  builtin intel audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After today's update, no audio can be played via connected Bluetooth
  headset (Sony LE_WH-1000XM3). The sound setting offers internal
  speakers or wireless headset, but either way any media (RhythmBox, Web
  video, ...) plays through the internal speakers.

  The notable exception is gnome-console's ping (played as output of a
  BELL character, like from hitting the backspace key on an empty bash
  command line, or from

echo -e \\007

  which does play through wireless headset (or internal speaker) as set
  by the sound setting.

  
  Before today's update, the Bluetooth headset did play audio (yet not 
immediately upon connecting; for though the sound setting had switched to the 
external headset, any 

[Desktop-packages] [Bug 1884124] [NEW] Text Editor (geditunusable with yaru-dark

2020-06-18 Thread tylerecouture
*** This bug is a duplicate of bug 1857191 ***
https://bugs.launchpad.net/bugs/1857191

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

gedit:
  Installed: 3.36.2-0ubuntu1
  Candidate: 3.36.2-0ubuntu1
  Version table:
 *** 3.36.2-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.1-1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

3) What you expected to happen
gedit/Text Editor to look nice and usable in yaru-dark (Settings > Appearance > 
Dark)

4) What happened instead
Highlighted line is unreadable.  It highlights in white but the text is very 
light gray!  The cursor is almost impossible to see as well.

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

** Attachment added: "gedit in yaru dark theme"
   
https://bugs.launchpad.net/bugs/1884124/+attachment/5385068/+files/Screenshot%20from%202020-06-18%2011-41-09.png

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center
  
  gedit:
-   Installed: 3.36.2-0ubuntu1
-   Candidate: 3.36.2-0ubuntu1
-   Version table:
-  *** 3.36.2-0ubuntu1 500
- 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.36.1-1 500
- 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 3.36.2-0ubuntu1
+   Candidate: 3.36.2-0ubuntu1
+   Version table:
+  *** 3.36.2-0ubuntu1 500
+ 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.36.1-1 500
+ 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  3) What you expected to happen
  gedit/Text Editor to look nice and usable in yaru-dark (Settings > Appearance 
> Dark)
  
  4) What happened instead
- Selected text is unreadable.  It highlights in very light gray but the text 
is white!  The cursor is almost impossible to see as well.
+ Highlighted line is unreadable.  It highlights in white but the text is very 
light gray!  The cursor is almost impossible to see as well.

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

Title:
  Text Editor (geditunusable with yaru-dark

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  gedit:
    Installed: 3.36.2-0ubuntu1
    Candidate: 3.36.2-0ubuntu1
    Version table:
   *** 3.36.2-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.1-1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  gedit/Text Editor to look nice and usable in yaru-dark (Settings > Appearance 
> Dark)

  4) What happened instead
  Highlighted line is unreadable.  It highlights in white but the text is very 
light gray!  The cursor is almost impossible to see as well.

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

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


[Desktop-packages] [Bug 1884126] [NEW] Trying to add google account fails with AUTH-1140

2020-06-18 Thread Joe Barnett
Public bug reported:

Trying to add a google account that redirects to another site for sign
in results in a window with the following error:

{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

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


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

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

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

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


[Desktop-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working

2020-06-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro
  not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Please see 
https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257
 for most background.
  tl;dr:
  - The Rodecaster Pro is a USB audio standard compliant device
  - lsusb sees it, but alsa cannot use it
  - trying the exact same setup with a Scarlett 2i2 USB device works (with some 
caveats, see the mentioned post)

  Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug.
  Alsa info is at 
http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also 
attached.

  nils@blackbox:~/tmp/soundtest$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  nils@blackbox:~/tmp/soundtest$ arecord --list-devices
   List of CAPTURE Hardware Devices 
  card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog 
[ALC887-VD Alt Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  nils  90077 F pulseaudio
   /dev/snd/controlC0:  nils  90077 F pulseaudio
   /dev/snd/controlC1:  nils  90077 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May  9 11:45:20 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-23 (1354 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AudioUsers: pulse
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  nils  90077 F pulseaudio
   /dev/snd/controlC0:  nils  90077 F pulseaudio
   /dev/snd/controlC1:  nils  90077 F pulseaudio
  Symptom_Jack: SPDIF Out, Internal
  Symptom_Type: Sound works for some users but not for others
  Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all 
users
  UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago)
  dmi.bios.date: 10/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5222
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704

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

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


[Desktop-packages] [Bug 1884102] [NEW] package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: el subproceso instalado paquete emacs-gtk script post-installation devolvió el código de salida de

2020-06-18 Thread Jean Paul
Public bug reported:

problem installing emacs from tty1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: emacs-gtk 1:26.3+1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jun 18 18:18:19 2020
ErrorMessage: el subproceso instalado paquete emacs-gtk script 
post-installation devolvió el código de salida de error 1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: emacs
Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: el 
subproceso instalado paquete emacs-gtk script post-installation devolvió el 
código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: el
  subproceso instalado paquete emacs-gtk script post-installation
  devolvió el código de salida de error 1

Status in emacs package in Ubuntu:
  New

Bug description:
  problem installing emacs from tty1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-gtk 1:26.3+1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:18:19 2020
  ErrorMessage: el subproceso instalado paquete emacs-gtk script 
post-installation devolvió el código de salida de error 1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: emacs
  Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: el 
subproceso instalado paquete emacs-gtk script post-installation devolvió el 
código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

2020-06-18 Thread Marcus Urso-Bernick
I'll follow up after work tonight work more specifics

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

Title:
  https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  OS: Pop!_OS 20.04 LTS x86_64 
  Host: XPS 13 9370 
  Kernel: 5.4.0-7634-generic 
  Uptime: 2 hours, 50 mins 
  Packages: 1817 (dpkg), 20 (snap) 
  Shell: bash 5.0.16 
  Resolution: 1920x1080 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Pop 
  Theme: Pop-dark [GTK2/3] 
  Icons: Pop [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  Memory: 3322MiB / 15729MiB 

  Summary(cont) - Attempt to input Google account info into online
  account util and get error--> TLS/SSL support not available; install
  glib-networking.

   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
  Referenced this BUG REPORT

  ##Downloaded Deb build but I'm having an issue applying appropriate
  inputs in the provided documentation. Please help!##

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

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


[Desktop-packages] [Bug 1884101] [NEW] jackdbus produces high cpu load

2020-06-18 Thread Thomas Schweikle
Public bug reported:

if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load.
jackd tends to take all availabl CPU power bringing the system to slow
down remarkably. Killing jackd and jackdbus frees cpu and system load
drops from 100%/per CPU down to ~4% overall.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sct-muc1800 F pulseaudio
 /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
 /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
 /dev/snd/timer:  sct-muc1800 f pulseaudio
CasperMD5CheckResult: skip
Date: Thu Jun 18 18:08:25 2020
InstallationDate: Installed on 2019-09-09 (282 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  jackdbus produces high cpu load

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu
  load. jackd tends to take all availabl CPU power bringing the system
  to slow down remarkably. Killing jackd and jackdbus frees cpu and
  system load drops from 100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

2020-06-18 Thread Marcus Urso-Bernick
Glib-networking is installed I'm getting an error that it's not
installed from the accounts app in settings

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

Title:
  https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  OS: Pop!_OS 20.04 LTS x86_64 
  Host: XPS 13 9370 
  Kernel: 5.4.0-7634-generic 
  Uptime: 2 hours, 50 mins 
  Packages: 1817 (dpkg), 20 (snap) 
  Shell: bash 5.0.16 
  Resolution: 1920x1080 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Pop 
  Theme: Pop-dark [GTK2/3] 
  Icons: Pop [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  Memory: 3322MiB / 15729MiB 

  Summary(cont) - Attempt to input Google account info into online
  account util and get error--> TLS/SSL support not available; install
  glib-networking.

   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
  Referenced this BUG REPORT

  ##Downloaded Deb build but I'm having an issue applying appropriate
  inputs in the provided documentation. Please help!##

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

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


[Desktop-packages] [Bug 1871864] Re: Toggle "Fractional Scaling" does nothing on wayland

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Toggle "Fractional Scaling" does nothing on wayland

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  System: Ubuntu Focal Fossa (Development Branch) 20.04

  Version of "gnome-control-center": 1:3.36.1-1ubuntu4

  In the setting there is option called "Fractional Scaling" but this
  option only works for X11.

  What is the problem:
  Enabling "Fractional Scaling" adds only ['x11-randr-fractional-scaling'] but 
['scale-monitor-framebuffer']

  What it should be:
  Enabling "Fractional Scaling" in the setting adds parameter for both X11 and 
wayland:
  ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 23:43:57 2020
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869288] Re: "Privacy" tab in gnome-control-center is not findable

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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


[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

2020-06-18 Thread You-Sheng Yang
@report, I couldn't find any log here.

@Mark, please file a new bug with `sudo apport-bug linux`, then we'll
have enough logs to investigate.

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

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

Bug description:
  Incorrect wifi drivers detected

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

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


[Desktop-packages] [Bug 1884063] Re: SRU the current 3.36.3 stable update

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SRU the current 3.36.3 stable update

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the GNOME settings still work correctly

  * Regression potential

  Nothing specific to test in this update

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

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


[Desktop-packages] [Bug 1877441] Re: Fingerprint icons during enrollment are selectable

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Fingerprint icons during enrollment are selectable

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Fingerprint enrollment icons are selectable while they should support no 
interaction.
  See picture at 
https://www.reddit.com/r/Ubuntu/comments/g6st9d/2004_comes_with_fingerprint_locks/

  [ Test case ]

  - Start enrolling a finger
  - Clicking or changing focus with tab should not highlight an icon

  [ Regression potential ]

  Print icons are not properly rendered

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

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


[Desktop-packages] [Bug 1877108] Re: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu Dock appears on the display opposite to that indicated on
  Appearance tab

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  I am unable to use ubuntu-bug to raise this report as I have upgraded
  to a new version in -proposed to test bug 1866088. This issue was not
  addressed in that bug fix.

  paul@n1644:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:3.36.2-0ubuntu1
Candidate: 1:3.36.2-0ubuntu1
Version table:
   *** 1:3.36.2-0ubuntu1 100
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I am using a a laptop with an external monitor set up as follows:

  Display 1 is the laptop's built-in monitor
  Display 2 is the external monitor set as being the primary display

  To reproduce:

  1) Go to the Appearance tab
  2) "Show on" will indicate on which display the dock is being shown
  3) In my case it is set to "1. Built in display" but it appears on the second 
or primary display
  4) Change the setting and the dock will move but...
  5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears 
on the built-in display.

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

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


[Desktop-packages] [Bug 1884091] Re: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-06-18 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 sysfsutils in Ubuntu.
https://bugs.launchpad.net/bugs/1884091

Title:
  package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in sysfsutils package in Ubuntu:
  New

Bug description:
  Getting this crash message on boot, not actually experiencing any
  noticeable problems otherwise. Likely just a holdover from upgrading
  16.04 -> 18.04 -> 20.04 over a couple days.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sysfsutils 2.1.0+repack-6
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun 15 10:43:40 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2017-06-27 (1086 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: sysfsutils
  Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-06-15 (2 days ago)

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

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


[Desktop-packages] [Bug 1876891] Re: The fractional scaling toggle applies instantly and not when "Apply" is pressed

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  Do this when in an Xorg/Ubuntu session:

  0. Have fractional scaling disabled and set to 100%
  1. Go to gnome-control-center -> displays
  2. Turn on the fractional scaling toggle
  3. Select 125%
  4. Press apply (the scaling should apply correctly)
  5. Turn off the toggle
  6. Turn the toggle back on

  At 5 and 6, the scaling changes. It shouldn't - this should only
  happen when you press 'Apply'. The toggle needs to not be directly
  connected to GSettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:35:48 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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


[Desktop-packages] [Bug 1876937] Re: Dock location reversed in RTL

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.3-1ubuntu1

---
gnome-control-center (1:3.36.3-1ubuntu1) groovy; urgency=medium

  * New upstream version rebased on Debian (lp: #1884063)

  [ Gunnar Hjalmarsson ]
  * debian/patches/0030-temporarily-revert-alt-char-key.patch:
- Change po/POTFILES.in too, so dh_translations can create
  gnome-control-center-2.0.pot.
  * d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
- Add "privacy" to Keywords in the .desktop file in line with
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/05f3cb67
  (LP: #1869288)

  [ Marco Trevisan (Treviño) ]
  * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Ensure dock position is respected in RTL (LP: #1876937)
- Add proper matching the dock monitor ID (LP: #1877108)
  * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch:
- Improve fractional scaling toggling (LP: #1876891, #1876894)
- Look for proper fractional scaling key in Wayland and X11 (LP: #1871864)
  * d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch:
- Don't make flowbox children selectable (LP: #1877441)

 -- Sebastien Bacher   Thu, 18 Jun 2020 13:44:56
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Dock location reversed in RTL

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  he dock location is horizontally reversed, selecting left puts the
  dock to the right and vice versa.

  Steps to reproduce (Ubuntu 20.04):

  1. Switch to an RTL language of your choice

  2. Open GNOME Settings

  3. Observe the Appearance icon (The default dock location is to the
  right while the icon shows as if it's to the left)

  4. The selection says "Left" (שמאל in Hebrew) yet the dock is aligned
  to the right, selecting the opposite option moves the dock to the left
  although I selected "Right" (ימין in Hebrew).

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

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


[Desktop-packages] [Bug 1884091] [NEW] package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-06-18 Thread Nakor
Public bug reported:

Getting this crash message on boot, not actually experiencing any
noticeable problems otherwise. Likely just a holdover from upgrading
16.04 -> 18.04 -> 20.04 over a couple days.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: sysfsutils 2.1.0+repack-6
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 15 10:43:40 2020
ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
InstallationDate: Installed on 2017-06-27 (1086 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: sysfsutils
Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
UpgradeStatus: Upgraded to focal on 2020-06-15 (2 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in sysfsutils package in Ubuntu:
  New

Bug description:
  Getting this crash message on boot, not actually experiencing any
  noticeable problems otherwise. Likely just a holdover from upgrading
  16.04 -> 18.04 -> 20.04 over a couple days.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sysfsutils 2.1.0+repack-6
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun 15 10:43:40 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2017-06-27 (1086 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: sysfsutils
  Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-06-15 (2 days ago)

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

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


[Desktop-packages] [Bug 1861882] Re: Shift key cancels accented IME input with fcitx

2020-06-18 Thread T.D. Stoneheart
Thanks for the information! I've filed a bug report at Chromium Bugs and
added its link on the description.

** Description changed:

  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and 
chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue)
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1
  
  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.
  
  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.
  
  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).
  
  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 83 (and possibly next versions).
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.
+ * This issue has been reported in Chromium Bugs, at: 
https://bugs.chromium.org/p/chromium/issues/detail?id=1086946

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

Title:
  Shift key cancels accented IME input with fcitx

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and 
chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue)
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1

  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.

  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.

  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).

  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 83 (and possibly next versions).
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.
  * This issue has been reported in Chromium Bugs, at: 
https://bugs.chromium.org/p/chromium/issues/detail?id=1086946

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread crvi
I tried this with 3 audio sinks ( local audio sink + network host 1
audio sink + network host 2 audio sink ), and I don't see any random
sink selection. Rhythmbox always plays in the default selected sink.
This is on Ubuntu 20.04 and Debian Unstable.

Can you gather more info ?

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1874717] Re: devices cannot connect to ubuntu hotspot

2020-06-18 Thread Shubh Pathak
Similar issue I am also facing. When the hotspot is ON with internet
connection connected to 20.04 , ssid is not visible on devices to
connect to the newtork

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer

2020-06-18 Thread and003
I believe this bug affects me, also, but I have a different printer, and
I get a different message. I have posted my issue here:

https://bugs.launchpad.net/hplip/+bug/1884084

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-18 Thread Michael Heller
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

@David is it sustainable in your case and works also after a power down of the 
machine?
unfortunately, in my case it only works when I first boot ubuntu 19.10 via live 
iso and reboot into installed ubuntu 20.04.
however, after a complete power down my 20.04 fails back to not working hsp/hfp 
mode.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-18 Thread Corey McCandless
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

I am experiencing this issue as well, but don't know how to extract the
19.10 default.pa from the .deb package. Can someone who has successfully
applied this solution please post which lines they changed/added?

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues

2020-06-18 Thread Roman Odaisky
This way each application has to be specifically modified to use
$SNAP_USER_COMMON instead of $HOME? Why not let the applications keep
using $HOME but add an option to snapcraft.yaml that would specify what
exactly to set $HOME to, with options like “real home”, “versioned snap
directory”, “common snap directory”? (So none of the REALHOME=$(getent
passwd $(id -u) | cut -d ':' -f 6) nonsense.)

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

Title:
  snap refresh while command is running may cause issues

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  In testing a desktop snap that saves state in $HOME on close, I
  noticed that if I snap refresh the snap while the command is running
  that it will try to save its state to the previous snap version's data
  directory. For the snap I was testing (a browser), this resulted in a
  very poor user experience (the browser on restart complained about an
  improper shutdown).

  What is happening is that:
  1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something 
like /home/user/snap/foo/x1. The security policy correctly allows writes to 
SNAP_USER_DATA
  2. on snap refresh to 'x2', the security policy for the snap is updated for 
the running process such that /home/user/snap/foo/x1 is readonly and 
/home/user/snap/foo/x2 is read/write
  3. the command in '1's environment is not changed and HOME (as well as 
SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path
  4. the command tries to shutdown gracefully and save state to the 'x1' HOME 
and security policy blocks it

  Snappy's design for rollbacks relies on the previous SNAP_DATA and
  SNAP_USER_DATA directories not being writable and IMHO we should not
  change the policy to make other snap version's data dirs writable.

  The design of the snappy state engine ensures (among other things)
  that there is only ever one security policy in place for the snap. In
  snappy 15.04 this problem was (intentionally) avoided because we used
  snap security policy that was versioned such that the new policy would
  not apply until the next app invocation.

  Gustavo and Zygmunt, you both advocated strongly for only one version
  of the policy on disk and loaded in the kernel and I recall bringing
  up this type of bug as a counter-argument, and if IIRC for daemons we
  said that snapd could simply restart them (makes perfect sense). Have
  you thought of the mechanism for restarting non-daemons?

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread zdohnal
Hi Till,

the plugin has a script inside itself, which calls 'python' binary - we
have 'python' file as a symlink to 'python3' in Fedora, but Ubuntu seems
to do not have a such binary or symlink.

Seems like a bug for Ubuntu Python team, but it is still a different
issue than this one is, turning off plugin requirement for most devices.

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

-- 
Mailing list: https://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 1880728] Re: [amdgpu] Gnome Shell freeze

2020-06-18 Thread David Landis Jr
Crashed again overnight.  No response from mouse, keyboard, or power
button.  Hard rebooted.  Dont see any new error links.  I have reinstalled
TeamViewer and disabled dash to dock to see if that does anything
different.

On Wed, Jun 17, 2020 at 9:50 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> Oh those are much better links, thanks. There you have:
>
> Bug 1877075: A fix for 20.04 is on the way (you will need libmutter
> version 3.36.3).
>
> Bug 1843982: A fix for 20.04 was released to updates yesterday.
>
> Bug 1878775: Not sure but maybe fixed with bug 1843982 yesterday?
>
> But that doesn't help us to choose a single issue for this bug to be
> about. I guess this bug doesn't need to stay open unless we can identify
> some new issue that doesn't already have a bug ID. Please continue
> reporting your crashes here so we can find some pattern.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   [amdgpu] Gnome Shell freeze
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell/+bug/1880728/+subscriptions
>

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

Title:
  [amdgpu] Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  was logged in through team viewer and got kicked out.  when i was able
  to physically access the machine the screens were on, but was not able
  to move the mouse or interact with the 

[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread zdohnal
Hi Chris,

I beg to differ - this issue has nothing to do with python 2 -> python 3
move. Plugins are binary blobs, not python scripts and installation
scripts shipped with them are python 3 compatible.

It is about HPLIP upstream changed the 'plugin' and 'plugin-reason'
entries in models.dat to '0' for most devices which needed it before.

It results into problems described above in certain situations.

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

2020-06-18 Thread Tony Espy
** Changed in: network-manager (Ubuntu)
 Assignee: Tony Espy (awe) => (unassigned)

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

Title:
  [phone] Does not auto-switch to available, known WiFi

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread Till Kamppeter
The bug report has an upstream task, so the HPLIP developers at HP
should be aware.

Seems that the main (free software) part of HPLIP which comes packaged
with the Linux distributions has no problem with Python 3 but the
proprietary plugin which one has to install separately for certain
devices requires Python 2. Newer distro versions, especially also Ubuntu
20.04 LTS have dropped Python 2 completely in favor of Python 3, as
nowadays practically all important free software projects work with
Python 3.

To the HPLIP developers at HP, can you make sure that the plugin works
also on systems with only Python 3 and no Python 2 installed? On Ubuntu
20.04 LTS and many other newer Linux distributions Python 2 got removed.

In many cases, especially on printers which need the plug-in only for
scanning one can go a driverless way without HPLIP or anything
proprietary needed.

If you run the utility

driverless

on the command line and an entry corresponding to your printer gets
listed, it should work driverless. Also if system-config-printer lists
your device under the discovered network printers (independent whether
it is connected by USB or network, the driverless printing/scanning
framework emulates a network printer if the device is connected to USB)
with an entry with "driverless" under the connection types, you can do
driverless printing.

SANE frontends like simple-scan should list your printer, too. Make sure
to select an entry which contains "eSCL".

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

-- 
Mailing list: https://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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

2020-06-18 Thread Dean Henrichsmeyer
I don't use nightlight and disabling bolt didn't help. As I think it's
notification related, I'm going to turn on do not disturb this evening and
see what happens.

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

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread Chris York
The  issue which is affecting all flavours of Ubuntu 20.04LTS and HPLIP is 
already known. In short the move from python 2 to python 3 in 20.04 renders 
HPLIP all but useless as the scanning features required by HP MFP`s require the 
plug-in which cannot be installed because the python 2 dependencies cannot be 
resolved.
I am sure the HP developers are aware of this due to past reporting, we can 
only await for the fix to arrive

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1861882] Re: Shift key cancels accented IME input with fcitx

2020-06-18 Thread Olivier Tilloy
If this also affects Google Chrome, then an upstream bug should be filed
at https://bugs.chromium.org/p/chromium/issues/entry (please share the
link to the bug here once filed).

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

Title:
  Shift key cancels accented IME input with fcitx

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and 
chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue)
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1

  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.

  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.

  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).

  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 83 (and possibly next versions).
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.

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

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


[Desktop-packages] [Bug 1884063] Re: SRU the current 3.36.3 stable update

2020-06-18 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  SRU the current 3.36.3 stable update

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the GNOME settings still work correctly

  * Regression potential

  Nothing specific to test in this update

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread Saroumane
Thanks for the help.

The workaround for paprefs did work for me.

Regarding rhythmbox :
I tried the gst-launch command line test a few times : it always outputs sound 
to my default sink, no problem here.

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1861882] Re: Shift key cancels accented IME input with fcitx

2020-06-18 Thread T.D. Stoneheart
** Description changed:

  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
- * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64 and 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64 also reproduce this issue)
+ * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and 
chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue)
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1
  
  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.
  
  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.
  
  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).
  
  Remarks:
- * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 81 (and possibly next versions).
+ * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 83 (and possibly next versions).
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.

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

Title:
  Shift key cancels accented IME input with fcitx

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Prerequisites:
  * Ubuntu Bionic or Zorin OS 15
  * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: 
chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, 
chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and 
chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue)
  * fcitx=1:4.2.9.6-1
  * fcitx-unikey=0.2.4-1.1

  Steps:
  * Launch fcitx and chromium-browser.
  * Focus input to a text box (e.g. omnibox, F12 console).
  * Trigger fcitx IME with UniKey.
  * Type a character sequence that produces a Vietnamese character (e.g. "aws" 
(without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl 
or Spacebar, which will commit the word.
  * Press either Shift key.

  Expected result:
  * Nothing happens, or the typed character should not change, at the very 
least.

  Actual result:
  * Typed word reverts back to "aws". The underline on the word still retains, 
meaning that the word is not yet committed. This issue is a real nuisance when 
typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark 
right after the word).

  Remarks:
  * This issue does not happen on any other programs, only happens on Chromium 
and Google Chrome, versions 79 to 83 (and possibly next versions).
  * Using fcitx-mozc, after typing a Japanese word, the Shift key does not 
change the character.
  * This issue, more or less, is similar to bug #1859294, although not a strict 
duplicate.

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

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


[Desktop-packages] [Bug 1871573] Re: [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found

2020-06-18 Thread Thierry Bossy
Hi,

I have a very similar problem and noticed the following:
My external display is working with Nvidia "Performance Mode" only. In 
"On-demand" mode, I have a black screen that it is not detected in Ubuntu 
system settings, although it is detected by Nvidia X Server Settings.
As if we needed a parameter in On-demand to force HDMI interface to start with 
Nvidia card and not Intel.

Any hints about this?

@Igor, are you sure that you are in "On Demand" mode? I realized that it
automatically switches to "Performance Mode" when we change the driver.

Thanks,
Thierry
---
My config:
- Lenovo Thinkpad P1 Gen2 with Nvidia Quadro T2000
- Secure Boot Disabled
- Nvidia driver 440 activated

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

Title:
  [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found

Status in nvidia-prime package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  I know that you have certified version 18.04 and that 20.04 is not out yet.
  So this is more heads up.

  I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen.
  Currently HDMI does not work.

  How do I know that problem is not in cable or monitor ?
  If I boot to windows, HDMI port works as expected.

  Thank you,
  Igor RACIC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 10:00:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
  InstallationDate: Installed on 2020-04-01 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: LENOVO 20QTCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/nvidia-prime/+bug/1871573/+subscriptions

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


[Desktop-packages] [Bug 1884063] [NEW] SRU the current 3.36.3 stable update

2020-06-18 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

* Test case

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

Check that the GNOME settings still work correctly

* Regression potential

Nothing specific to test in this update

** Affects: gnome-control-center (Ubuntu)
 Importance: Low
 Status: In Progress

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: New => In Progress

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

Title:
  SRU the current 3.36.3 stable update

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the GNOME settings still work correctly

  * Regression potential

  Nothing specific to test in this update

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread crvi
Rhythmbox uses ```autoaudiosink``` gstreamer plugin for outputting
audio, which means Rhythmbox outsources the audio sink selection process
to gstreamer. So, test your bug with the following command first.

```
$ gst-launch-1.0 -v -m audiotestsrc ! audioconvert ! audioresample ! 
autoaudiosink
```

This plays a audio tone on the audio sink "automatically" selected by
gstreamer ```autoaudiosink``` plugin. If the same random device sink
selection happens, the issue could be with ```autoaudiosink``` gstreamer
plugin, and not Rhythmbox.

https://gstreamer.freedesktop.org/documentation/frequently-asked-
questions/using.html?gi-language=c should help.

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread crvi
> Regarding this, all is greyed out in "paprefs" for the new user

See https://gitlab.freedesktop.org/pulseaudio/paprefs/-/issues/7 for
workaround.

** Bug watch added: gitlab.freedesktop.org/pulseaudio/paprefs/-/issues #7
   https://gitlab.freedesktop.org/pulseaudio/paprefs/-/issues/7

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1884056] [NEW] Package Homepage links to a 404 error

2020-06-18 Thread Joshua Lackey
Public bug reported:

Package info provides

Homepage: https://wslu.patrickwu.space/

It leads to a Github Pages 404 error.

Appears to affect all versions.

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


** Tags: bitesize packaging string-fix

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

Title:
  Package Homepage links to a 404 error

Status in wslu package in Ubuntu:
  New

Bug description:
  Package info provides

  Homepage: https://wslu.patrickwu.space/

  It leads to a Github Pages 404 error.

  Appears to affect all versions.

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

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


[Desktop-packages] [Bug 1884049] [NEW] gnome-shell is taking more and more CPU over time, UI becomes slowly unusable

2020-06-18 Thread James Mason
Public bug reported:

I'm a relatively heavy desktop user, having multiple browsers running at
any given time, lots of terminal windows, etc.However, my browsers
don't use a lot of CPU as most of the tabs are suspended at any given
moment.

On a regular basis, over time, my desktop becomes less and less usable.
It starts with becoming noticeably slower, laggy, and eventually
absolutely requiring a reboot since it becomes totally unusable.

At the same time my my system load is low, and remains low, while gnome-
shell appears only to take more and more CPU. I often see it using 30,
50, 90, and sometimes 100% CPU, while the rest is idle.

It reaches the point where terminals don't easily

The only "fix" is rebooting, or restarting X.

I must admit that I've been seeing this on my laptop for years now, and
there is no improvement in sight even though I upgrade Ubuntu to the
next version every time an update is out.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 18 11:53:00 2020
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-shell is taking more and more CPU over time, UI becomes slowly
  unusable

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm a relatively heavy desktop user, having multiple browsers running
  at any given time, lots of terminal windows, etc.However, my
  browsers don't use a lot of CPU as most of the tabs are suspended at
  any given moment.

  On a regular basis, over time, my desktop becomes less and less
  usable.  It starts with becoming noticeably slower, laggy, and
  eventually absolutely requiring a reboot since it becomes totally
  unusable.

  At the same time my my system load is low, and remains low, while
  gnome-shell appears only to take more and more CPU. I often see it
  using 30, 50, 90, and sometimes 100% CPU, while the rest is idle.

  It reaches the point where terminals don't easily

  The only "fix" is rebooting, or restarting X.

  I must admit that I've been seeing this on my laptop for years now,
  and there is no improvement in sight even though I upgrade Ubuntu to
  the next version every time an update is out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 18 11:53:00 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago)

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

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


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

2020-06-18 Thread Jenske
Since having installed Kubuntu 20.04, and having ONLY one printer/scanner 
attached to our home network (Envy 5542), I see multiple printers with names 
with "Envy" in it, but with different extra characters.
It isn't at all clear why it is so difficult to have Ubuntu (and Windows 10 of 
other people on our network) see multiple Envy's. In Windows 10 the printer 
often (but not always) doesn't work, OR only prints one-sided.
In Ubuntu it usually works, but it keeps being confusing: I see at least 3 
"versions" of Envy on the printer-list.

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

Title:
  HP Envy 5530 printer/scanner does not work

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.04 LTS
  see troubleshoot.txt please

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

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

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


[Desktop-packages] [Bug 1876693] Re: [SRU] New stable release 1.64.1

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package gobject-introspection -
1.64.1-1~ubuntu20.04.1

---
gobject-introspection (1.64.1-1~ubuntu20.04.1) focal; urgency=medium

  * Backport new stable release from unstable / groovy. (LP: #1876693)
  * control, gbp.conf: Update for focal

gobject-introspection (1.64.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- d/p/gimarshallingtests-Use-g_assert_cmpfloat_with_epsilon.patch:
  Drop patch, applied upstream

 -- Iain Lane   Mon, 04 May 2020 11:13:36 +0100

** Changed in: gobject-introspection (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] New stable release 1.64.1

Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection source package in Focal:
  Fix Released

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gobject-
  introspection.

  Changes:

  1.64.1 - 2020-04-05
  ---

  * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
  * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  Do this:

- Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
- Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

  [ Regression potential ]

  g-i being broken will break pretty much the whole desktop, but you'd
  know that quite fast.

  The .py changes, if they're wrong or bad, could break the build of r
  -build-deps.

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1848332.

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 2020-06-18T07:54:04+00:00 zdohnal wrote:

The newest version of hplip turns off plugin requirements for most
printers.

If the plugin wasn't installed in the past on the machine, it negatively
affects HPLIP supported queues:

- printing for devices which need a plugin for printing
- scanning for all devices which uses HPLIP

I currently reverted the change, but it should be upstreamed - I
reported it as
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1883898 .

Reply at: https://bugs.launchpad.net/hplip/+bug/1883898/comments/2


** Changed in: hplip (Fedora)
   Status: Unknown => Confirmed

** Changed in: hplip (Fedora)
   Importance: Unknown => Undecided

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

2020-06-18 Thread Amr Ibrahim
Still affecting gnome-software 3.36.0-0ubuntu3 in Focal.

The gnome-software background process consumes 600 MB of memory after 6
days uptime.

** Tags added: focal

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

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


[Desktop-packages] [Bug 1863895] Re: gnome software taking large amount of memory

2020-06-18 Thread Amr Ibrahim
*** This bug is a duplicate of bug 1616332 ***
https://bugs.launchpad.net/bugs/1616332

** This bug is no longer a duplicate of bug 1862087
   High RSS useage for gnome-software background process
** This bug has been marked a duplicate of bug 1616332
   gnome-software using hundreds of MB of memory when not in use

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

Title:
  gnome software taking large amount of memory

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I just notice that gnome-software is taking at the moment 377MB of
  memory, which I consider quite excessive.

  Let me know if I can help more.

  What happened?
  gnome-software using high memory, up to 377MB

  What did I expect?
  gnome-software using at most 280MB

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb 19 15:00:56 2020
  InstallationDate: Installed on 2019-02-03 (380 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.2-0ubuntu2
   gnome-software-plugin-snap3.35.2-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1862087] Re: High RSS useage for gnome-software background process

2020-06-18 Thread Amr Ibrahim
*** This bug is a duplicate of bug 1616332 ***
https://bugs.launchpad.net/bugs/1616332

** This bug has been marked a duplicate of bug 1616332
   gnome-software using hundreds of MB of memory when not in use

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

Title:
  High RSS useage for gnome-software background process

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I've had an uptime of slightly in excess of 2 days, and the gnome-
  software --gapplication-service process is using 700M RSS (3GiB Virt,
  ~50MB SHR).

  This seems excessive. I'll try running under heaptrack to see if
  there's any obvious slow leaks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200129.3826d9e0-1.1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200129.3826d9e0-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 10:49:40 2020
  InstallationDate: Installed on 2019-08-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.2-0ubuntu1
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-20 (16 days ago)

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

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


[Desktop-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback

2020-06-18 Thread Hui Wang
@Seb,

No other pending fixes so far, please upload now.

thx.

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

Title:
  [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag
  when enter Suspend during playback

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Users reported the audio and video is out of sync when entering suspend 
during playback on bionic.

  [Fix]
  The mainline pulseaudio already has the fix for this issue, and the fix is 
already in the eoan, focal and groovy, but it is not in the bionic.

  [Test Case]
  open a online video on the firefox, while it is playing, suspend the system, 
wait for 30 seconds, resume the system, the audio and video is still on the 
sync.

  [Regression Risk]
  Low, these 2 patches are already in the mainline pulseaudio, and already in 
the eoan, focal and groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882042/+subscriptions

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


[Desktop-packages] [Bug 1881756] Re: SRU the current 3.36.3 stable update

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package nautilus - 1:3.36.3-0ubuntu1

---
nautilus (1:3.36.3-0ubuntu1) focal; urgency=medium

  * New stable update (lp: #1881756)
  * debian/patches/gitlab_tracker_fixes.patch:
- removed, fixed slightly differently in the new version

 -- Sebastien Bacher   Tue, 02 Jun 2020 17:03:10
+0200

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

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

Title:
  SRU the current 3.36.3 stable update

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-3-36/NEWS

  
  * Test case

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

  Check that browsing directories and opening, copying, etc files still
  work correctly

  
  * Regression potential

  The update has some fixes to the file search, check that it works
  correctly in the file manager as well as the desktop overview screen

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

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


[Desktop-packages] [Bug 1881756] Update Released

2020-06-18 Thread Łukasz Zemczak
The verification of the Stable Release Update for nautilus has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU the current 3.36.3 stable update

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-3-36/NEWS

  
  * Test case

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

  Check that browsing directories and opening, copying, etc files still
  work correctly

  
  * Regression potential

  The update has some fixes to the file search, check that it works
  correctly in the file manager as well as the desktop overview screen

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread zdohnal
Hi Sebastien,

as I wrote in the previous comment, I filed the issue for Ubuntu for the
future, because it seems new hplip version hasn't arrived yet.

I'm able to reproduce the issue with my MFD device - HP LaserJet m1536 -
with scanning. According of hpaio code, most devices are using a plugin
for scanning.

The basic reproducer is (after you install hplip-3.20.6):

Prereq:
- has an OS which haven't had HP plugin installed before ('hp-plugin' wasn't 
run successfully)
- has a device which needs HP plugin for printing or scanning or for both
- printing and scanning needs to be done via HPLIP, not via any driverless 
solutions (print queue device uri needs to start with 'hp://', scanner device 
uri with 'hpaio://')

Steps to reproduce for printing (if the device needs HP plugin for printing):
1) install the print queue via hp-setup
2) try to print

Actual result:
Printing fails due missing plugin

Expected result:
Printing goes well


Steps to reproduce for scanning (if the device needs HP plugin for scanning):
1) find out your scanner device uri with:
 
$ scanimage -L

2) take hpaio:// uri from previous uri and use scanimage to scan:

$ scanimage -d  >out.pnm

Actual results:
Scanning fails with Device I/O.

Expected results:
Scanning works.

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Unknown

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

-- 
Mailing list: https://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 827695]

2020-06-18 Thread J.R. Messias
Thank you, Dante.
Em 18/06/2020 01:15, "Dante19031999" <827...@bugs.launchpad.net> escreveu:

> (In reply to RGB from comment #50)
> > @dante19031999 this is NOT an OpenGL or OS related problem. Indeed, this
> > problem predates the whole introduction of OpenGL support into the
> suite.
> >
> > Insert a Math object into Writer and type this code
> >
> > left[ stack{1#2#3#4#5#6#7#8} right]
> >
> > you'll immediately see how wrong square brackets are, independently of
> > OpenGL, OS or anything: just print or export to PDF to see that's NOT a
> > display problem, but something deeper.
>
> Sorry. My bad.
>
> --
> You received this bug notification because you are subscribed to
> openoffice.org in Ubuntu.
> https://bugs.launchpad.net/bugs/827695
>
> Title:
>   [Upstream] bug in displaying scalable square brackets in math object
>
> Status in LibreOffice:
>   Confirmed
> Status in OpenOffice:
>   Confirmed
> Status in libreoffice package in Ubuntu:
>   Confirmed
> Status in openoffice.org package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   1) lsb_release -rd
>   Description:  Ubuntu 11.04
>   Release:  11.04
>
>   2) apt-cache policy libreoffice-writer
>   libreoffice-writer:
> Installed: 1:3.3.3-1ubuntu2
> Candidate: 1:3.3.3-1ubuntu2
> Version table:
>*** 1:3.3.3-1ubuntu2 0
>   100 /var/lib/dpkg/status
>1:3.3.2-1ubuntu5 0
>   500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main
> i386 Packages
>1:3.3.2-1ubuntu4 0
>   500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386
> Packages
>
>   3) When is expected to happen in LibreOffice Writer via a terminal:
>   cd ~/Desktop && wget https://bugs.launchpad.net/
> ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_
> example.odt && lowriter --nologo bracket_example.odt
>
>   is the scalable square brackets look as they would in Word. Latex also
>   shows the desired bracket shape as per
>   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+
> bug/827695/+attachment/2287347/+files/latex_brackets.pdf
>   .
>
>   4) What happens instead is the top and bottom part of the bracket look
>   like a square instead of a line pointing inwards towards the equation.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/df-libreoffice/+bug/827695/+subscriptions
>

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

Title:
  [Upstream] bug in displaying scalable square brackets in math object

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) When is expected to happen in LibreOffice Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt
 && lowriter --nologo bracket_example.odt

  is the scalable square brackets look as they would in Word. Latex also
  shows the desired bracket shape as per
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf
  .

  4) What happens instead is the top and bottom part of the bracket look
  like a square instead of a line pointing inwards towards the equation.

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread Saroumane
"In 20.04 :
-> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
-> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem"

In addition, I created a brand new user on my system to reproduce the bug, but 
he could not see RAOP sinks. So I can't see if the bug is happening.
Regarding this, all is greyed out in "paprefs" for the new user and my main 
user (see screenshot attached). The only difference is that "Make discoverable 
Apple AirTunes sound devices available locally" is pre-ticked for my main user, 
and pre-"unticked" for the new user. Maybe I should fill another bug report 
about this.

** Attachment added: "Screenshot from 2020-06-18 10-26-09.png"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+attachment/5384938/+files/Screenshot%20from%202020-06-18%2010-26-09.png

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1883965] Re: gnome-software consumes 600 MB of memory after 6 days uptime

2020-06-18 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1616332 ***
https://bugs.launchpad.net/bugs/1616332

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 1616332, 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 1616332
   gnome-software using hundreds of MB of memory when not in use

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

Title:
  gnome-software consumes 600 MB of memory after 6 days uptime

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The gnome-software background process consumes 600 MB of memory after
  6 days uptime. I think this is a memory leak.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 21:41:49 2020
  InstallationDate: Installed on 2020-04-26 (52 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback

2020-06-18 Thread Sebastien Bacher
@Hui, thanks for the work, do you want that bionic update uploaded now
or should we try to include other pending fixes still there?

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

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

Title:
  [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag
  when enter Suspend during playback

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Users reported the audio and video is out of sync when entering suspend 
during playback on bionic.

  [Fix]
  The mainline pulseaudio already has the fix for this issue, and the fix is 
already in the eoan, focal and groovy, but it is not in the bionic.

  [Test Case]
  open a online video on the firefox, while it is playing, suspend the system, 
wait for 30 seconds, resume the system, the audio and video is still on the 
sync.

  [Regression Risk]
  Low, these 2 patches are already in the mainline pulseaudio, and already in 
the eoan, focal and groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882042/+subscriptions

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


[Desktop-packages] [Bug 1883813] Re: package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26 26.3~1.git96dd01

2020-06-18 Thread Sebastien Bacher
Thank you for your bug report but emacs26 26.3~1.git96dd019-kk1+20.04
isn't an Ubuntu version, you should report the issue to the maintainer
of the ppa you are using

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

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

Title:
  package emacs-gtk (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package
  emacs26 26.3~1.git96dd019-kk1+20.04

Status in emacs package in Ubuntu:
  Invalid

Bug description:
  apt now unusable

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-gtk (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 21:54:18 2020
  ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is 
also in package emacs26 26.3~1.git96dd019-kk1+20.04
  InstallationDate: Installed on 2020-06-10 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: emacs
  Title: package emacs-gtk (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26 
26.3~1.git96dd019-kk1+20.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1883812] Re: package emacs-common (not installed) failed to install/upgrade: trying to overwrite '/usr/include/emacs-module.h', which is also in package emacs26-common 26.3~1.g

2020-06-18 Thread Sebastien Bacher
Thank you for your bug report but emacs26 26.3~1.git96dd019-kk1+20.04
isn't an Ubuntu version, you should report the issue to the maintainer
of the ppa you are using

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

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

Title:
  package emacs-common (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/emacs-module.h', which is also in package
  emacs26-common 26.3~1.git96dd019-kk1+20.04

Status in emacs package in Ubuntu:
  Invalid

Bug description:
  An older version of emacs was among many packages from an --install-
  suggests. I use a version from a PPA that supports vterm. Didn't want
  or expect another version of emacs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 16 21:54:17 2020
  ErrorMessage: trying to overwrite '/usr/include/emacs-module.h', which is 
also in package emacs26-common 26.3~1.git96dd019-kk1+20.04
  InstallationDate: Installed on 2020-06-10 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: emacs
  Title: package emacs-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/emacs-module.h', which is also in package 
emacs26-common 26.3~1.git96dd019-kk1+20.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884008] Re: network manager prefers further away AP when there are multiple APs

2020-06-18 Thread Sebastien Bacher
Thank you for your bug report, could you report this upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  network manager prefers further away AP when there are multiple APs

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm on Ubuntu 20.04. My Wifi set-up has multiple access points
  throughout my home, and they all have the same SSID. It doesn't matter
  where I am in my home though, network manager always connects to one
  particular AP. If I list all the access points with `nmcli dev wifi
  list` I can see that it even picks that one access point if it is the
  farthest away one:

  76:83:C2:BB:34:2A  --  Infra  36405 
Mbit/s  97  ▂▄▆█  WPA2  
  74:83:C2:BB:34:2A  my_access_point Infra  36405 
Mbit/s  95  ▂▄▆█  WPA2  
  74:83:C2:BA:34:2A  my_access_point Infra  1 195 
Mbit/s  94  ▂▄▆█  WPA2  
  76:83:C2:BA:34:2A  --  Infra  1 195 
Mbit/s  94  ▂▄▆█  WPA2  
  B6:FB:E4:45:CA:82  --  Infra  157   405 
Mbit/s  44  ▂▄__  WPA2  
  *   B4:FB:E4:45:CA:82  my_access_point Infra  157   405 
Mbit/s  44  ▂▄__  WPA2  
  B6:FB:E4:44:CA:82  --  Infra  11195 
Mbit/s  42  ▂▄__  WPA2  
  B4:FB:E4:44:CA:82  my_access_point Infra  11195 
Mbit/s  40  ▂▄__  WPA2  

  It is true that if I change the BSSID field in the wifi settings I can
  get it to connect to a particular one, but that is not sufficient. I
  have a laptop, and if I move around my home I need it to connect to
  the closest one, and switching manually to whichever one is closest is
  not practical.

  I can't even create multiple entries for each BSSID in the list of
  networks, if I try many different networks appear with the same name
  and random numbers and I can't even label them.

  This is network manager version 1.22.10-1ubuntu2.1

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

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


[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device

2020-06-18 Thread Sebastien Bacher
Thank you for your bug report, is that specific to rhythmbox or do you
get the same issue in e.g totem?

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

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

Title:
  rhythmbox ignores pulseaudio default sink and outputs sound on random
  device

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  rhythmbox:
    Installed: 3.4.4-1ubuntu2
    Candidate: 3.4.4-1ubuntu2

  What I expect to happen :

  When I launch rhythmbox, I expect it to use the default pulseaudio
  sink. (Which can be defined in pavucontrol or with set-default-sink in
  /etc/pulse/default.pa ).

  What happened instead :

  when I launch rhythmbox, it outputs sound to a random device (in my
  case : either a RAOP sink in my living-room, or another RAOP sink in
  my kitchen. Never my local soundcard)

  If I correct the output sink (with pavucontrol or pactl) the problem
  is fixed... until I quit and restart rhythmbox.

  I did not have this problem with Ubuntu 19.10 / Rhythmbox
  3.4.3-2ubuntu1

  In 20.04 :
  -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem
  -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the 
problem

  I already tried to delete $HOME/.config/pulse with no improvement.

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread Sebastien Bacher
Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Incomplete
Status in hplip package in Fedora:
  Unknown

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-18 Thread zdohnal
** Bug watch added: Red Hat Bugzilla #1848332
   https://bugzilla.redhat.com/show_bug.cgi?id=1848332

** Also affects: hplip (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1848332
   Importance: Unknown
   Status: Unknown

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New
Status in hplip package in Fedora:
  Unknown

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1878603] Re: bbswitch-dkms fails with 5.6 kernels

2020-06-18 Thread Timo Aaltonen
I've tested the build against linux-oem-20.04 (5.6) kernel and it
succeeded. The autopkgtest failure on armhf is irrelevant, since this
package is not even useful on non-x86 and quite frankly shouldn't be
built on !amd64.

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

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

Title:
  bbswitch-dkms fails with 5.6 kernels

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

Bug description:
  * Impact
  the package fails to install when using a 5.6 kernel

  * Test case
  install a 5.6 kernel (linux-oem-20.04) and then install bbswitch-dkms, it 
should build without error

  * Regression potential
  the code is specific to newer kernel versions, it shouldn't create problems 
on existing systems

  

  when i install bumblebee on my labtop in ubuntu20.04LST, tell me that
  "dpkg: 处理软件包 bbswitch-dkms (--configure)时出错:已安装 bbswitch-dkms 软件包
  post-installation 脚本 子进程返回错误状态 10"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bbswitch-dkms 0.8-8
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   dkms:amd64: Install
   bumblebee:amd64: Install
   bbswitch-dkms:amd64: Install
   primus-libs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 14 20:28:26 2020
  ErrorMessage: 已安装 bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  InstallationDate: Installed on 2020-05-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.12-1~16.04
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: bbswitch
  Title: package bbswitch-dkms 0.8-8 failed to install/upgrade: 已安装 
bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1878603] Update Released

2020-06-18 Thread Timo Aaltonen
The verification of the Stable Release Update for bbswitch has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  bbswitch-dkms fails with 5.6 kernels

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

Bug description:
  * Impact
  the package fails to install when using a 5.6 kernel

  * Test case
  install a 5.6 kernel (linux-oem-20.04) and then install bbswitch-dkms, it 
should build without error

  * Regression potential
  the code is specific to newer kernel versions, it shouldn't create problems 
on existing systems

  

  when i install bumblebee on my labtop in ubuntu20.04LST, tell me that
  "dpkg: 处理软件包 bbswitch-dkms (--configure)时出错:已安装 bbswitch-dkms 软件包
  post-installation 脚本 子进程返回错误状态 10"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bbswitch-dkms 0.8-8
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   dkms:amd64: Install
   bumblebee:amd64: Install
   bbswitch-dkms:amd64: Install
   primus-libs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 14 20:28:26 2020
  ErrorMessage: 已安装 bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  InstallationDate: Installed on 2020-05-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.12-1~16.04
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: bbswitch
  Title: package bbswitch-dkms 0.8-8 failed to install/upgrade: 已安装 
bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1878603] Re: bbswitch-dkms fails with 5.6 kernels

2020-06-18 Thread Launchpad Bug Tracker
This bug was fixed in the package bbswitch - 0.8-8ubuntu0.20.04.1

---
bbswitch (0.8-8ubuntu0.20.04.1) focal; urgency=medium

  * debian/patches/0001-Use-proc_ops-structure-for-kernel-version-5.6.0.patch,
debian/patches/fix-clean.patch,
debian/patches/series:
- Add support for Linux 5.6 and fix the clean target to run
  against the kernel version used for building (LP: #1878603)

 -- Alberto Milone   Mon, 18 May 2020
10:47:19 +0200

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

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

Title:
  bbswitch-dkms fails with 5.6 kernels

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

Bug description:
  * Impact
  the package fails to install when using a 5.6 kernel

  * Test case
  install a 5.6 kernel (linux-oem-20.04) and then install bbswitch-dkms, it 
should build without error

  * Regression potential
  the code is specific to newer kernel versions, it shouldn't create problems 
on existing systems

  

  when i install bumblebee on my labtop in ubuntu20.04LST, tell me that
  "dpkg: 处理软件包 bbswitch-dkms (--configure)时出错:已安装 bbswitch-dkms 软件包
  post-installation 脚本 子进程返回错误状态 10"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bbswitch-dkms 0.8-8
  Uname: Linux 5.6.11-050611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   dkms:amd64: Install
   bumblebee:amd64: Install
   bbswitch-dkms:amd64: Install
   primus-libs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 14 20:28:26 2020
  ErrorMessage: 已安装 bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  InstallationDate: Installed on 2020-05-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.12-1~16.04
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: bbswitch
  Title: package bbswitch-dkms 0.8-8 failed to install/upgrade: 已安装 
bbswitch-dkms 软件包 post-installation 脚本 子进程返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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   >