[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu

2020-07-26 Thread Lonnie Lee Best
** Description changed:

  Modern web browsers, by spec, are supposed to support Speech Synthesis.
  Although Firefox does indeed support it, it doesn't work in Kubuntu
- 19.10.
+ 20.04.
  
  On this very page, you should be able to have Firefox read it aloud by
  typing shift-ctrl-I and then entering this code-line into the console
  (and pressing enter):
  
  speechSynthesis.speak(new
  SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
  
  Something shorter, that you could type into the console (for testing)
  is:
  
  speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
  
  You should be able to hear the browser say "testing 1, 2, 3" after doing
- this, but it doesn't working Kubuntu 19.10.
+ this, but it doesn't working Kubuntu 20.04.
  
- This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
- 19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
- 20.04.
+ This works in Ubuntu 20.04 and Windows 10, but doesn't work in Kubuntu
+ 20.04. I'm reporting this in hopes that it gets fixed in a manner where
+ all Kubuntu user can enjoy Speech Synthesis by default.
+ 
+ Currently, to enable Speech Synthesis in Firefox, on Kubuntu 20.04, you
+ have to manually install speech-dispatcher and restart Firefox:
+ 
+ sudo apt install speech-dispatcher
+ 
+ The main purpose of this bug is to request that speech-dispatcher be
+ installed by default because Firefox needs it to be complaint with
+ modern web standards.
+ 
+ Additionally, the Kubuntu team should put this task into their release-
+ checklist, for all future builds of Kubuntu, so that the desktop's
+ speech-dispatcher is always there for the applications that expect its
+ availability.
  
  ProblemType: Bug
- DistroRelease: Ubuntu 19.10
- Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
- ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
- Uname: Linux 5.3.0-40-generic x86_64
+ DistroRelease: Ubuntu 20.04
+ Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
- ApportVersion: 2.20.11-0ubuntu8.5
+ ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  lonnie 1850 F pulseaudio
-  /dev/snd/controlC0:  lonnie 1850 F pulseaudio
- BuildID: 20200217142647
+ BuildID: 20200708170202
+ CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
- Date: Tue Mar 10 13:25:31 2020
+ Date: Sun Jul 26 03:51:21 2020
+ DefaultProfileExtensions: extensions.sqlite corrupt or missing
+ DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
+ DefaultProfileLocales: extensions.sqlite corrupt or missing
+ DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
+ DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
- InstallationDate: Installed on 2020-02-03 (36 days ago)
- InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
- NoProfiles: True
+ InstallationDate: Installed on 2020-04-26 (91 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Profile0Extensions: extensions.sqlite corrupt or missing
+ Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
+ Profile0Locales: extensions.sqlite corrupt or missing
+ Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
+ Profile0PrefSources: prefs.js
+ Profile0Themes: extensions.sqlite corrupt or missing
+ Profiles:
+  Profile1 (Default) - LastVersion=None/None (Out of date)
+  Profile0 - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

** Summary 

[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-07-26 Thread Christian Ehrhardt 
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since 
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also 
affected I'm worried that I might just not hit the same race/trigger by 
accident.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 

Re: [Desktop-packages] [Bug 1888797] Re: missing luahbtex

2020-07-26 Thread Norbert Preining
> I downloaded texlive-bin 2020 and tried to debuild. But I have harfbuzz
> 2.6.4 and there seems to be some mismatch in xetex over whether
> harfbuzz-icu is needed or not. The packaging files imply that all

Can you show the error message?

I will try to set up VM with Ubuntu 20.04, but it shouldn't be a
problem, the same package compiles fine in Debian/testing which should
be close to what 20.04 is shipping.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

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

Title:
  missing luahbtex

Status in texlive-base package in Ubuntu:
  New

Bug description:
  I'm trying to install luahbtex. texlive-luatex implies it includes the
  corresponding luahbtex CTAN package, but the only filename containing
  the characters hb, installed by texlive-luatex is man1/luahbtex.1.gz
  which makes no reference to luahbtex within it.

  Yours, wanting to use luahbtex, please.
  TIA
  PS I tried to report this against texlive-luatex but ubuntu-bug wouldn't let 
me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: texlive-luatex 2019.20200218-1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 24 13:49:10 2020
  InstallationDate: Installed on 2018-04-23 (822 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  PackageArchitecture: all
  SourcePackage: texlive-base
  UpgradeStatus: Upgraded to focal on 2020-05-13 (71 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-04-26T13:30:20.884695

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

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


[Desktop-packages] [Bug 1792300] Re: Speech Synthesis Not Working

2020-07-26 Thread Lonnie Lee Best
I was able to get Speech Synthesis working in Kubuntu via Firefox:
https://askubuntu.com/a/1262310/256054

However, I still can't get it working in Chromium.

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

Title:
  Speech Synthesis Not Working

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04.5, Firefox supports Speech Synthesis by utilizing
  Text-To-Speech voices provided by default from the operating system.

  In Windows 10, both both Firefox and Chrome support Speech Synthesis
  by utilizing Text-To-Speech voices provided by default from the
  operating system.

  However,in Chromium 68 and 69, although the API is supported, Chromium
  cannot speak, because it doesn't seem to know how to load those Text-
  To-Speech voices that Firefox is successfully utilizing.

  Here's what users said at Ask Ubuntu, regarding the issue:
  https://askubuntu.com/questions/761975/

  For example, this page should speak the text is shows:
  http://www.lonniebest.com/CardTrick/

  The link above does not work in Chromium 69 on Ubuntu, however it does
  work in the following browser/os combinations:

  - Firefox (Ubuntu 16.04.5)
  - Chrome (Windows 10)
  - Firefox (Windows 10)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 00:38:53 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Load-Avg-1min: 0.51
  Load-Processes-Running-Percent:   0.1%
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c57c4be3-fe0f-4162-804e-627e28920546 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1888797] Re: missing luahbtex

2020-07-26 Thread mhosken
Thanks. Yes, it would be great if texlive 2020 was in Ubuntu 20.04. But
I doubt it will happen given the feature packages for 20.04 are fixed
now.

I downloaded texlive-bin 2020 and tried to debuild. But I have harfbuzz
2.6.4 and there seems to be some mismatch in xetex over whether
harfbuzz-icu is needed or not. The packaging files imply that all
reference to harfbuzz-icu was removed in 2019, but there is code in
texk/web2c/xetexdir/XeTeXLayoutInterface.cpp that if harfbuzz is greater
than 2.5, then it should use harfbuzz-icu.

I wonder if you can help me out of my confusion. If I get this to build
well, I may be up for putting up a PPA for it.

TIA,
Yours,
Martin

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

Title:
  missing luahbtex

Status in texlive-base package in Ubuntu:
  New

Bug description:
  I'm trying to install luahbtex. texlive-luatex implies it includes the
  corresponding luahbtex CTAN package, but the only filename containing
  the characters hb, installed by texlive-luatex is man1/luahbtex.1.gz
  which makes no reference to luahbtex within it.

  Yours, wanting to use luahbtex, please.
  TIA
  PS I tried to report this against texlive-luatex but ubuntu-bug wouldn't let 
me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: texlive-luatex 2019.20200218-1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 24 13:49:10 2020
  InstallationDate: Installed on 2018-04-23 (822 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  PackageArchitecture: all
  SourcePackage: texlive-base
  UpgradeStatus: Upgraded to focal on 2020-05-13 (71 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-04-26T13:30:20.884695

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

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


[Desktop-packages] [Bug 1889031] [NEW] syslog filling up quickly with entries about org.gnome.Shell.desktop

2020-07-26 Thread elmonitis
Public bug reported:

First time to report what I think might be a bug.

/var/log/syslog is currently 1.2G, and syslog.1 is 717M.

Running

tail -n 500 /var/log/syslog | less

shows multiple instances of lines like the following:

Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: == Stack trace 
for context 0x55671fd02330 ==
Jul 27 12:08:45 elmerm-desktop gnome-shell[1913]: Object St.Icon 
(0x556726741490), has been already deallocated - impossible to access it. This 
might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #0 0x7ffc794c6070 
b   
/home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indi
cators/network.js:164 (0x7f6f1acbc3c8 @ 42)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #1 0x7ffc794c60e0 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #2 0x7ffc794c61b0 
b   self-hosted:918 (0x7f6f706f12b8 @ 394)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #3 0x556720194290 
i   
/home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/exte
nsion.js:225 (0x7f6f1acafef0 @ 64)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #4 0x556720194210 
i   
/home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/exte
nsion.js:214 (0x7f6f1acafe68 @ 65)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #5 0x556720194160 
i   
/home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/extension.js:172
 (0x7f6f1acafcd0 @ 98)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #6 0x5567201940a8 
i   
/home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/extension.js:110
 (0x7f6f1acaf6f8 @ 1421)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #7 0x7ffc794c82c0 
b   resource:///org/gnome/shell/ui/extensionSystem.js:135 (0x7f6f70259340 @ 509)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #8 0x556720193f78 
i   resource:///org/gnome/shell/ui/extensionSystem.js:342 (0x7f6f70259c48 @ 13)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #9 0x7ffc794c90c0 
b   self-hosted:251 (0x7f6f706c4ab0 @ 223)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #10 
0x556720193ef8 i   resource:///org/gnome/shell/ui/extensionSystem.js:341 
(0x7f6f70259bc0 @ 76)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #11 
0x556720193e78 i   resource:///org/gnome/shell/ui/extensionSystem.js:369 
(0x7f6f70259de0 @ 67)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #12 
0x7ffc794ca5c0 b   resource:///org/gnome/gjs/modules/signals.js:128 
(0x7f6f706d2230 @ 386)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #13 
0x7ffc794cadd0 b   resource:///org/gnome/shell/ui/sessionMode.js:205 
(0x7f6f526704d8 @ 254)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #14 
0x7ffc794cae30 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #15 
0x556720193de8 i   resource:///org/gnome/shell/ui/sessionMode.js:174 
(0x7f6f52670340 @ 100)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #16 
0x7ffc794cba10 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #17 
0x556720193d40 i   resource:///org/gnome/shell/ui/screenShield.js:1212 
(0x7f6f52653918 @ 159)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #18 
0x7ffc794cc5f0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop gnome-shell[1913]: clutter_actor_hide: assertion 
'CLUTTER_IS_ACTOR (self)' failed
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #19 
0x556720193cc0 i   resource:///org/gnome/shell/ui/screenShield.js:1198 
(0x7f6f52653890 @ 17)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #20 
0x556720193c38 i   resource:///org/gnome/shell/gdm/authPrompt.js:501 
(0x7f6f52681120 @ 61)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #21 
0x7ffc794cd880 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #22 
0x556720193bb0 i   resource:///org/gnome/shell/ui/unlockDialog.js:147 
(0x7f6f5268e5e8 @ 25)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #23 
0x7ffc794ce460 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f6f706b5de0 @ 71)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #24 
0x556720193b30 i   resource:///org/gnome/shell/ui/screenShield.js:1198 
(0x7f6f52653808 @ 46)
Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #25 
0x7ffc794cf040 I   

[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu

2020-07-26 Thread Lonnie Lee Best
@kia-kasurinen Thank you so much!

sudo apt-get install speech-dispatcher

After the command above, and restarting Firefox, Speech Synthesis is
working in Firefox.

Please advocate getting this package into the default install of Kubuntu
20.04. The browser will use it if it is there, and other OS desktops
make sure a speech-dispatcher is provided. Kubuntu should also. This
will help all web developers who use speech synthesis and keep Kubuntu
users from scratching their heads on web pages that are supposed to be
speaking to them, but are not.

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

Title:
  Firefox Speech Synthesis Not Working in Kubuntu

Status in firefox package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  New

Bug description:
  Modern web browsers, by spec, are supposed to support Speech
  Synthesis. Although Firefox does indeed support it, it doesn't work in
  Kubuntu 19.10.

  On this very page, you should be able to have Firefox read it aloud by
  typing shift-ctrl-I and then entering this code-line into the console
  (and pressing enter):

  speechSynthesis.speak(new
  SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));

  Something shorter, that you could type into the console (for testing)
  is:

  speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");

  You should be able to hear the browser say "testing 1, 2, 3" after
  doing this, but it doesn't working Kubuntu 19.10.

  This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
  19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1850 F pulseaudio
   /dev/snd/controlC0:  lonnie 1850 F pulseaudio
  BuildID: 20200217142647
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Mar 10 13:25:31 2020
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-03 (36 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NoProfiles: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

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

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


[Desktop-packages] [Bug 1880764] Re: Dragging icons frozen in place without finishing

2020-07-26 Thread Launchpad Bug Tracker
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Dragging icons frozen in place without finishing

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Expired

Bug description:
  When I was dragging around the discord icon around, Gnome froze and
  the icon remained in place. This was happening when I was compiling
  gettext and it was using memory. However, even after the compilation
  stopped and the memory went down, Gnome keeps the icons in place,
  refusing to finish what it started. In this state, the Grid button on
  the bottom has no effect, and clicking on the icons have no effect,
  though they will update when a new program launches or closes, and if
  a new window opens.

  I expect the Gnome Shell to become responsive once the memory has gone
  down. It has enough memory to finish the animations; it just won't
  finish them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  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
  CasperMD5CheckResult: skip
  Date: Tue May 26 17:24:53 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1880513] Re: Battery status indicator is wrong

2020-07-26 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Battery status indicator is wrong

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  The battery icon (top right for me) shows the wrong charge. I know this only 
because it freezes. So I plug in my computer to charge, it suspends/hibernates, 
and then when it is woken up the battery icon has frozen.
  I have a Lenovo Thinkpad X1 Carbon (3rd Gen), running Ubuntu 20.04 LTS.

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

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


[Desktop-packages] [Bug 1889021] Re: package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-07-26 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

** Changed in: software-properties (Ubuntu)
   Status: New => Invalid

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

Title:
  package python3-software-properties 0.98.9 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 
3.36.0-1ubuntu1 is installed
   Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 
is installed
   Depends: python3-software-properties (= 0.98.9.1) 
but 0.98.9 is installed
   Depends: ubuntu-drivers-common (>= 1:0.2.75) but 
1:0.8.1.1 is installed
   Depends: python3:any but it is a virtual package

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-software-properties 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 21:03:14 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-07-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  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: software-properties
  Title: package python3-software-properties 0.98.9 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1881009] Re: Gnome System Settings keep getting uninstalled automatically everytime I boot up the system. It has to be reinstalled by using apt install gnome-control-center.

2020-07-26 Thread Launchpad Bug Tracker
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Gnome System Settings keep getting uninstalled automatically everytime
  I boot up the system. It has to be reinstalled by using apt install
  gnome-control-center.

Status in gnome-control-center package in Ubuntu:
  Expired

Bug description:
  I am running Ubuntu 20.04 LTS. The system settings package cannot be
  found anywhere or called from the command line. Also, the display
  scaling (set to 1.25x) gets reset. I need to manually install gnome-
  control-center for it to work, but even then the display scaling
  option malfunctions, going much more than 2x as if it started at 1.25x
  as base. I have no seen issues with the other settings.


  $ gnome-control-center

  Command 'gnome-control-center' not found, but can be installed with:

  sudo apt install gnome-control-center

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
   apt-cache policy gnome-control-center
  gnome-control-center:
Installed: (none)
Candidate: 1:3.36.2-0ubuntu1
Version table:
   1:3.36.2-0ubuntu1 500
  500 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   1:3.36.1-1ubuntu5 500
  500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I'm on an HP Pavilion CS2800 laptop, with / on the SSD and /home on
  HDD.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 01:07:30 2020
  InstallationDate: Installed on 2020-05-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1881009/+subscriptions

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


[Desktop-packages] [Bug 602809] Re: add Mouse Click Debounce Feature?

2020-07-26 Thread Yei Gei
Here is a patch for libinput which worked for me. The debounce time is
hard coded to 25 ms and 12 ms. The patch will increase it to 100 ms and
50 ms. I hope it will help.

libinput_debounce_time.patch
 
--- a/src/evdev-debounce.c  2020-06-19 10:00:40.778552300 +1000
+++ b/src/evdev-debounce.c  2020-07-27 02:02:52.343254576 +1000
@@ -124,7 +124,7 @@
 debounce_set_timer(struct fallback_dispatch *fallback,
   uint64_t time)
 {
-   const int DEBOUNCE_TIMEOUT_BOUNCE = ms2us(25);
+   const int DEBOUNCE_TIMEOUT_BOUNCE = ms2us(100);
 
libinput_timer_set(>debounce.timer,
   time + DEBOUNCE_TIMEOUT_BOUNCE);
@@ -134,7 +134,7 @@
 debounce_set_timer_short(struct fallback_dispatch *fallback,
 uint64_t time)
 {
-   const int DEBOUNCE_TIMEOUT_SPURIOUS = ms2us(12);
+   const int DEBOUNCE_TIMEOUT_SPURIOUS = ms2us(50);
 
libinput_timer_set(>debounce.timer_short,
   time + DEBOUNCE_TIMEOUT_SPURIOUS);

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

Title:
  add Mouse Click Debounce Feature?

Status in xserver-xorg-input-evdev:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Model:  bonp3
  OS:  Ubuntu 10.04 LTS

  When I single click the mouse (external USB Mouse - Mouse Pad
  disabled) half the time the system responds as though I have double
  clicked the mouse.  I try 2 different USB mouse units and it still
  does this.  I am running Ubuntu 10.04 on a separate PC that does not
  have this mouse problem.  So I am thinking this problem is a System76
  driver issue???

  It's annoying.  :(

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

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


[Desktop-packages] [Bug 1888088] Re: [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

2020-07-26 Thread John Gilmore
I found a way to enable the amdgpu support for this hardware in the
standard LTS kernel!  Based on this comment on a YouTube video reviewing
this laptop:

  https://www.youtube.com/watch?v=FjegdWtHuOE=UgzbtkQw4vuk6ls-
6vF4AaABAg

Add "amdgpu.exp_hw_support=1" to the kernel command line in /etc/default/grub, 
run
update-grub, and reboot.  This FIXES ALL THE ISSUES that I encountered in this 
bug.  I am running linux-image-5.4.0-42-generic:amd64 (5.4.0-42.46) which is 
the current LTS kernel.

The same poster also recommended turning on this Firefox about:config
setting, to avoid screen tearing while playing YouTube videos:
layers.acceleration.force-enabled.

I have seen reports (comments below that same YouTube video, and
elsewhere) that there are small kernel patches in the 5.7 kernels that
also fix the screen brightness settings on this hardware.  Perhaps a
future Ubuntu kernel update can cherry-pick those fixes, and
automatically enable the experimental hardware support for this
integrated AMD Ryzen 5 4500U CPU/GPU?  Would be good for these fixes to
get into the Ubuntu 20.04.1 point release, too; these laptops are very
fast and cost $600 so they are selling very well.

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

Title:
  [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in mutter package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than
  Landscape doesn't work.  Similarly, selecting Fractional Scaling and
  then picking a scale factor has no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see behind the popup that the screen did not change its orientation,
  and the "Orientation" setting back in the Settings->Display window has
  been reverted to "Landscape" without me doing it.  Whether I choose
  keep or revert, or merely let it time out after 20 seconds, the result
  remains the same -- the display stays in Landscape mode and the
  setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  But when I turn on the "Fractional Scaling"
  slider, the graphics around the edge of the screen immediately
  increase in size (the icons in the left-hand dock, the text in the top
  bar), even though I have not changed the scale setting.  I have
  included two screenshots (original screen, and with Fractional Scaling
  on).  There is also some strangeness about whether sliding the
  Fractional Scaling slider updates the Scale menu to allow more scales
  - sometimes it does, sometimes it doesn't.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not actually scale, and a pop-up asks if I want to keep
  or revert the setting.  But looking back at the Displays settings, the
  Scale has already reverted to 100% (as above with the Orientation).
  Screenshot enclosed.

  The display has been rock-solid before this, but now it started
  showing artifacts, such as previous copies of the Displays window.
  I've enclosed a screen shot, which shows checkerboard in the screen
  locations that (in reality) were displaying prior versions of the
  window.  Hmm, examining that screenshot, it looks like the display DID
  start occupying 25% more space horizontally and vertically, but
  something about the video scanning versus the screen updating got out
  of whack.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. 

[Desktop-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW

2020-07-26 Thread Kai-Chuan Hsieh
** Summary changed:

- System shutdown directly by pressing power button and releasing immediately 
on Dell Vostro 5301
+ System shutdown directly by pressing power button and releasing immediately 
on Dell Vostro HW

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately on Dell Vostro HW

Status in OEM Priority Project:
  Incomplete
Status in gnome-session package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1881896] Re: "Sign In…" string not available for translation

2020-07-26 Thread Adolfo Jayme
** Changed in: ubuntu-translations
   Status: New => In Progress

** Changed in: ubuntu-translations
   Importance: Undecided => Low

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

Title:
  "Sign In…" string not available for translation

Status in Ubuntu Translations:
  In Progress
Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  The "Sign In…" string seems to be untranslated in deb version of GNOME
  Software on Ubuntu 20.04 and is not available for translation on
  Launchpad.

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

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


[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-07-26 Thread Kai-Chuan Hsieh
** Changed in: oem-priority
   Status: Fix Committed => 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/1881094

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

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


[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

2020-07-26 Thread Kai-Chuan Hsieh
** Changed in: oem-priority
   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/1882161

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

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

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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


[Desktop-packages] [Bug 1889021] [NEW] package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-07-26 Thread Charles Hodge
Public bug reported:

Check if you are using third party repositories. If so disable them, since they 
are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f
Transaction failed: The package system is broken
 The following packages have unmet dependencies:

software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 
3.36.0-1ubuntu1 is installed
 Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 is 
installed
 Depends: python3-software-properties (= 0.98.9.1) but 
0.98.9 is installed
 Depends: ubuntu-drivers-common (>= 1:0.2.75) but 
1:0.8.1.1 is installed
 Depends: python3:any but it is a virtual package

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-software-properties 0.98.9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Jul 26 21:03:14 2020
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2020-07-27 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
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: software-properties
Title: package python3-software-properties 0.98.9 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (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 software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1889021

Title:
  package python3-software-properties 0.98.9 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in software-properties package in Ubuntu:
  New

Bug description:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 
3.36.0-1ubuntu1 is installed
   Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 
is installed
   Depends: python3-software-properties (= 0.98.9.1) 
but 0.98.9 is installed
   Depends: ubuntu-drivers-common (>= 1:0.2.75) but 
1:0.8.1.1 is installed
   Depends: python3:any but it is a virtual package

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-software-properties 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 21:03:14 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-07-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  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: software-properties
  Title: package python3-software-properties 0.98.9 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake

2020-07-26 Thread Hui Wang
So, let's debug with the pulseaudio log.

Enable the debugging log in the pulsaudio:
edit /usr/lib/systemd/user/pulseaudio.service, comment out the line starting 
with ExecStart=..., add a new line "ExecStart=/user/bin/pulseaudio - 
--log-target=file:/home/your_user_name/pa.log

reboot

Then tail -f ~/pa.log


Plug the hdmi monitor, and select the hdmi audio as output device from UI. now 
check the pa.log, could you find the "configured_default_sink" from the log, it 
indicates the change of configured_default_sink.

If the hdmi audio is set to configured_default_sink and keeps unchanged
during the suspend and resume, the hdmi audio should be the output
device after resume.  So please check the changing about
configured_default_sink in the pa.log.

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

Title:
  pulseaudio has is buggy with hdmi audio and sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu

2020-07-26 Thread Kai Kasurinen
speech-dispatcher is not installed by default

** Project changed: kde-baseapps => kubuntu-meta (Ubuntu)

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

Title:
  Firefox Speech Synthesis Not Working in Kubuntu

Status in firefox package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  New

Bug description:
  Modern web browsers, by spec, are supposed to support Speech
  Synthesis. Although Firefox does indeed support it, it doesn't work in
  Kubuntu 19.10.

  On this very page, you should be able to have Firefox read it aloud by
  typing shift-ctrl-I and then entering this code-line into the console
  (and pressing enter):

  speechSynthesis.speak(new
  SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));

  Something shorter, that you could type into the console (for testing)
  is:

  speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");

  You should be able to hear the browser say "testing 1, 2, 3" after
  doing this, but it doesn't working Kubuntu 19.10.

  This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
  19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1850 F pulseaudio
   /dev/snd/controlC0:  lonnie 1850 F pulseaudio
  BuildID: 20200217142647
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Mar 10 13:25:31 2020
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-03 (36 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NoProfiles: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

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

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


[Desktop-packages] [Bug 1776069] Re: "Don't know how to handle 'file:///home//Downloads/.flatpakref'"

2020-07-26 Thread cyril hicks
** Changed in: gnome-software
   Status: Confirmed => Fix Committed

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

Title:
  "Don't know how to handle
  'file:///home//Downloads/.flatpakref'"

Status in GNOME Software:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  After installing Flatpak and the plugin for GNOME Software, Flatpaks 
downloaded from the Flatpak website (flathub.org/apps) are not able to be 
opened in the GNOME Software Center, with the program giving me the following 
error:
  "Don't know how to handle 
'file:///home//Downloads/.flatpakref'."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 07:44:30 2018
  InstallationDate: Installed on 2018-06-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.1-0ubuntu4
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

  -
  >>> IDENTICAL BUG IN GNOME'S GITLAB: 
https://gitlab.gnome.org/GNOME/gnome-software/issues/400/ <<<

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

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


[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

2020-07-26 Thread Hui Wang
After you plug in the headphone, the Active Profile should change to be


Could you please redo the test and upload a log?
reboot with headphone unplugged,
after booting up, plug headphone, make sure the headphone couldn't output sound,
run 'pacmd list > pa.log', then upload the pa.log.

thx.

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem

2020-07-26 Thread Hui Wang
According to the alsainfo.txt, the Capture source is not "Headset mic",
so the headphone can't output sound.

control.6 {
iface MIXER
name 'Capture Source'
value 'Headphone Mic'
comment {
access 'read write'
type ENUMERATED
count 1
item.0 'Headset Mic'
item.1 'Headphone Mic'
item.2 'Internal Mic'
}
}


Could you please remove the pulseaudio setting by running "rm -rf 
~/.config/pulse/*", then reboot and check if the Capture Source is Headset Mic 
now?

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

Title:
  [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm unable to play sound through the headphone jack on this laptop.
  When I try to play a wav with aplay (e.g. aplay /usr/share/sounds
  /speech-dispatcher/test.wav) the level indicators in pavucontrol
  fluctuate, but no sound results.  Adjusting the volume does not help.

  Also, when the headphones are plugged in, I cannot play sound through
  the internal speakers by selecting the "Speakers" port in pavucontrol
  Output Devices.  With the headphones unplugged, the internal speakers
  work fine.

  I tested the Ubuntu 19.10 live USB and I am able to play sound through
  the headphones without doing anything special (plug in headphones,
  select "Headphones" from the popup that appears, and use aplay as
  above), so the hardware itself is apparently okay.  The headphones do
  not work when booting the Ubuntu 20.04 live USB.

  The problem may be intermittent as I seem to recall I have been able
  to use the headphones since upgrading to 20.04, but I am not sure of
  my recollection.  I also think that in some of my tests, I was able to
  play sound through the speakers with the headphones plugged in (by
  selecting Speakers in pavucontrol) but I cannot reproduce this now.

  Happy to provide more information, try troubleshooting ideas, etc.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nate   2549 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 14:20:31 2020
  InstallationDate: Installed on 2019-06-03 (419 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0G7VYP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5482
  dmi.product.sku: 089E
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu

2020-07-26 Thread Lonnie Lee Best
Kubuntu team,

Can you please address this issue and add it to a checklist of testing
for all future releases?

Is there any way you'll be fixing this in Kubuntu 20.04 LTS?

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

Title:
  Firefox Speech Synthesis Not Working in Kubuntu

Status in KDE Base:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Modern web browsers, by spec, are supposed to support Speech
  Synthesis. Although Firefox does indeed support it, it doesn't work in
  Kubuntu 19.10.

  On this very page, you should be able to have Firefox read it aloud by
  typing shift-ctrl-I and then entering this code-line into the console
  (and pressing enter):

  speechSynthesis.speak(new
  SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));

  Something shorter, that you could type into the console (for testing)
  is:

  speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");

  You should be able to hear the browser say "testing 1, 2, 3" after
  doing this, but it doesn't working Kubuntu 19.10.

  This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
  19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1850 F pulseaudio
   /dev/snd/controlC0:  lonnie 1850 F pulseaudio
  BuildID: 20200217142647
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Mar 10 13:25:31 2020
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-03 (36 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NoProfiles: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions

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


[Desktop-packages] [Bug 1888984] Re: Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu

2020-07-26 Thread Lonnie Lee Best
*** This bug is a duplicate of bug 1866880 ***
https://bugs.launchpad.net/bugs/1866880

** This bug has been marked a duplicate of bug 1866880
   Firefox Speech Synthesis Not Working in Kubuntu

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

Title:
  Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu

Status in firefox package in Ubuntu:
  New

Bug description:
  This bug is more the fault of the Kubuntu and Ubuntu teams than it is
  the fault of Mozilla. Firefox indeed supports the web standard for
  speechSynthesis, but it doesn't work in Kubuntu 20.04. This does work
  in Ubuntu 16.04 and in Window 10. Like I said, it is web standard that
  should work in every browser. This bug is a regression compared to
  16.04.

  To reproduce this bug, open up any web page using Firefox and type
  ctrl-shift-I (to bring up the console of Firefox). Then, copy and
  paste the following text into the console and press enter:

  speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
  speak.");

  You should hear your browser say "Hello, I can speak.", but it doesn't
  work in the latest LTS releases.

  This bug means that all web pages, on the internet, that use
  speechSynthesis do not function as intended on Kubuntu 20.04 and
  Ubuntu 20.04.

  If you'd like to hear speechSynthesis in action, go to this web page using 
Firefox on Windows 10 or in Ubuntu 16.04 (where the trick's instructions will 
be spoken to you via Speech Synthesis):
  http://www.lonniebest.com/CardTrick/

  20.04 is a Long Term Support release. Please fix this, or I'm going to
  ask for my money back! Wait, scratch that last sentence.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jul 26 03:51:21 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-26 (91 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

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

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


[Desktop-packages] [Bug 1888984] Re: Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu

2020-07-26 Thread Lonnie Lee Best
** Description changed:

- This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
- Firefox supports the web standard for speechSynthesis, but it doesn't
- work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
- currently work in Window 10. Like I said, it is web standard that should
- work in every browser.
+ This bug is more the fault of the Kubuntu and Ubuntu teams than it is
+ the fault of Mozilla. Firefox indeed supports the web standard for
+ speechSynthesis, but it doesn't work in Kubuntu 20.04. This does work in
+ Ubuntu 16.04 and in Window 10. Like I said, it is web standard that
+ should work in every browser. This bug is a regression compared to
+ 16.04.
  
- To reproduce this bug, open up any web page using Firefox and hit ctrl-
+ To reproduce this bug, open up any web page using Firefox and type ctrl-
  shift-I (to bring up the console of Firefox). Then, copy and paste the
  following text into the console and press enter:
  
  speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
- speak");
+ speak.");
+ 
+ You should hear your browser say "Hello, I can speak.", but it doesn't
+ work in the latest LTS releases.
  
  This bug means that all web pages, on the internet, that use
  speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
  20.04.
  
- If you'd like to hear speechSynthesis in action, go to this web page using 
Firefox on Windows 10 or Ubuntu 16.04 (where the instructions will be spoken to 
you using Speech Synthesis web standard):
+ If you'd like to hear speechSynthesis in action, go to this web page using 
Firefox on Windows 10 or in Ubuntu 16.04 (where the trick's instructions will 
be spoken to you via Speech Synthesis):
  http://www.lonniebest.com/CardTrick/
  
- 20.04 is a Long Term Support release. Please fix this!
+ 20.04 is a Long Term Support release. Please fix this, or I'm going to
+ ask for my money back! Wait, scratch that last sentence.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jul 26 03:51:21 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-26 (91 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.sku: Not Applicable
  dmi.product.version: bonw13
  dmi.sys.vendor: System76

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

Title:
  Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu

Status in firefox package in Ubuntu:
  New

Bug description:
  This bug is more the fault of the Kubuntu and Ubuntu teams than it is
  the fault of Mozilla. Firefox indeed supports the web standard for
  speechSynthesis, but it doesn't work in Kubuntu 

[Desktop-packages] [Bug 1325867] Re: package duplicity 0.6.23-1ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package duplicity 0.6.23-1ubuntu4 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in duplicity package in Ubuntu:
  New

Bug description:
  I've got this error when I tried to update the system:
  Errors were encountered while processing:
   duplicity
   
  Current status: 1 update [-29].

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: duplicity 0.6.23-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Tue Jun  3 09:41:30 2014
  DuplicateSignature: package:duplicity:0.6.23-1ubuntu4:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-02-10 (477 days ago)
  InstallationMedia: Linux Mint 14 "Nadia" - Release amd64 (20121120)
  SourcePackage: duplicity
  Title: package duplicity 0.6.23-1ubuntu4 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to petra on 2014-03-30 (64 days ago)

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

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


[Desktop-packages] [Bug 1621686] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject-2 package in Ubuntu:
  Confirmed

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1621687] Re: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gi 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject
  Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1637355] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  I was uninstall python2 and reinstalled

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Oct 27 18:37:32 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-12-23 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to trusty on 2016-10-19 (8 days ago)

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

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


[Desktop-packages] [Bug 1632835] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  Referente ao python

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 10 11:46:09 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-09-26 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1743727] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug is no longer a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  子进程 已安装 post-installation 脚本 返回错误状态 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  when pc powered up, the mistake appeared

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan 12 15:09:31 2018
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2018-01-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-07-26 Thread Helmut Stult
With kernel 5.8-rc7

https://linux-hardware.org/?probe=ee86715eb3

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  

[Desktop-packages] [Bug 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem

2020-07-26 Thread Nate Eldredge
This seemed like it might have been related to bug 1873384.  However I
have pulseaudio 1:13.99.1-1ubuntu3.5 in which that bug is supposedly
fixed, and changing input sources does not fix the problem for me.

On the other hand the speakers are now working with the headphones
plugged in, when "Speakers" is selected in pavucontrol.  I don't know
what changed.

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

Title:
  [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm unable to play sound through the headphone jack on this laptop.
  When I try to play a wav with aplay (e.g. aplay /usr/share/sounds
  /speech-dispatcher/test.wav) the level indicators in pavucontrol
  fluctuate, but no sound results.  Adjusting the volume does not help.

  Also, when the headphones are plugged in, I cannot play sound through
  the internal speakers by selecting the "Speakers" port in pavucontrol
  Output Devices.  With the headphones unplugged, the internal speakers
  work fine.

  I tested the Ubuntu 19.10 live USB and I am able to play sound through
  the headphones without doing anything special (plug in headphones,
  select "Headphones" from the popup that appears, and use aplay as
  above), so the hardware itself is apparently okay.  The headphones do
  not work when booting the Ubuntu 20.04 live USB.

  The problem may be intermittent as I seem to recall I have been able
  to use the headphones since upgrading to 20.04, but I am not sure of
  my recollection.  I also think that in some of my tests, I was able to
  play sound through the speakers with the headphones plugged in (by
  selecting Speakers in pavucontrol) but I cannot reproduce this now.

  Happy to provide more information, try troubleshooting ideas, etc.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nate   2549 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 14:20:31 2020
  InstallationDate: Installed on 2019-06-03 (419 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0G7VYP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5482
  dmi.product.sku: 089E
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1491564] Re: package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1715062 ***
https://bugs.launchpad.net/bugs/1715062

** This bug has been marked a duplicate of bug 1715062
   package python-six 1.10.0-3 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in totem package in Ubuntu:
  Expired

Bug description:
  It's occurs while system auto update.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Wed Sep  2 16:06:07 2015
  DuplicateSignature: package:totem:3.14.2-0ubuntu1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-08-22 (10 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: totem
  Title: package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

2020-07-26 Thread anxiety scroll
Solved after deleting custom installation of lib-wacom and then
installing xserver-xorg-input-wacom, libwacom2, and libwacom-common.
Showing on the settings page after rebooting.

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

Title:
  Wacom tablet not recognized in Settings > Devices

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem with Ubuntu 18.04 developing branch as described for 
Ubuntu 16.04 in
  https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887
  I can draw, e.g., with tuxpaint, I can use stylus and graphic tablet "Wacom 
Intuos Art Black Pen + Touch S" like a touchpad with mouse (left, muddle, right 
button), but I cannot access the pad via Settings > Devices > Wacom Tablet: 
"Stylus not recognized". So, no reprogramming of stylus buttons and tablet 
buttons :(

  Hopefully this will be resolved till the final version of 18.04 in
  April?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 16:48:48 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  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/1753525/+subscriptions

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


[Desktop-packages] [Bug 1889015] [NEW] display crashes sometimes when click on firefox or settings

2020-07-26 Thread robert a mclean
Public bug reported:

display crashes sometimes when click on firefox or settings

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jul 26 16:07:13 2020
DistUpgraded: 2020-07-09 17:13:15,323 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] 
[103c:2a58]
InstallationDate: Installed on 2020-07-09 (17 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: HP-Pavilion RX885AA-ABA a6000n
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=e43514f2-3e33-49da-9662-a8e8923b87f6 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2020-07-09 (16 days ago)
dmi.bios.date: 02/02/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.01
dmi.board.name: NARRA
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.01
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.01:bd02/02/2007:svnHP-Pavilion:pnRX885AA-ABAa6000n:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.family: 103C_53316J
dmi.product.name: RX885AA-ABA a6000n
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
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 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Jul 26 16:01:21 2020
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.4
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug bionic compiz-0.9 corruption ubuntu

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

Title:
  display crashes sometimes when click on firefox or settings

Status in xorg package in Ubuntu:
  New

Bug description:
  display crashes sometimes when click on firefox or settings

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jul 26 16:07:13 2020
  DistUpgraded: 2020-07-09 17:13:15,323 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] 
[103c:2a58]
  InstallationDate: Installed on 2020-07-09 (17 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 001 Device 002: ID 0bda:0111 Realtek 

[Desktop-packages] [Bug 1889013] [NEW] Xorg freeze

2020-07-26 Thread Mike Hatch
Public bug reported:

Everything is running smooth, I enjoy this software, but it all freezes
up randomly.  Sometimes I can still move the cursor, other times I
cannot do anything but a hard reset.  Do not know why, or haven't
figured out what specifically I am doing when this happens.  Usually
just browsing the net or something simple like that when it happens.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 26 14:01:10 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:099d]
InstallationDate: Installed on 2020-07-13 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire E5-532
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eb592001-0986-4e81-8bae-52faaa85ba41 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Zoro_BA
dmi.board.vendor: Acer
dmi.board.version: V1.16
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.16:bd11/13/2015:svnAcer:pnAspireE5-532:pvrV1.16:rvnAcer:rnZoro_BA:rvrV1.16:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BSW
dmi.product.name: Aspire E5-532
dmi.product.sku: Aspire E5-532_099D_1.16
dmi.product.version: V1.16
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
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

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Everything is running smooth, I enjoy this software, but it all
  freezes up randomly.  Sometimes I can still move the cursor, other
  times I cannot do anything but a hard reset.  Do not know why, or
  haven't figured out what specifically I am doing when this happens.
  Usually just browsing the net or something simple like that when it
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 14:01:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:099d]
  InstallationDate: Installed on 2020-07-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  

[Desktop-packages] [Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

2020-07-26 Thread anxiety scroll
Reporting the bug from ubuntu  18.04.4 LTS. The tablet works and the
pointer moves as expected but the settings->devices->wacom configuration
does not recognize the tablet. Also, I report this same tablet and same
computer was working properly before, but not sure if it was on 18.04 or
19.something. The thing is it was working well before doing a clean
reinstall of 18.04.4

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

Title:
  Wacom tablet not recognized in Settings > Devices

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem with Ubuntu 18.04 developing branch as described for 
Ubuntu 16.04 in
  https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887
  I can draw, e.g., with tuxpaint, I can use stylus and graphic tablet "Wacom 
Intuos Art Black Pen + Touch S" like a touchpad with mouse (left, muddle, right 
button), but I cannot access the pad via Settings > Devices > Wacom Tablet: 
"Stylus not recognized". So, no reprogramming of stylus buttons and tablet 
buttons :(

  Hopefully this will be resolved till the final version of 18.04 in
  April?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 16:48:48 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  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/1753525/+subscriptions

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


[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-07-26 Thread Mike Lykov
Wow, I have now same bug with VLC. I can start it, but can not quit. It do not 
respond to quit and stays in tray and in background. I need to kill it to start 
again if I want to watch anything other.
If this bug is not a VLC bug, but amdgpu driver bug, I will check it when 5.8 
will be released.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  

[Desktop-packages] [Bug 1799440] Re: Many apps are missing icons in high contrast

2020-07-26 Thread Paul White
Using Ubuntu 20.04 I'm seeing high contrast icons for gnome-calculator,
gnome-software and gnome-system-monitor so changing the status of those
tasks to 'Fix Released'.

** Changed in: gnome-calculator (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Fix Released

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

Title:
  Many apps are missing icons in high contrast

Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Fix Released
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New

Bug description:
  ## Expected Behavior

  Every app has a proper symbolic icon for high contrast mode.

  ## Actual Behavior

  Characters and Logs are missing an icon.

  Amazon, Calculator, Remmina, Software & Updates, Startup Disk Creator,
  System Monitor, Thunderbird, Ubuntu Software are using fullcolor
  icons, in some cases different from default.

  LibreOffice, Software Updater, Startup Applications and Transmission
  are using deprecated HighContrast icons.

  
  ## Steps to Reproduce the Problem

1. Settings → Universal Access → High Contrast
2. Show Applications

  ## Specifications

  Default Ubuntu 18.10 image.

  See attached screenshots.

  (Moved from https://github.com/ubuntu/yaru/issues/927)

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

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


[Desktop-packages] [Bug 1889010] [NEW] [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem

2020-07-26 Thread Nate Eldredge
Public bug reported:

I'm unable to play sound through the headphone jack on this laptop.
When I try to play a wav with aplay (e.g. aplay /usr/share/sounds
/speech-dispatcher/test.wav) the level indicators in pavucontrol
fluctuate, but no sound results.  Adjusting the volume does not help.

Also, when the headphones are plugged in, I cannot play sound through
the internal speakers by selecting the "Speakers" port in pavucontrol
Output Devices.  With the headphones unplugged, the internal speakers
work fine.

I tested the Ubuntu 19.10 live USB and I am able to play sound through
the headphones without doing anything special (plug in headphones,
select "Headphones" from the popup that appears, and use aplay as
above), so the hardware itself is apparently okay.  The headphones do
not work when booting the Ubuntu 20.04 live USB.

The problem may be intermittent as I seem to recall I have been able to
use the headphones since upgrading to 20.04, but I am not sure of my
recollection.  I also think that in some of my tests, I was able to play
sound through the speakers with the headphones plugged in (by selecting
Speakers in pavucontrol) but I cannot reproduce this now.

Happy to provide more information, try troubleshooting ideas, etc.
Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nate   2549 F pulseaudio
CasperMD5CheckResult: skip
Date: Sun Jul 26 14:20:31 2020
InstallationDate: Installed on 2019-06-03 (419 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: Only some of outputs are working
Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback 
problem
UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago)
dmi.bios.date: 07/02/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0G7VYP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5482
dmi.product.sku: 089E
dmi.sys.vendor: Dell Inc.

** 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/1889010

Title:
  [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm unable to play sound through the headphone jack on this laptop.
  When I try to play a wav with aplay (e.g. aplay /usr/share/sounds
  /speech-dispatcher/test.wav) the level indicators in pavucontrol
  fluctuate, but no sound results.  Adjusting the volume does not help.

  Also, when the headphones are plugged in, I cannot play sound through
  the internal speakers by selecting the "Speakers" port in pavucontrol
  Output Devices.  With the headphones unplugged, the internal speakers
  work fine.

  I tested the Ubuntu 19.10 live USB and I am able to play sound through
  the headphones without doing anything special (plug in headphones,
  select "Headphones" from the popup that appears, and use aplay as
  above), so the hardware itself is apparently okay.  The headphones do
  not work when booting the Ubuntu 20.04 live USB.

  The problem may be intermittent as I seem to recall I have been able
  to use the headphones since upgrading to 20.04, but I am not sure of
  my recollection.  I also think that in some of my tests, I was able to
  play sound through the speakers with the headphones plugged in (by
  selecting Speakers in pavucontrol) but I cannot reproduce this now.

  Happy to provide more information, try troubleshooting ideas, etc.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nate   2549 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 14:20:31 2020
  InstallationDate: Installed on 2019-06-03 (419 days ago)
  InstallationMedia: Ubuntu 19.04 

[Desktop-packages] [Bug 1889005] Re: Can no longer print to network printer

2020-07-26 Thread Paul White
As per https://wiki.ubuntu.com/Bugs/FindRightPackage#Printing I'm moving
this to the cups package.

** Package changed: ubiquity (Ubuntu) => cups (Ubuntu)

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

Title:
  Can no longer print to network printer

Status in cups package in Ubuntu:
  New

Bug description:
  I believe that a recent update has broken the ability of this laptop to print 
to a network printer.  HPLIP reports that it is unable to communicate with the 
printer although the machine to which the printer is directly connected (via 
USB cable) has normal print function.  The command 

   hp-check -i 

  gives the following output

  don@Homebrew ~ $ hp-check -i
  Saving output in log file: /home/don/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the
  HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies
  are installed to successfully compile HPLIP.  
  
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro  
  
  supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
  
  has the proper dependencies installed to successfully run.
  
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode  
  
  will check both of the above cases (both compile- and run-time dependencies). 
  

  Check types:  
  
  a. EXTERNALDEP - External Dependencies
  
  b. GENERALDEP - General Dependencies (required both at compile and run time)  
  
  c. COMPILEDEP - Compile time Dependencies 
  
  d. [All are run-time checks]  
  
  PYEXT SCANCONF QUEUES PERMISSION  
  

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10
  versions dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
GNU/Linux
   Host: Homebrew
   Proc: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 GNU/Linux
   Distribution: ubuntu 20.04
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.20.3
  HPLIP-Home: /usr/share/hplip
  warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  20.04 version 

  Current contents of '/etc/hp/hplip.conf' file:
  # hplip.conf.  Generated from hplip.conf.in by configure.

  [hplip]
  version=3.20.3

  [dirs]
  home=/usr/share/hplip
  run=/var/run
  ppd=/usr/share/ppd/hplip/HP
  ppdbase=/usr/share/ppd/hplip
  doc=/usr/share/doc/hplip
  html=/usr/share/doc/hplip-doc
  icon=no
  cupsbackend=/usr/lib/cups/backend
  cupsfilter=/usr/lib/cups/filter
  drv=/usr/share/cups/drv
  bin=/usr/bin
  apparmor=/etc/apparmor.d
  # Following values are determined at configure time and cannot be changed.
  [configure]
  network-build=yes
  libusb01-build=no
  pp-build=no
  gui-build=yes
  scanner-build=yes
  fax-build=yes
  dbus-build=yes
  cups11-build=no
  doc-build=yes
  shadow-build=no
  hpijs-install=yes
  foomatic-drv-install=yes
  foomatic-ppd-install=no
  foomatic-rip-hplip-install=no
  hpcups-install=yes
  cups-drv-install=yes
  cups-ppd-install=no
  internal-tag=3.20.3
  restricted-build=no
  ui-toolkit=qt5
  qt3=no
  qt4=no
  qt5=yes
  policy-kit=yes
  lite-build=no
  udev_sysfs_rules=no
  hpcups-only-build=no
  hpijs-only-build=no
  apparmor_build=no
  class-driver=no

  
  Current contents of '/var/lib/hp/hplip.state' file:
  Plugins are not installed. Could not access file: No such file or directory

  Current contents of '~/.hplip/hplip.conf' file:
  [commands]
  scan = /usr/bin/simple-scan %SANE_URI%

  [fax]
  email_address = 
  voice_phone = 

  [last_used]
  device_uri = hp:/usb/HP_LaserJet_M203-M206?serial=VNB3B86941
  printer_name = 
  working_dir = .

  [polling]
  device_list = 
  enable = false
  interval = 5

  [refresh]
  enable = false
  rate = 30
  type = 1

  [settings]
  systray_messages = 0
  systray_visible = 0

  [upgrade]
  last_upgraded_time = 1592057498
  notify_upgrade = false
  

[Desktop-packages] [Bug 1889005] [NEW] Can no longer print to network printer

2020-07-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I believe that a recent update has broken the ability of this laptop to print 
to a network printer.  HPLIP reports that it is unable to communicate with the 
printer although the machine to which the printer is directly connected (via 
USB cable) has normal print function.  The command 
  
 hp-check -i 

gives the following output

don@Homebrew ~ $ hp-check -i
Saving output in log file: /home/don/hp-check.log

HP Linux Imaging and Printing System (ver. 3.20.3)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10
versions dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 GNU/Linux
 Host: Homebrew
 Proc: 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 GNU/Linux
 Distribution: ubuntu 20.04
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.20.3
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  20.04 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.20.3

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.20.3
restricted-build=no
ui-toolkit=qt5
qt3=no
qt4=no
qt5=yes
policy-kit=yes
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=no
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[commands]
scan = /usr/bin/simple-scan %SANE_URI%

[fax]
email_address = 
voice_phone = 

[last_used]
device_uri = hp:/usb/HP_LaserJet_M203-M206?serial=VNB3B86941
printer_name = 
working_dir = .

[polling]
device_list = 
enable = false
interval = 5

[refresh]
enable = false
rate = 30
type = 1

[settings]
systray_messages = 0
systray_visible = 0

[upgrade]
last_upgraded_time = 1592057498
notify_upgrade = false
pending_upgrade_time = 0

[installation]
date_time = 07/26/20 10:10:55
version = 3.20.3


 


-
| External Dependencies |
-

 error: cups  CUPS - Common Unix Printing System
   REQUIRED1.1 -   INCOMPAT   'CUPS may not be 
installed or not running'
 gs   GhostScript - PostScript and PDF language interpreter and 
previewer REQUIRED7.059.50OK -
 error: xsane xsane - Graphical scanner frontend for SANE   
   OPTIONAL0.9 -   

[Desktop-packages] [Bug 1884461] Re: Cheese "webcam" application lacks settings menu option in 20.04 LTS

2020-07-26 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1879183 ***
https://bugs.launchpad.net/bugs/1879183

** This bug has been marked a duplicate of bug 1879183
   Cheese  does not show preferences/options/menus to non-GNOME Users

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

Title:
  Cheese "webcam" application lacks settings menu option in 20.04 LTS

Status in Ubuntu MATE:
  New
Status in cheese package in Ubuntu:
  New

Bug description:
  I have used cheese successfully with a popular thermal camera and uvc board 
combo on cheese for about a year in ubuntu mate 18.04 LTS. The only requirement 
was a small change to the resolution in the settings of the cheese application. 
I have ubuntu mate 20.04 LTS installed on two different laptops and can now not 
access the settings option; rendering the thermal camera unusable with this 
application. I definitely do not see an option in the gui to access settings in 
"cheese". 
  Thanks : )

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

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


[Desktop-packages] [Bug 1869897] Re: missing ssh prompt to touch yubikey device when using gnome

2020-07-26 Thread Davide Marchi
The same problem with ssh PAM OATH and Gnome Shell 3.28.4

Via ssh no problem, via "Gnome File" filemanager gui using
"sftp://user@192.168.88.250:22/home/user; no any window to ask the one
time secret key, and the process fails.

sftp://vage@192.168.88.250:22/home/vage

Jul 26 18:42:16 localhost dbus-daemon[1155]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
Jul 26 18:42:16 localhost NetworkManager[1207]:   [1595781736.3070] dhcp4 
(eth1):   nameserver '208.67.220.220'
Jul 26 18:42:16 localhost nm-dispatcher: req:1 'dhcp4-change' [eth1]: new 
request (1 scripts)
Jul 26 18:42:16 localhost NetworkManager[1207]:   [1595781736.3071] dhcp4 
(eth1): state changed bound -> bound
Jul 26 18:42:16 localhost nm-dispatcher: req:1 'dhcp4-change' [eth1]: start 
running ordered scripts...
Jul 26 18:42:16 localhost systemd[1]: Starting Network Manager Script 
Dispatcher Service...
Jul 26 18:42:16 localhost systemd[1]: Started Network Manager Script Dispatcher 
Service.

If request I can try from a newer OS.

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

Title:
  missing ssh prompt to touch yubikey device when using gnome

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

Bug description:
  I can't exactly pinpoint which gnome package is responsible for this.
  It might be gnome-keyring. Let's go with gnome-shell first.

  openssh 8.2p1[1] in focal has support for U2F authentication. This is
  a new feature we will highlight in the release notes and a blog post.

  You can create a keypair and the authentication only succeeds if you
  have the u2f hardware device plugged in, and touch it at the moment of
  authentication.

  In a console only env, it works like this:
  """
  andreas@nsnx:~$ env|grep SSH
  andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75
  Confirm user presence for key ECDSA-SK 
SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M
  Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 
5.4.0-21-generic x86_64)
  ...
  Last login: Tue Mar 31 13:35:44 2020 from 10.0.100.1
  """

  The "Confirm" prompt is asking the user to touch the hardware device
  (a yubikey in this case).

  If I use openssh's ssh-agent, it still works as expected and I see
  that prompt:

  """
  andreas@nsnx:~$ env|grep SSH
  andreas@nsnx:~$ eval $(ssh-agent)
  Agent pid 68267
  andreas@nsnx:~$ env|grep SSH
  SSH_AUTH_SOCK=/tmp/ssh-75OwXd9gR6tq/agent.68252
  SSH_AGENT_PID=68267
  andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75
  Warning: Permanently added '10.0.100.75' (ECDSA) to the list of known hosts.
  Confirm user presence for key ECDSA-SK 
SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M
  Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 
5.4.0-21-generic x86_64)
  (...)
  Last login: Tue Mar 31 14:33:18 2020 from 10.0.100.1
  """

  But with "gnome's ssh-agent" (I'm waving my hands here a bit), it just
  stalls. The prompt is swallowed by something. Here I opened a new
  gnome terminal in my existing focal desktop session:

  """
  andreas@nsnx:~$ env|grep SSH
  SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  SSH_AGENT_PID=4655
  andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75
  
  """

  It only moves forward if I touch the device, which is expected. But
  the "Confirm user presence" prompt is nowhere to be seen.

  I'm not sure how gnome-keyring interacts with ssh-agent. I see it is spawned 
by gnome-keyring-daemon:
     4556 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
     6449 ?S  0:00  \_ /usr/bin/ssh-agent -D -a 
/run/user/1000/keyring/.ssh

  But the PID referenced by the SSH_AGENT_PID shell variable above points to 
another copy, spawned by gnome-session-binary:
     4583 tty3 Sl+0:00  \_ /usr/libexec/gnome-session-binary 
--systemd --systemd --session=ubuntu
     4655 ?Ss 0:00  \_ /usr/bin/ssh-agent 
/usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session 
--systemd --session=ubuntu

  In any case, the actual prompt "Confirm user presence for key" comes from 
openssh code:
  ./ssh-agent.c:"Confirm user presence for key %s %s",
  ./sshconnect2.c:  "Confirm user presence for key %s 
%s",

  My guess is that the gnome wrapper, whatever it is, is not expecting
  that prompt.

  1. https://www.openssh.com/txt/release-8.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 11:29:06 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-13 (169 days ago)
  

[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

2020-07-26 Thread Nicolas Rogues
HPLIP 3.20.6 downloaded from developers.hp.com resolves all the issues

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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


[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-07-26 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => New

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected 

[Desktop-packages] [Bug 1884461] Re: Cheese "webcam" application lacks settings menu option in 20.04 LTS

2020-07-26 Thread Norbert
** Tags removed: cheese
** Tags added: focal

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

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

Title:
  Cheese "webcam" application lacks settings menu option in 20.04 LTS

Status in Ubuntu MATE:
  New
Status in cheese package in Ubuntu:
  New

Bug description:
  I have used cheese successfully with a popular thermal camera and uvc board 
combo on cheese for about a year in ubuntu mate 18.04 LTS. The only requirement 
was a small change to the resolution in the settings of the cheese application. 
I have ubuntu mate 20.04 LTS installed on two different laptops and can now not 
access the settings option; rendering the thermal camera unusable with this 
application. I definitely do not see an option in the gui to access settings in 
"cheese". 
  Thanks : )

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

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


[Desktop-packages] [Bug 1888042] Re: Qualcomm Atheros QCA6174

2020-07-26 Thread Norbert
** Tags removed: lan wireless

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

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

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


[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

2020-07-26 Thread Nicolas Rogues
Same issue issue with an OfficeJet 8010 here on a fresh Ubuntu 20.04
install. HPLIP downloaded from hp.com used to work on 16.04 & 18.04
setups with this printer.

No HPLIP installed from hp.com, just Ubuntu 20.04 installation.

I ran the command from post #4, no error. But it still does not work.
Please find attached hp-check log.

These comments from hp-check log are strange for packages from focal repos ?
1/ warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
2/ warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  20.04 version
3/ Missing Required Dependencies
-
error: 'libcups2' package is missing/incompatible 
error: 'libdbus-1-dev' package is missing/incompatible 
error: 'libjpeg-dev' package is missing/incompatible 
error: 'libcups2-dev' package is missing/incompatible 
error: 'cups-bsd' package is missing/incompatible 
error: 'cups-client' package is missing/incompatible 
error: 'libcupsimage2-dev' package is missing/incompatible 
error: 'libusb-1.0.0-dev' package is missing/incompatible 
error: 'libusb-0.1-4' package is missing/incompatible 
error: 'libsane-dev' package is missing/incompatible 
error: 'libsnmp-dev' package is missing/incompatible 
error: 'snmp-mibs-downloader' package is missing/incompatible 
error: 'openssl' package is missing/incompatible 
error: 'python3-pyqt4' package is missing/incompatible 
error: 'gtk2-engines-pixbuf' package is missing/incompatible 
error: 'python3-dev' package is missing/incompatible 
error: 'libtool' package is missing/incompatible 
error: 'libtool-bin' package is missing/incompatible 

Missing Optional Dependencies
-
error: 'gtk2-engines-pixbuf' package is missing/incompatible 
error: 'xsane' package is missing/incompatible 
error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

** Attachment added: "hp-check.log"
   
https://bugs.launchpad.net/hplip/+bug/1879649/+attachment/5395993/+files/hp-check.log

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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


[Desktop-packages] [Bug 1888127] Re: firefox crash

2020-07-26 Thread Norbert
** Tags added: focal

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

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

Title:
  firefox crash

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox crashes when  i leave it open i suspend the pc then when i
  open it firefox crashes

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

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


[Desktop-packages] [Bug 1888042] Missing required logs.

2020-07-26 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1888042

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

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

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


[Desktop-packages] [Bug 1888125] Re: refreshing cache stuck in ubuntu mate 20.04

2020-07-26 Thread Norbert
** Tags added: focal

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  refreshing cache stuck in ubuntu mate 20.04

Status in Ubuntu MATE:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  i have a very annoying bug which is refreshing cache is just not
  closing only if i rebooted the system!

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

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


[Desktop-packages] [Bug 1888042] Re: Qualcomm Atheros QCA6174

2020-07-26 Thread Norbert
** Tags added: focal

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

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

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

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

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


[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

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

** Changed in: notify-python (Ubuntu)
   Status: New => Confirmed

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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


[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

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

** Changed in: pillow-python2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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


[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

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

** Changed in: python-reportlab (Ubuntu)
   Status: New => Confirmed

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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


[Desktop-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update

2020-07-26 Thread Paul White
With -proposed enabled I updated the various evolution packages to
version 3.36.4-0ubuntu1.

As per text case, I was able to send emails between the accounts that I
have set up in Evolution, view existing entries in the Calendar and
create new Calendar entries which were viewable in other applications
such as Lightning and my email provider's web interface.

** 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 evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1886644

Title:
  SRU the current 3.36.4 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server 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/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

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

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


[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-07-26 Thread Oliver Old
** Bug watch added: github.com/systemd/systemd/issues #15316
   https://github.com/systemd/systemd/issues/15316

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/15316
   Importance: Unknown
   Status: Unknown

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  Unknown
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): 

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

2020-07-26 Thread Saroumane
Sorry for not answering sooner, I've been quite busy.
I already spent too much time reproducing the bug under differents OS and 
setups.

Gnome does not want to help ? Fine, I switched to more reliable audio
player.

-- 
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 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

2020-07-26 Thread Bartosz Kosiorek
Please run application with command:

`simple-scan -d`

and attach the output.

It seems that it is duplication of the upstream issue:
https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185


** Bug watch added: gitlab.gnome.org/GNOME/simple-scan/-/issues #185
   https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185

** Changed in: simple-scan (Ubuntu)
   Status: New => Incomplete

** Also affects: simple-scan via
   https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1888238/+subscriptions

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


[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3

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

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ 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.

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

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

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


[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-26 Thread Treviño
** 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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1874567

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
  

[Desktop-packages] [Bug 1888996] [NEW] NetworkManager crashes with segfault after July 2020 updates

2020-07-26 Thread Sec Aficionado
Public bug reported:

Ubuntu 18.04 upgraded from 16.04 in 2018. System was working fine until
latest batch of updates/patches.

PC boots up without issues, but there is no network when desktop
appears. dmesg does not show any problems related to network. It appears
network simply does not attempt to start. When trying to start network-
manager manually, it crashes with segfault.

Network does start manually with: sudo ip link set dev eno1 up
Followed by: sudo dhclient -v eno1
NetworkManager applets say "something went wrong"

Output of lsb_release -rd:
Description:Ubuntu 18.04.4 LTS
Release:18.04

Output of apt-cache policy pkgname:
network-manager:
  Installed: 1.10.6-2ubuntu1.4
  Candidate: 1.10.6-2ubuntu1.4
  Version table:
 *** 1.10.6-2ubuntu1.4 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.10.6-2ubuntu1.1 500
   500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
 1.10.6-2ubuntu1 500
   500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

What I expected to happen:
System should boot up normally and have network available, via DHCP

What happened instead:
System boots up, network is not configured, there are no errors, but 
NetworkManager crashes upon manual start.

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

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

Title:
  NetworkManager crashes with segfault after July 2020 updates

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 upgraded from 16.04 in 2018. System was working fine
  until latest batch of updates/patches.

  PC boots up without issues, but there is no network when desktop
  appears. dmesg does not show any problems related to network. It
  appears network simply does not attempt to start. When trying to start
  network-manager manually, it crashes with segfault.

  Network does start manually with: sudo ip link set dev eno1 up
  Followed by: sudo dhclient -v eno1
  NetworkManager applets say "something went wrong"

  Output of lsb_release -rd:
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  Output of apt-cache policy pkgname:
  network-manager:
Installed: 1.10.6-2ubuntu1.4
Candidate: 1.10.6-2ubuntu1.4
Version table:
   *** 1.10.6-2ubuntu1.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  What I expected to happen:
  System should boot up normally and have network available, via DHCP

  What happened instead:
  System boots up, network is not configured, there are no errors, but 
NetworkManager crashes upon manual start.

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

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


[Desktop-packages] [Bug 1888994] [NEW] Display scale setting is not saved across reboot

2020-07-26 Thread todd palgut
Public bug reported:

I set my scale setting to 200%.  If I have to reboot the pc the setting
is not saved and must be set again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Sun Jul 26 08:42:34 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-06-29 (27 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1888994

Title:
  Display scale setting is not saved across reboot

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

Bug description:
  I set my scale setting to 200%.  If I have to reboot the pc the
  setting is not saved and must be set again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jul 26 08:42:34 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-29 (27 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1888994/+subscriptions

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


[Desktop-packages] [Bug 1888992] [NEW] [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

2020-07-26 Thread Francis Chin
Public bug reported:

I boot my system without any sound devices plugged into any jacks;
checking Gnome settings Sound, Output Device is "Dummy Output" (no other
options available in drop-down list). I plug in headphones into the
front jack and play some audio, but do not hear any sound from the
headphones; checking Gnome settings Sound, the Output Device is still
"Dummy Output", with no other options available.

This is a regression from previous behaviour, when plugging in
headphones into the front jack would automatically enable/switch to the
front jack and its associated controller "Family 17h (Models 00h-0fh) HD
Audio Controller" (this is the motherboard's onboard audio hardware).

I can currently workaround this each time I plug in the headphones by
installing and running pavucontrol, and under Configuration selecting
"Analogue Stereo Output (unplugged) (unavailable)" - this option becomes
"Analogue Stereo Output" after I select it.

This seems to be a regression in pulseaudio after an upgrade from from
1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chinf  1741 F pulseaudio
 /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
 /dev/snd/controlC0:  chinf  1741 F pulseaudio
 /dev/snd/timer:  chinf  1741 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 26 12:46:52 2020
InstallationDate: Installed on 2018-10-29 (635 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chinf  1741 F pulseaudio
 /dev/snd/controlC0:  chinf  1741 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No 
sound at all
UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
dmi.bios.date: 12/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.40
dmi.board.name: AB350 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1888992

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  

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

2020-07-26 Thread Andreas
thank you, people - restarting (Alt-F2 > r) indeed gets rid of the window. 
Do we know what causes it? 
How to fix? 

Ubuntu 20.04 running Gnome-Vanilla desktop with nvidia-driver
is this related to snap by any chance? Or to the new disk that I added to my 
system recently? 

can I provide any logs?

cheers

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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


[Desktop-packages] [Bug 1888986] [NEW] package install-info 6.7.0.dfsg.2-5 failed to install/update

2020-07-26 Thread Gerhard Beck
Public bug reported:

Ubuntu 20.04 LTS
 when sudo apt-get update:

install-info (6.7.0.dfsg.2-5) wird eingerichtet ...
/usr/sbin/update-info-dir: 6: /etc/environment: Syntax error: Unterminated 
quoted string
dpkg: Fehler beim Bearbeiten des Paketes install-info (--configure):
 »installiertes install-info-Skript des Paketes post-installation«-Unterprozess 
gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)

then:
install-info (6.7.0.dfsg.2-5) wird eingerichtet ...
/usr/sbin/update-info-dir: 6: /etc/environment: Syntax error: Unterminated 
quoted string
dpkg: Fehler beim Bearbeiten des Paketes install-info (--configure):
 »installiertes install-info-Skript des Paketes post-installation«-Unterprozess 
gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
 install-info
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  package install-info 6.7.0.dfsg.2-5 failed to install/update

Status in texinfo package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS
   when sudo apt-get update:

  install-info (6.7.0.dfsg.2-5) wird eingerichtet ...
  /usr/sbin/update-info-dir: 6: /etc/environment: Syntax error: Unterminated 
quoted string
  dpkg: Fehler beim Bearbeiten des Paketes install-info (--configure):
   »installiertes install-info-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 2 zurück
  Fehler traten auf beim Bearbeiten von:
   install-info
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  then:
  install-info (6.7.0.dfsg.2-5) wird eingerichtet ...
  /usr/sbin/update-info-dir: 6: /etc/environment: Syntax error: Unterminated 
quoted string
  dpkg: Fehler beim Bearbeiten des Paketes install-info (--configure):
   »installiertes install-info-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 2 zurück
  Fehler traten auf beim Bearbeiten von:
   install-info
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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


[Desktop-packages] [Bug 1888984] [NEW] Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu

2020-07-26 Thread Lonnie Lee Best
Public bug reported:

This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
Firefox supports the web standard for speechSynthesis, but it doesn't
work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
currently work in Window 10. Like I said, it is web standard that should
work in every browser.

To reproduce this bug, open up any web page using Firefox and hit ctrl-
shift-I (to bring up the console of Firefox). Then, copy and paste the
following text into the console and press enter:

speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
speak");

This bug means that all web pages, on the internet, that use
speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
20.04.

If you'd like to hear speechSynthesis in action, go to this web page using 
Firefox on Windows 10 or Ubuntu 16.04 (where the instructions will be spoken to 
you using Speech Synthesis web standard):
http://www.lonniebest.com/CardTrick/

20.04 is a Long Term Support release. Please fix this!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BuildID: 20200708170202
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: KDE
Date: Sun Jul 26 03:51:21 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-04-26 (91 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=78.0.2/20200708170202 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76

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


** Tags: amd64 apport-bug focal

** Description changed:

- This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
- Firefox supports the web standard for speechSynthesis, but it doesn't
- work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
- currently work in Window 10. Like I said, it is web standard that should
- work in every browser.
+ This bug is more the fault of the Kubuntu and Ubuntu distribution teams
+ than it is fault of Mozilla. Firefox supports the web standard for
+ speechSynthesis, but it doesn't work in Kubuntu 20.04. This did work in
+ Ubuntu 16.04 and does also currently work in Windows 10. Like I said, it
+ is web standard that should work in every browser. It is a big help to
+ the visually impaired.
  
  To reproduce this bug, open up any web page using Firefox and hit ctrl-
  shift-I (to bring up the console of Firefox). Then, copy and paste the
  following text into the console and press enter:
  
  speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
  speak");
  
  This bug means that all web pages, on the internet, that use
- speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
- 20.04.
+ speechSynthesis cannot be properly used Kubuntu 20.04 LTS and Ubuntu
+ 20.04 LTS.
  
- If you'd like to hear speechSynthesis in action, go to this web page using 
Firefox on Windows 10 or Ubuntu 16.04:
+ If you'd like to hear speechSynthesis in action, go to this web 

[Desktop-packages] [Bug 1792300] Re: Speech Synthesis Not Working

2020-07-26 Thread Lonnie Lee Best
User activation has been added to my trick for Chromium:
http://www.lonniebest.com/CardTrick/

As Olivier pointed out, the issue remains that speechSynthesis (a web
standard that major browsers support in other operating systems) is not
working Kubuntu 20.04 or Ubuntu 20.04. These are long term support
releases. Where is the support? I reported this two years ago. What
about the visual impaired people that depend on speechSynthesis?

To reproduce this bug, open Chromium on any web page and then hit ctrl-shift-I. 
At the console type (or copy/paste):
speechSynthesis.speak(new SpeechSynthesisUtterance("Testing 1 2 3"));

If you do not hear your browser speak "Testing 1 2 3", the bug is not
fixed. Try the same test on Windows 10 to experience speechSynthesis
working as expected.

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

Title:
  Speech Synthesis Not Working

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04.5, Firefox supports Speech Synthesis by utilizing
  Text-To-Speech voices provided by default from the operating system.

  In Windows 10, both both Firefox and Chrome support Speech Synthesis
  by utilizing Text-To-Speech voices provided by default from the
  operating system.

  However,in Chromium 68 and 69, although the API is supported, Chromium
  cannot speak, because it doesn't seem to know how to load those Text-
  To-Speech voices that Firefox is successfully utilizing.

  Here's what users said at Ask Ubuntu, regarding the issue:
  https://askubuntu.com/questions/761975/

  For example, this page should speak the text is shows:
  http://www.lonniebest.com/CardTrick/

  The link above does not work in Chromium 69 on Ubuntu, however it does
  work in the following browser/os combinations:

  - Firefox (Ubuntu 16.04.5)
  - Chrome (Windows 10)
  - Firefox (Windows 10)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 00:38:53 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Load-Avg-1min: 0.51
  Load-Processes-Running-Percent:   0.1%
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c57c4be3-fe0f-4162-804e-627e28920546 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1888983] [NEW] Suspend notification wakes external monitor.

2020-07-26 Thread lb design
Public bug reported:

Right before my laptop suspends gnome-shell shows a notification
"Automatic suspend - Computer will suspend very soon because of
inactivity"  https://i.imgur.com/b4SxVk2.png

That notification wakes my external monitor only to present itself then
suspends the laptop leaving the monitor to restart it's 30 min. turn off
cycle. There should be a way to disable that notification.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 26 10:31:51 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-31 (116 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/1888983/+attachment/5395882/+files/image.png

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

Title:
  Suspend notification wakes external monitor.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Right before my laptop suspends gnome-shell shows a notification
  "Automatic suspend - Computer will suspend very soon because of
  inactivity"  https://i.imgur.com/b4SxVk2.png

  That notification wakes my external monitor only to present itself
  then suspends the laptop leaving the monitor to restart it's 30 min.
  turn off cycle. There should be a way to disable that notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 10:31:51 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-31 (116 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1738774]

2020-07-26 Thread Stéphane Guillou
*** Bug 131946 has been marked as a duplicate of this bug. ***

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions

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


[Desktop-packages] [Bug 1888975] Re: Double click on a window's titlebar is transferred to desktop

2020-07-26 Thread Arham Amouei
** Description changed:

  Hi. In ubuntu 20.04, whenever I double click on the titlebar of the
  window of some programs (including: firefox, simplenote, geany, visual
  studio code, etc.; excluding gedit, evince, nautilus, etc.), the double
- click is transferred to the desktop. For example, if behind the
- titlebar, at the  (X,Y) position of mouse pointer, there is a folder
- icon on my desktop, that folder gets opened.
+ click is transferred to the desktop. For example, if behind the titlebar
+ of firefox, at the  (X,Y) position of mouse pointer, there is a folder
+ icon on my desktop, that folder gets opened after firefix window is
+ maximized/unmaximized.
  
  However, if right behind the titlebar there is another window (not
  desktop), the double click is not transferred to that window or to
  desktop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 10:02:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics Controller [1043:1863]
     Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics Controller [1043:1863]
  InstallationDate: Installed on 2020-04-19 (97 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  MachineType: ASUSTeK Computer Inc. F82Q
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F82Q
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: F82Q
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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

** Description changed:

  Hi. In ubuntu 20.04, whenever I double click on the titlebar of the
  window of some programs (including: firefox, simplenote, geany, visual
- studio code, etc.; excluding gedit, evince, nautilus, etc.), the double
+ studio code, etc.; excluding: gedit, evince, nautilus, etc.), the double
  click is transferred to the desktop. For example, if behind the titlebar
  of firefox, at the  (X,Y) position of mouse pointer, there is a folder
  icon on my desktop, that folder gets opened after firefix window is
  maximized/unmaximized.
  
  However, if right behind the titlebar there is another window (not
  desktop), the double click is not transferred to that window or to
  desktop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 10:02:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics Controller [1043:1863]
 

[Desktop-packages] [Bug 1888975] [NEW] Double click on a window's titlebar is transferred to desktop

2020-07-26 Thread Arham Amouei
Public bug reported:

Hi. In ubuntu 20.04, whenever I double click on the titlebar of the
window of some programs (including: firefox, simplenote, geany, visual
studio code, etc.; excluding gedit, evince, nautilus, etc.), the double
click is transferred to the desktop. For example, if behind the
titlebar, at the  (X,Y) position of mouse pointer, there is a folder
icon on my desktop, that folder gets opened.

However, if right behind the titlebar there is another window (not
desktop), the double click is not transferred to that window or to
desktop.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 26 10:02:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics 
Controller [1043:1863]
   Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics 
Controller [1043:1863]
InstallationDate: Installed on 2020-04-19 (97 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
MachineType: ASUSTeK Computer Inc. F82Q
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F82Q
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F82Q
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
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

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


** Tags: amd64 apport-bug focal ubuntu

** Description changed:

- Hi. In ubuntu 20.20, whenever I double click on the titlebar of the
+ Hi. In ubuntu 20.04, whenever I double click on the titlebar of the
  window of some programs (including: firefox, simplenote, geany, visual
  studio code, etc.; excluding gedit, evince, nautilus, etc.), the double
  click is transferred to the desktop. For example, if behind the
  titlebar, at the  (X,Y) position of mouse pointer, there is a folder
  icon on my desktop, that folder gets opened.
  
  However, if right behind the titlebar there is another window (not
  desktop), the double click is not transferred to that window or to
  desktop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 10:02:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics Controller [1043:1863]
-Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics Controller [1043:1863]
+  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated 
Graphics 

[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen

2020-07-26 Thread Ubuntooo
On a Dell Precision 7510 Laptop (nVidia Quadro M2000M) running Ubuntu
18.04 , Marco's workaround in #7, Ctrl+alt+f1 -> Ctrl+alt+f2, works for
me.  I think I'd prefer to wait for Wayland to be fixed rather than
disable it in /etc/gdm3/custom.conf, though.

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

Title:
  GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps
  another not scaled cursor mid screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Showing two cursors after login to ubuntu-desktop.

  One cursor moves and is scaled, and one is stationary mid screen and
  not scaled.

  The moving cursor does not appear on screenshots, making it difficult
  to upload a screenshot.

  Previously reported:
  https://gitlab.gnome.org/GNOME/mutter/issues/904
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428

  Package: mutter 3.36.1-3ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

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

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