date:20200517

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

** This bug has been marked a duplicate of bug 1851992
   Lock screen not locking upon resume (org.gnome.desktop.lockdown 
disable-lock-screen set to true for some reason)

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

Title:
  Screen not locked after resume from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Whenever I suspend my laptop, and then resume, I get directly to the
  gnome-shell desktop without having to log in.

  This used to work perfectly before the upgrade to 20.04.

  For information, I'm using pure gnome-shell, not Unity, in case that
  matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv1699 F pulseaudio
   /dev/snd/controlC0:  juloliv1699 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 14:08:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-24 (10 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1876928] Re: no lock screen and no password prompt when laptop lid is opened.

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

** This bug is no longer a duplicate of bug 1876908
   Screen not locked after resume from suspend
** This bug has been marked a duplicate of bug 1851992
   Lock screen not locking upon resume (org.gnome.desktop.lockdown 
disable-lock-screen set to true for some reason)

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

Title:
  no lock screen and no password prompt when laptop lid is opened.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I open my laptop after it being closed whether it's closed for 
minutes or for hours, the system directly logs in without prompting me for a 
password. I have checked all my lock screen related settings and they all seem 
to be set the way they should. I uploaded screenshots of my settings to Imgur 
so you can check and verify: https://imgur.com/a/I3LQvim 
  Sorry I couldn't attach them with this bug report; I am only allowed to 
upload one attachment.
  Please note that this issue doesn't occur when I log out or suspend manually 
(with the laptop lid being open).

  What I expected to happen: 
  I expected the lock screen to show up and to prompt me for password input 
after I open the laptop lid.

  What happened instead: 
  The system directly logs in without the lock screen to show up and without 
attempting me to type in a password after opening my laptop lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver 3.6.1-11ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 15:29:18 2020
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2020-04-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  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/1876928/+subscriptions

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread teimcrr

Yes, but expect some glitches in apps.
In Darktable for example, when hovering on gui elements, tooltips appear 
somewhere else in the screen...

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1879177] Re: Sound cuts off and back on randomly during online streaming of videos

2020-05-17 Thread Siddhant Ahuja

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Sound cuts off and back on randomly during online streaming of videos

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound cuts off and comes back on every 10 or so minutes. I have tried
  the usual stuff like purging and removing alsa and pulseaudio and
  restarting, forcing alsa reload, killing pulseaudio and starting
  again, etc.

  Here is the output from 
  cat /var/log/syslog* | grep -i pulse

  gnome-shell[7674]:
  [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  I have attached alsa information also as an attachment

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

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

[Desktop-packages] [Bug 1879177] [NEW] Sound cuts off and back on randomly during online streaming of videos

You have been subscribed to a public bug:

Sound cuts off and comes back on every 10 or so minutes. I have tried
the usual stuff like purging and removing alsa and pulseaudio and
restarting, forcing alsa reload, killing pulseaudio and starting again,
etc.

Here is the output from 
cat /var/log/syslog* | grep -i pulse

gnome-shell[7674]:
[8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation is
nullptr.

I have attached alsa information also as an attachment

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


** Tags: bot-comment
-- 
Sound cuts off and back on randomly during online streaming of videos
https://bugs.launchpad.net/bugs/1879177
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

That's not a helpful comment.

Many of us actually have never encountered this bug so to say "whole
distro is useless for serious production use" is grossly inaccurate. And even 
those who do encounter this bug would not say it makes Ubuntu "useless".

Please only comment if you have productive, useful, information to add.
And if you continue to experience any problems please report them by
opening a new bug with the command:

  ubuntu-bug mutter

and/or reporting them to the developers at:

  https://gitlab.gnome.org/GNOME/mutter/-/issues


** Summary changed:

- [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 
93)
+ [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 
20.04 (see comment 93)

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

Re: [Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-17 Thread Heikki Moisander

If there is a possibility that copy-paste will result to an error, whole
distro is useless for serious production use.
It is really sad, testing this kind of bug is so uncertain and difficult.
In my opinion programmer should be able to guarantee that such error can
not take place. Otherwise there are something fundamentally wrong in
design.

Sorry, I am a big fan of Ubuntu and would like to see open source success
in office environment, but this bug seems a show stopper for me if
community is incapable of fixing it 100%.

On Mon, 18 May 2020 at 07:05, Adam Dingle  wrote:

> Once again I am the original reporter - Daniel recently asked for my
> opinion about whether this bug has been fixed.
>
> I have now been running with the proposed 3.36.2-1ubuntu1~20.04.1
> package for three days, during which I have done a fair amount of
> editing with copying and pasting.  During that time I saw this
> copy/paste bug occur twice: once on 5/16 when I couldn't copy and paste
> from Epiphany (a web browser) to gedit, and once on 5/17 when I couldn't
> copy and paste from a LibreOffice Writer window into another LibreOffice
> Writer window.
>
> My opinion is that the proposed fix is a definite improvement, because I
> am sure that without it I would have seen more copy/paste failures these
> last few days.  However I believe that the bug is still not completely
> fixed.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1873686).
> https://bugs.launchpad.net/bugs/1852183
>
> Title:
>   [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
>   comment 93)
>
> Status in LibreOffice:
>   Won't Fix
> Status in Mutter:
>   Unknown
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Eoan:
>   Triaged
> Status in mutter source package in Focal:
>   Fix Committed
> Status in mutter source package in Groovy:
>   Fix Released
>
> Bug description:
>   [ Impact ]
>
>   I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.
>
>   In this environment, copy/cut/paste often fails.  Specifically, the
>   paste command sometimes does not paste the text that was cut/copied
>   most recently.  Instead, it pastes text that was cut/copied at some
>   prior time.
>
>   [ Test case ]
>
>   1. Use use libreoffice writer/calc
>   2. Copy text around
>   3. Paste it and ensure it always work
>
>   [ Regression potential ]
>
>   Copy/paste won't work as expected, for non-text types
>
>   -
>
>
>   I use LibreOffice Writer a lot, and I now see this problem very often,
> i.e. many times every day.
>
>   There is some discussion of the problem here:
>
>  https://ask.libreoffice.org/en/question/213510/copypaste-issues-
>   libreoffice-calc/
>
>   Several posters there say that they are also using Ubuntu 19.10.
>
>   Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:
>
>  https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
>   -Clipboard-Manager
>
>   It seems like that could be related.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions
>

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1857656] Re: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1

[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/1857656

Title:
  [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments
  to method Clutter.Actor.destroy: expected 0, got 1

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  1) Ubuntu 19.10
  2) GNOME Shell 3.34.1
  3) No error.
  4) Error in Logs.

  
  12:23:41 PM gnome-shell: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-28 (115 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

Yeah even if this is a partial fix, it sounds like an improvement.

Let's try to release this fix and then the first person still having
problems after it's released can open a new bug by running:

  ubuntu-bug mutter

But please don't do that yet. We want to be sure about which version
gets promoted from 'proposed' to 'updates' first.


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

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

And once again a reminder:

If you are using a virtual machine you may also need to wait for bug
1872527 to be fixed in focal.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-17 Thread Adam Dingle

Once again I am the original reporter - Daniel recently asked for my
opinion about whether this bug has been fixed.

I have now been running with the proposed 3.36.2-1ubuntu1~20.04.1
package for three days, during which I have done a fair amount of
editing with copying and pasting.  During that time I saw this
copy/paste bug occur twice: once on 5/16 when I couldn't copy and paste
from Epiphany (a web browser) to gedit, and once on 5/17 when I couldn't
copy and paste from a LibreOffice Writer window into another LibreOffice
Writer window.

My opinion is that the proposed fix is a definite improvement, because I
am sure that without it I would have seen more copy/paste failures these
last few days.  However I believe that the bug is still not completely
fixed.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot in kernel 5.4, but 5.5.19 has no problem

** Summary changed:

- [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot
+ [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot 
in kernel 5.4, but 5.5.19 has no problem

** No longer affects: mutter (Ubuntu)

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

Title:
  [Ice Lake] 2-second black screen blips when using Chrome or gnome-
  screenshot in kernel 5.4, but 5.5.19 has no problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Im using a HP 14s dq laptop with intel 630 graphics.

  I've tried both the mode setting and xserver-xorg-video-intel drivers,
  both result in the same 2-second black screen blips. The happens
  frequently using chrome, and always when using the gnome screenshot
  utility. Also, during boot teh screen flickers between black screen
  and boot splash a lot.

  setting nomodeset as a grub parameter stops the flickering, but is not
  a feasible solution as brightness can no longer be set.

  kind regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 08:15:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:86c8]
  InstallationDate: Installed on 2020-04-16 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 14s-dq1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.31
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-dq1xxx
  dmi.product.sku: 8BL04EA#ABH
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1878666] Re: Firefox snap is very slow (30 sec) to start

** Summary changed:

- Firefox snap is very slow, when i start it
+ Firefox snap is very slow (30 sec) to start

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

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

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

Title:
  Firefox snap is very slow (30 sec) to start

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap is very slow, when i start it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 19:53:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-25 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/firefox/+bug/1878666/+subscriptions

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

[Desktop-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly

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

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


** This bug has been marked a duplicate of bug 1874217
   [nvidia] Dual monitor setup with secondary monitor in portrait-right mode 
cause tiled windows to occupy 1.5 monitors

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

Title:
  Display settings configures dual display resolution incorrectly

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two displays side-by-side: one that is 2560x1440 in landscape
  and a second that is 1280x1024 in portrait. In earlier versions of
  Ubuntu (definitely in 18.04 and 19.10) I was able to configure this
  using Display Settings in the default windowing environment.

  After upgrading to Ubuntu 20.04 it seems Display Settings is computing
  an incorrect horizontal resolution for the combined display. This
  results in a display that is too wide for the monitors that pans when
  I mouse toward the edges.

  xrandr is reporting that it's trying to make a display that is
  3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume
  something is doing the math before considering the smaller display is
  in portrait instead of landscape.

  here is the output from xrandr:

  $ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
     1280x1024 60.02*+  75.02
     1280x960  60.00
     1152x864  75.00
     1024x768  75.0370.0760.00
     800x600   75.0072.1960.3256.25
     640x480   75.0072.8159.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
     2560x1440 59.95*+
     2048x1152 60.00
     1920x1200 59.88
     1920x1080 60.0059.9450.0029.9725.0023.98
     1680x1050 59.95
     1600x1200 60.00
     1280x1024 75.0260.02
     1280x720  60.0059.9450.00
     1200x960  59.90
     1152x864  75.00
     1024x768  75.0360.00
     800x600   75.0060.32
     720x576   50.00
     720x480   59.94
     640x480   75.0059.9459.93
  DP-5 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
  .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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   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: ubuntu:GNOME
  Date: Sun May 17 20:35:03 2020
  DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
  InstallationDate: Installed on 2018-09-17 (608 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic

[Desktop-packages] [Bug 1878953] Re: Display settings is lost when switching between modes with Super+P

I think this is expected. I think Gnome Shell only remembers one
configuration per set of attached monitors. But intuitively yes that's
annoying if you're only tapping Super+P.


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

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

** Tags added: multimonitor

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

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

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

Title:
  Display settings is lost when switching between modes with Super+P

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

Bug description:
  When switching between modes (built-in only, joint, ...) with Super+P,
  the display settings are lost. That even occurs when selecting already
  selected mode (selecting "joint" while being in "joint" mode).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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:
  ApportVersion: 2.20.11-0ubuntu27
  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: Fri May 15 18:12:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] 
[103c:8611]
  InstallationDate: Installed on 2020-05-11 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ZBook 15 G6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.02.01
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 15
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6CJ09AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.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
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

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

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

Title:
  scaling changes when closing/re-opening the lid

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  scaling changes when closing/re-opening the lid. Seen in bionic.

  My scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

  [ Test case ]

  In a laptop with HiDPI screen, force the scaling to 1:

  Run this and close the lid:
   xprop -spy -root RESOURCE_MANAGER

  Once reopened the value should not change and if it does the
  `Xft.dpi:\t96` value should stay constant, and not change to 192.

  [ Regression potential ]

  Wrong resolution is set for the laptop lid

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

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

[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

This bug is about radeon and Ubuntu 18.04. Please don't discuss Nvidia
here.

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

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 16 19:34:47 2018
  xserver.configfile: default

[Desktop-packages] [Bug 1872230] Re: The left Ctrl key does not work when using pointer location

There is no need to reinstall. You won't get a fix any faster that way.

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

Title:
  The left Ctrl key does not work when using pointer location

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

Bug description:
  I am using 20.04 Focal.

  I am using a US international keyboard layout with dead keys, so that
  I can enter text in many different languages. After I had rebooted my
  system today and so loaded the newest GNOME Shell, the left Ctrl key
  stopped working in the terminal windows and also in emacs, while the
  right Ctrl still works. To get the left Ctrl working again I have to
  switch to a plain US English keyboard layout, without dead keys.

  I have also tried the different alternatives of US International
  keyboard layouts, each of them seems to work as intended but the left
  Ctrl key is not working. Only with plain US English layout I get the
  left Ctrl working.

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

If you want to +1 bugs, please use the green link near the top left of
the page.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

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

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

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

Title:
  gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index ->
  g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.1-1ubuntu1~19.04.1, the problem page at 
https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson

** Description changed:

  I have two displays side-by-side: one that is 2560x1440 in landscape and
  a second that is 1280x1024 in portrait. In earlier versions of Ubuntu
- (definitely in 19.04 and 19.10) I was able to configure this using
+ (definitely in 18.04 and 19.10) I was able to configure this using
  Display Settings in the default windowing environment.
  
  After upgrading to Ubuntu 20.04 it seems Display Settings is computing
  an incorrect horizontal resolution for the combined display. This
  results in a display that is too wide for the monitors that pans when I
  mouse toward the edges.
  
  xrandr is reporting that it's trying to make a display that is 3840x1440
  (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is
  doing the math before considering the smaller display is in portrait
  instead of landscape.
  
  here is the output from xrandr:
  
  $ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
-1280x1024 60.02*+  75.02  
-1280x960  60.00  
-1152x864  75.00  
-1024x768  75.0370.0760.00  
-800x600   75.0072.1960.3256.25  
-640x480   75.0072.8159.94  
+    1280x1024 60.02*+  75.02
+    1280x960  60.00
+    1152x864  75.00
+    1024x768  75.0370.0760.00
+    800x600   75.0072.1960.3256.25
+    640x480   75.0072.8159.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
-2560x1440 59.95*+
-2048x1152 60.00  
-1920x1200 59.88  
-1920x1080 60.0059.9450.0029.9725.0023.98  
-1680x1050 59.95  
-1600x1200 60.00  
-1280x1024 75.0260.02  
-1280x720  60.0059.9450.00  
-1200x960  59.90  
-1152x864  75.00  
-1024x768  75.0360.00  
-800x600   75.0060.32  
-720x576   50.00  
-720x480   59.94  
-640x480   75.0059.9459.93  
+    2560x1440 59.95*+
+    2048x1152 60.00
+    1920x1200 59.88
+    1920x1080 60.0059.9450.0029.9725.0023.98
+    1680x1050 59.95
+    1600x1200 60.00
+    1280x1024 75.0260.02
+    1280x720  60.0059.9450.00
+    1200x960  59.90
+    1152x864  75.00
+    1024x768  75.0360.00
+    800x600   75.0060.32
+    720x576   50.00
+    720x480   59.94
+    640x480   75.0059.9459.93
  DP-5 disconnected (normal left inverted right x axis y axis)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
  .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.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
-  GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
+  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: ubuntu:GNOME
  Date: Sun May 17 20:35:03 2020
  DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
+  NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
  InstallationDate: Installed on 2018-09-17 (608 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUS All Series
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-

[Desktop-packages] [Bug 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot

2020-05-17 Thread Christopher Chafin

I have the same exact problem, on Kubuntu 20.04 with Dell XPS 13 9300,
using another kernel does fix it, but I have no wifi as a result and
couldn't seem to solve that myself.

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

Title:
  [Ice Lake] 2-second black screen blips when using Chrome or gnome-
  screenshot

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Im using a HP 14s dq laptop with intel 630 graphics.

  I've tried both the mode setting and xserver-xorg-video-intel drivers,
  both result in the same 2-second black screen blips. The happens
  frequently using chrome, and always when using the gnome screenshot
  utility. Also, during boot teh screen flickers between black screen
  and boot splash a lot.

  setting nomodeset as a grub parameter stops the flickering, but is not
  a feasible solution as brightness can no longer be set.

  kind regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 08:15:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:86c8]
  InstallationDate: Installed on 2020-04-16 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 14s-dq1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.31
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-dq1xxx
  dmi.product.sku: 8BL04EA#ABH
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

As suggested in comment #8, please try disabling voice prompts. That
seems to work on a variety of Bose devices:

  https://www.bose.com/en_us/support/article/disabling-voice-prompts-
soundlink-mini-ii.html

If you would like to discuss the problem further then it would probably
be best to report it to the developers here:

  BlueZ: 
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth
  PulseAudio: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

No one has yet(?)

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

Sounds like a good workaround. That's what the Randr fractional scaling
patch is *meant* to do.

I think you can hack/script those same settings with:

  xrandr --fb WIDTHxHEIGHT

or

  xrandr --output OUTPUT --scale-from WIDTHxHEIGHT

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1879122] Re: Cannot enable wifi hotspot on the first attempt

2020-05-17 Thread Thomas

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

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

Title:
  Cannot enable wifi hotspot on the first attempt

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

Bug description:
  after open gnome control centre i canot "enable hotspot" i must click
  on another item etc. "Network" and I must go back to previous item
  "Wifi" and then is able to "enable hotspot"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 08:09:05 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-05-07 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.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/1879122/+subscriptions

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

To roll back:

  sudo apt install --reinstall PACKAGENAME1/focal PACKAGENAME2/focal ...

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1878592] Re: super key problem

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

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


** This bug has been marked a duplicate of bug 1871913
   super key does not work with secondary keyboard layout

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

Title:
  super key problem

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  in farsi language super key not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.19
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 15:22:42 2020
  InstallationDate: Installed on 2020-05-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-05-11 (2 days ago)

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

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

[Desktop-packages] [Bug 1879209] [NEW] Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson

Public bug reported:

I have two displays side-by-side: one that is 2560x1440 in landscape and
a second that is 1280x1024 in portrait. In earlier versions of Ubuntu
(definitely in 19.04 and 19.10) I was able to configure this using
Display Settings in the default windowing environment.

After upgrading to Ubuntu 20.04 it seems Display Settings is computing
an incorrect horizontal resolution for the combined display. This
results in a display that is too wide for the monitors that pans when I
mouse toward the edges.

xrandr is reporting that it's trying to make a display that is 3840x1440
(2560+1280) instead of 3584x1440 (2560+1024), so I assume something is
doing the math before considering the smaller display is in portrait
instead of landscape.

here is the output from xrandr:

$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
   1280x1024 60.02*+  75.02  
   1280x960  60.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.3256.25  
   640x480   75.0072.8159.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
   2560x1440 59.95*+
   2048x1152 60.00  
   1920x1200 59.88  
   1920x1080 60.0059.9450.0029.9725.0023.98  
   1680x1050 59.95  
   1600x1200 60.00  
   1280x1024 75.0260.02  
   1280x720  60.0059.9450.00  
   1200x960  59.90  
   1152x864  75.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0059.9459.93  
DP-5 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
.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.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
 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: ubuntu:GNOME
Date: Sun May 17 20:35:03 2020
DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
InstallationDate: Installed on 2018-09-17 (608 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago)
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: Z97-PRO(Wi-Fi ac)
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.:rnZ97-PRO(Wi-Fiac):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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Desktop-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly

2020-05-17 Thread Chris Anderson

** Attachment added: "Display Settings 2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879209/+attachment/5373107/+files/Screenshot%20from%202020-05-17%2020-44-29.png

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

Title:
  Display settings configures dual display resolution incorrectly

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two displays side-by-side: one that is 2560x1440 in landscape
  and a second that is 1280x1024 in portrait. In earlier versions of
  Ubuntu (definitely in 19.04 and 19.10) I was able to configure this
  using Display Settings in the default windowing environment.

  After upgrading to Ubuntu 20.04 it seems Display Settings is computing
  an incorrect horizontal resolution for the combined display. This
  results in a display that is too wide for the monitors that pans when
  I mouse toward the edges.

  xrandr is reporting that it's trying to make a display that is
  3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume
  something is doing the math before considering the smaller display is
  in portrait instead of landscape.

  here is the output from xrandr:

  $ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y 
axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 
0/0/0/0
 1280x1024 60.02*+  75.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   75.0072.1960.3256.25  
 640x480   75.0072.8159.94  
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0059.9450.0029.9725.0023.98  
 1680x1050 59.95  
 1600x1200 60.00  
 1280x1024 75.0260.02  
 1280x720  60.0059.9450.00  
 1200x960  59.90  
 1152x864  75.00  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   59.94  
 640x480   75.0059.9459.93  
  DP-5 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia wl
  .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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   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: ubuntu:GNOME
  Date: Sun May 17 20:35:03 2020
  DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546]
  InstallationDate: Installed on 2018-09-17 (608 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago)
  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: Z97-PRO(Wi-Fi ac)
  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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-05-17 Thread Matt Lee

HW acceleration doesn't work for me in the latest build. I noted that
Olivier was going to build with a newer version of libva so I went ahead
an installed the latest version, as per this guide:
https://github.com/intel/media-driver/wiki/How-to-build-and-use-media-
driver%3F. Unfortunately that did not change the behavior, so I still
see kVideoDecoderName="VpxVideoDecoder"

snap info --abs-time chromium & vainfo dumps below:

name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical*
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/vaapi
refresh-date: 2020-05-17T17:46:48-07:00
channels:
  latest/stable:81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB -
  latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB -
  latest/beta:  83.0.4103.56  2020-05-15T02:46:16Z (1155) 163MB -
  latest/edge:  84.0.4143.2   2020-05-13T04:57:20Z (1154) 164MB -
installed:  81.0.4044.138  (1162) 162MB -

libva info: VA-API version 1.8.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.8 (libva 2.1.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.2.pre 
(f403839f)
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Beta Chromium 80 Snap with vaapi enabled :

  https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
  source-enable-
  vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap

  Install it with --devmode

  
  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD

[Desktop-packages] [Bug 1879203] Re: combination Super + Space do not switch to another language

2020-05-17 Thread imelnyk1347

** Description changed:

  After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding to
  the switching command.
+ 
+ gnome-shell (3.36.1-5ubuntu2)
  
  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

Title:
  combination Super + Space do not switch to another language

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding
  to the switching command.

  gnome-shell (3.36.1-5ubuntu2)

  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

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

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

2020-05-17 Thread Stefano Dall'Agata

Public bug reported:

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

Description:Ubuntu 20.04 LTS
Release:20.04

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

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


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

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

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

2020-05-17 Thread Stefano Dall'Agata

These problems are highlighted with hplip-gui diagnostics:

DeskJet-3630

Type: Printer
Device URI: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
PPD: /etc/cups/ppd/DeskJet-3630.ppd
warning: Failed to read /etc/cups/ppd/DeskJet-3630.ppd ppd file
PPD Description: 
Printer status: la stampante DeskJet-3630 è inattiva.  è stata abilitata da lun 
18 mag 2020, 02:12:27
error: Unable to communicate with device (code=12): 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
error: Device not found
error: Communication status: Failed


--
| PERMISSION |
--


Checking Permissions


Checking for Configured Queues
warning: Fail to read ppd=/etc/cups/ppd/DeskJet-3630.ppd file
warning: Insufficient permission to access file /etc/cups/ppd/DeskJet-3630.ppd
warning: Could not complete Queue(s) configuration check


Checking for HP Properitery Plugin's
No plug-in printers are configured.
 

Checking for Printer Status
error: 'DeskJet-3630' Printer is either Powered-OFF or Failed to communicate.
Turn On Printer and re-run hp-doctor

Diagnose completed...

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

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

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

2020-05-17 Thread Stefano Dall'Agata

In another partition that I keep for testing, I had made a clean
installation of 20.04 and after installing hplip the same printer works
without problems.

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

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

[Desktop-packages] [Bug 1879203] Re: combination Super + Space do not switch to another language

2020-05-17 Thread imelnyk1347

** Description changed:

- After update Linux(04/20), switching the language combination stopped
+ After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding to
  the switching command.
  
  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

Title:
  combination Super + Space do not switch to another language

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding
  to the switching command.

  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

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

[Desktop-packages] [Bug 1879203] [NEW] combination Super + Space do not switch to another language

2020-05-17 Thread imelnyk1347

Public bug reported:

After update Linux(04/20), switching the language combination stopped
working correctly Super + Space. At one time, the switching works
correctly, but at the same moment it may immediately stop responding to
the switching command.

Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

** Description changed:

- After the Linux update (04/20), switching the language combination
- stopped working correctly Super + Space. At one time, the switching
- works correctly, but at the same moment it may immediately stop
- responding to the switching command.
+ After update Linux(04/20), switching the language combination stopped
+ working correctly Super + Space. At one time, the switching works
+ correctly, but at the same moment it may immediately stop responding to
+ the switching command.
  
  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

Title:
  combination Super + Space do not switch to another language

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After update Linux(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding
  to the switching command.

  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread Faraz Khan

@Teimcrr: YOU are a life saver. The viewport hack works amazingly well

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1065126] Re: "Always do this from now on" does not work

2020-05-17 Thread Mathew Hodson

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

** Bug watch removed: Mozilla Bugzilla #160144
   https://bugzilla.mozilla.org/show_bug.cgi?id=160144

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

Title:
  "Always do this from now on" does not work

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Downloading an unknown file type in Firefox displays a dialog for choosing 
which application to use for opening the file.
  The dialog contains a check box labelled "Always do this action from now on".
  Checking this option does not work: When I download a file of the same type 
next time, the same dialog is displayed again.

  This feature is broken for as long as I can remember (> 10 years).
  It's time it was fixed (or removed).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 15.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruediger   2536 F pulseaudio
  BuildID: 20120907231657
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49'
     Mixer name : 'Analog Devices AD1984'
     Components : 'HDA:11d41984,17aa20bb,00100400'
     Controls  : 32
     Simple ctrls  : 20
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
     Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Channel: Unavailable
  Date: Wed Oct 10 18:17:44 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 172.31.0.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   172.31.0.0/20 dev wlan0  proto kernel  scope link  src 172.31.9.26  metric 2
  MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
   icedtea-6-plugin  1.2-2ubuntu1.2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 6457BBG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6457BBG
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1879193] [NEW] folder with applications freezes

Public bug reported:

when placing applications in the folder the screen freezes, when
removing the folder, the screen freezes

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 18:43:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
InstallationDate: Installed on 2020-05-17 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ZMAX MOBILE 8100 B
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2011
dmi.bios.vendor: Insyde
dmi.bios.version: F.0D
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NCL60/61
dmi.board.vendor: Compal
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: MOBILE 8100 B
dmi.product.sku: Calpella_Fab
dmi.product.version: F01
dmi.sys.vendor: ZMAX
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Description changed:

- when placing applications in folder the screen freezes, when renaming
- the folder the screen freezes
+ when placing applications in the folder the screen freezes, when
+ removing the folder, the screen freezes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 18:43:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
-Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
+  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
+    Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ZMAX MOBILE 8100 B
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NCL60/61
  dmi.board.vendor: Compal
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: MOBILE 8100 B
  dmi.product.sku: Calpella_Fab
  dmi.product.version: F01
  dmi.sys.vendor: ZMAX
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core:

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-17 Thread Mohammad Ali Toufighi

You can upgrade only related packages (Taken from
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1):

mutter
mutter-common
libmutter-6-0
gir1.2-mutter-6

To rollback, remove proposed packages from your sources.list. Then, run
apt-update and install them.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues

2020-05-17 Thread Eric Jacolin

Same problem installing 3.20.5 on Ubuntu 20.04 (after an upgrade from 18.04)
Looks like hplip uses Python 2.7, but the python-pyqt5 package (Python 2 
bindings for Qt5) is no longer available in the distro.
The corresponding package for Python3 is python3-pyqt5, which is available

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

Title:
  Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip
  issues

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  Hi,
   
  I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04,
  Spent some time troubleshooting with the default (previously current) drivers 
hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially 
due to missing dependencies. Errors about missing pyqt4 dependencies among 
others.

  When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found
  but fails to print.

  Just noticed similar bug filed, 690720 , and saw note that new hplip
  ver. 3.20.5 was just released and supports Ubuntu 20.04

  When trying to install new package hplip ver. 3.20.5 with the .run
  script provided by HP I am unable to complete installatoin as it
  reports unmet dependency of pyqt5 , even though package python3-pyqt5
  is installed on system.

  https://developers.hp.com/hp-linux-imaging-and-printing/gethplip

  Maybe the repo just needs to be updated with a newer build (3.20.5) to
  install on my system, or is there something that can be done in the
  meantime.

  Below hp-check -t when using the repo hplip ver. 3.20.3 ,

  ==
  Saving output in log file: /root/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-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
GNU/Linux
   Host: judith-mini
   Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux
   Distribution: ubuntu 20.04
   Bitness: 64 bit

[Desktop-packages] [Bug 1869522] Re: Simple Scan doesn't work

2020-05-17 Thread Charles

Thanks for the response.  "Bug" was resolved by Bartosz, reference:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524

now when I run $ which simple-scan
the result is:
/usr/bin/simple-scan
as expected.
When I run $ ldd -r /usr/bin/simple-scan
the result is:
linux-vdso.so.1 (0x7ffe617db000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7febc9a62000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7febc974b000)
libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7febc8e43000)
libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7febc8b4d000)
libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 
(0x7febc883)
libgdk_pixbuf-2.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7febc860c000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7febc826d000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7febc8019000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7febc7dfc000)
libgusb.so.2 => /usr/lib/x86_64-linux-gnu/libgusb.so.2 
(0x7febc7bee000)
libsane.so.1 => /usr/lib/x86_64-linux-gnu/libsane.so.1 
(0x7febc79bf000)
libcolord.so.2 => /usr/lib/x86_64-linux-gnu/libcolord.so.2 
(0x7febc779f000)
libpackagekit-glib2.so.18 => 
/usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 (0x7febc7543000)
libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6 
(0x7febc72da000)
libwebpmux.so.3 => /usr/lib/x86_64-linux-gnu/libwebpmux.so.3 
(0x7febc70d)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7febc6cdf000)
/lib64/ld-linux-x86-64.so.2 (0x7febca06b000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7febc6a6d000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7febc684e000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7febc664a000)
libpangocairo-1.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7febc643d000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7febc6105000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7febc5ef5000)
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 
(0x7febc5cef000)
libcairo-gobject.so.2 => 
/usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7febc5ae6000)
libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7febc58c)
libatk-bridge-2.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x7febc568f000)
libepoxy.so.0 => /usr/lib/x86_64-linux-gnu/libepoxy.so.0 
(0x7febc538e000)
libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 
(0x7febc5178000)
libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7febc4f2b000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7febc4ce6000)
libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 
(0x7febc4ae3000)
libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 
(0x7febc48d8000)
libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 
(0x7febc46ce000)
libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 
(0x7febc44cb000)
libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 
(0x7febc42c8000)
libxkbcommon.so.0 => /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0 
(0x7febc4089000)
libwayland-cursor.so.0 => 
/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0 (0x7febc3e81000)
libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 
(0x7febc3c7f000)
libwayland-client.so.0 => 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x7febc3a7)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x7febc385e000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7febc3656000)
libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7febc33b1000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7febc30fd000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7febc2ecb000)
libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 
(0x7febc2cc8000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x7febc2aa)
libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 
(0x7febc2893000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 
(0x7febc2689000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7febc2461000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7febc2246000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2020-05-17 Thread M M

I've had this issue since 16.04. How is it that we've gone through 3 LTS
releases without a fix? What is the technical challenge with getting a
Bluetooth LE headset paired for use as a headset? What is going on?

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[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-05-17 Thread Nathan

I have also been affected by this bug on 20.04

-- 
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 1878201] Re: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection

2020-05-17 Thread tecywiz121

Following the instructions here
https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1575078/comments/17 seems to have worked, at least for 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/1878201

Title:
  [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No
  playback when selecting "Headset" after headset connection

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded to ubuntu 20, worked fine with 18.

  When I plug in my hyperX headset, the sound does not work when I select 
Headset, even if I change back and forth with the speakers in the settings. 
  It works perfectly if I select Headphones, and I can then select my headset 
microphone as a workaround.

  Thanks for the great work!

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aurelien   2334 F pulseaudio
   /dev/snd/pcmC0D0c:   aurelien   2334 F...m pulseaudio
   /dev/snd/pcmC0D0p:   aurelien   2334 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 14:19:43 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79+berline+X00
  InstallationDate: Installed on 2020-03-03 (69 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago)
  dmi.bios.date: 02/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0WWHJ2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5540
  dmi.product.sku: 0906
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1878201] Re: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection

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

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

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

Title:
  [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No
  playback when selecting "Headset" after headset connection

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded to ubuntu 20, worked fine with 18.

  When I plug in my hyperX headset, the sound does not work when I select 
Headset, even if I change back and forth with the speakers in the settings. 
  It works perfectly if I select Headphones, and I can then select my headset 
microphone as a workaround.

  Thanks for the great work!

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aurelien   2334 F pulseaudio
   /dev/snd/pcmC0D0c:   aurelien   2334 F...m pulseaudio
   /dev/snd/pcmC0D0p:   aurelien   2334 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 14:19:43 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79+berline+X00
  InstallationDate: Installed on 2020-03-03 (69 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago)
  dmi.bios.date: 02/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0WWHJ2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5540
  dmi.product.sku: 0906
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

2020-05-17 Thread Daniel Letzeisen

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

** Tags removed: gstreamer-error

** Description changed:

  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d
  
  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52
  
  Should Xubuntu default to a different camera program, such as guvcview?
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: cheese 3.34.0-1build1
- ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
- Uname: Linux 5.4.0-29-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: XFCE
- Date: Sun May 17 14:10:31 2020
- InstallationDate: Installed on 2020-04-23 (23 days ago)
- InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
- MachineType: innotek GmbH VirtualBox
- RelatedPackageVersions:
-  cheese3.34.0-1build1
-  cheese-common 3.34.0-1build1
- SourcePackage: linux
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 12/01/2006
- dmi.bios.vendor: innotek GmbH
- dmi.bios.version: VirtualBox
- dmi.board.name: VirtualBox
- dmi.board.vendor: Oracle Corporation
- dmi.board.version: 1.2
- dmi.chassis.type: 1
- dmi.chassis.vendor: Oracle Corporation
- dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
- dmi.product.family: Virtual Machine
- dmi.product.name: VirtualBox
- dmi.product.version: 1.2
- dmi.sys.vendor: innotek GmbH
- lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  New

Bug description:
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

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

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

[Desktop-packages] [Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone

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

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

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

Title:
  Rhythmbox crashes when trying to connect to iPhone

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and 
Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. 
  I opened Rhythmbox from the terminal to see the error and I got this

  ```
  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-repeat can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)

  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-shuffle can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)
  **
  Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion 
failed: (strlen (uri) >= 46)
  Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: 
assertion failed: (strlen (uri) >= 46)
  [1]15045 abort (core dumped)  rhythmbox
  ```

  Details of the current system:

  ```
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  ```

  ```
  apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.3-2ubuntu1
Candidate: 3.4.3-2ubuntu1
Version table:
   *** 3.4.3-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  ```

  What I expected to happen:
  I was expected Rhythmbox to show my iPhone under "devices"

  What actually happned:
  Rhythmbox just crashed

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

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

[Desktop-packages] [Bug 1879183] [NEW] Cheese does not show preferences/options/menus to non-GNOME Users

You have been subscribed to a public bug:

Cheese has removed the GUI method of accessing preferences for non-GNOME users.
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

I'm not sure if upstream cheese devs care enough to fix it:
https://gitlab.gnome.org/GNOME/cheese/-/issues/62
https://gitlab.gnome.org/GNOME/cheese/-/issues/52

Should Xubuntu default to a different camera program, such as guvcview?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cheese 3.34.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun May 17 14:10:31 2020
InstallationDate: Installed on 2020-04-23 (23 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: innotek GmbH VirtualBox
RelatedPackageVersions:
 cheese3.34.0-1build1
 cheese-common 3.34.0-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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


** Tags: amd64 apport-bug focal gstreamer-error
-- 
Cheese  does not show preferences/options/menus to non-GNOME Users
https://bugs.launchpad.net/bugs/1879183
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cheese in Ubuntu.

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

[Desktop-packages] [Bug 1870847] Re: App grid has too many page dots on right

2020-05-17 Thread Saeed

It occurs on my laptop too:
Asus k56cb
Ubuntu 20.04 LTS
GNOME Version: 3.36.2
Uname: Linux k56cb 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  App grid has too many page dots on right

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

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879182] [NEW] Sound cuts off and back on randomly during online streaming of videos

2020-05-17 Thread Siddhant Ahuja

Public bug reported:

Sound shuts off and turns back on again with two pop clicks. When the
sound is off, if i turn up the volume to the max, i can hear crackling
sound in speakers in tune with sound playing on the computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  siddahuja  31829 F pulseaudio
 /dev/snd/controlC0:  siddahuja  31829 F pulseaudio
 /dev/snd/pcmC0D0p:   siddahuja  31829 F...m pulseaudio
 /dev/snd/timer:  siddahuja  31829 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 23:56:27 2020
InstallationDate: Installed on 2020-04-27 (20 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: 10/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-Gaming 3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
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.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z170X-Gaming 3
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821

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


** Tags: amd64 apport-bug focal

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+attachment/5373017/+files/CurrentDmesg.txt

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

Title:
  Sound cuts off and back on randomly during online streaming of videos

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound shuts off and turns back on again with two pop clicks. When the
  sound is off, if i turn up the volume to the max, i can hear crackling
  sound in speakers in tune with sound playing on the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddahuja  31829 F pulseaudio
   /dev/snd/controlC0:  siddahuja  31829 F pulseaudio
   /dev/snd/pcmC0D0p:   siddahuja  31829 F...m pulseaudio
   /dev/snd/timer:  siddahuja  31829 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 23:56:27 2020
  InstallationDate: Installed on 2020-04-27 (20 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: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170X-Gaming 3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821

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

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

[Desktop-packages] [Bug 1879053] Re: Fractional Upscaling is descaling Certain Apps

2020-05-17 Thread Tobi M.

additional information: another app affected by that issue is spotify.

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

Title:
  Fractional Upscaling is descaling Certain Apps

Status in mutter package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04
  2) wine-development:
    Installed: 5.5-3ubuntu1
    Candidate: 5.5-3ubuntu1
  Same goes for wine stable 5.0.
  Other Packages foxit 2.4.4.xx, Notepad v7.8.6

  3) I'm using a relatively small QHD Display. The Fractional Scaling
  Feature is really something I've looked forward to and I'm super
  grateful that it has been implemented. With my setup my life gets
  easier when having a little zoom but still have a good amount of
  pixels and nice sharpness on my workspace :D

  4) With some apps the fractional scaling has an opposite effect. For
  example wine apps and foxit reader appear tiny with fractional scaling
  turned on (I'm using 125%) and the apps shrink compared to 100%.

  Is this the right place to report the bug or do i need to make a
  bugreport for every specific app?

  Kind regards,
  Tobi

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

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

[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2020-05-17 Thread kkivi

19.10->20.04 the same thing.
It is happened not to be a loop but a series of identical messages from 
different packages. I package name should be included int the messages,
to help user better understand the issue

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-17 Thread erio

can someone explain how to set proposed and update just this package AND
how to rollback? After enabling proposed I get `78 packages can be
upgraded`. The rollback part is important for me since this is my work
environment and this bug can't be tested in a VM because of bug 1872527.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key

2020-05-17 Thread razor7

Hi! At time of writing, applying the patch results in moving the desktop
file/folder to trash, but no difference with **shift+delete** (it also
moves the file to the trash)

To apply the patch intermediately instead of waiting to the release of
the updated package, you can follow this steps.

If you followed https://gitlab.gnome.org/GNOME/nautilus/issues/158
#alternative-solution, you may need these extra steps:

 - rm ~/.config/autostart/nemo-autostart-with-gnome.desktop
 - sudo apt-get purge nemo
 - sudo apt autoremove -y
 - sudo apt install --reinstall gnome-shell-extension-desktop-icons

Then edit this two files:

 - In a terminal: sudo nautilus
 - Navigate to /usr/share/gnome-shell/extensions/desktop-icons@csoriano/
 - Open createFolderDialog.js with gedit or similar
 - Copy/Paste 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/raw/8ba06e3f456e211dfeace27bb27221cd375b65de/createFolderDialog.js
 - Open desktopGrid.js with gedit or similar
 - Copy/Paste 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/raw/8ba06e3f456e211dfeace27bb27221cd375b65de/desktopGrid.js

Restart and you're done!

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #158
   https://gitlab.gnome.org/GNOME/nautilus/issues/158

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

Title:
  Can't delete file from desktop by clicking it and hitting delete key

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed

Bug description:
  Just upgraded to 19.10 today. Previously, in 19.04, I could delete a
  file from the desktop by clicking on it and hitting the delete key.
  That no longer works.

  It's probably relevant that it doesn't appear to be possible to direct
  keyboard focus to the desktop itself any longer. When I click on an
  icon on the desktop and then hit the delete key, the keystroke is sent
  to the window that had focus before I clicked. This appears to be true
  regardless of what window focus mode I'm using (Click to Focus, Focus
  on Hover, or Secondary-Click). Note that the description of Secondary-
  Click, "Window is focused when hovered with the pointer. Hovering the
  desktop removes focus from the previous window," does not appear to be
  true. When I select that focus mode and hover my mouse over the
  desktop I remain focused on the previously focused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.4-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:12:42 2019
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use

2020-05-17 Thread Leó Kolbeinsson

This is unchanged in LibreOffice version 6.4.3.2 Build ID 
1:6.4.3-0ubuntu0.20.04.1
on Lubuntu 20.04. - again this only happens in Libre Office and all other apps 
open/edit/save as normal.

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

Title:
  Opening file from Samba share results in Document in Use

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This bug is related to bug # 1430531 however this only occurs when
  Libre Office is on OS with LxQt desktop.

  I am running Lubuntu version 20.04 with all updates installed
  The Libre Office version :
  Version: 6.4.2.2
  Build ID: 1:6.4.2-0ubuntu3
  CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-US
  Calc: threaded

  
  1. connect to share on local network with PCManFM-Qt File Manager 
  2. click on file TEST_Samba.odt 
  3. The Libre Office splash/Logo screen appears for a split second and the 
nothing happens and the file is not opened.
  4. I then right-click on file and select "open with Libre Office Writer
  5. Document in Use" window appears with text:

 Document file 'TEST_Samba.odt' is locked for editing by:

 Unknown User

 Open document read-only or open a copy of the document for editing.

 Open Read-Only Open Copy Cancel

  Screen shot attached..

  Expected results:
 The "TEST_Samba.odt" files is opened in read-write mode, user can edit it.

  Actual results:
 User can't edit original document (see 3-5 above)

  I have tested this on several boxes running Lubuntu 20.04 with the exact same 
results.
  I have also tested this on SparkyLinux LxQT version 5.11 with the same 
results.
  Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing 
and/or saving this file back to the Samba share. 
  Again this occurs only on machines with LXQt desktop.

  Global Samba config is "default"
   Usershare config is:

  $ cat /var/lib/samba/usershares/sameign2
  #VERSION 2
  path=/home/kbeins/Sameign2
  comment=
  usershare_acl=S-1-1-0:F
  guest_ok=n
  sharename=Sameign2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Tue Apr 28 17:51:14 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879170] Re: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2

2020-05-17 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

** Changed in: cups (Ubuntu)
   Status: New => Invalid

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

Title:
  package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed
  cups package post-installation script subprocess returned error exit
  status 2

Status in cups package in Ubuntu:
  Invalid

Bug description:
  i am not able to install unetbooting software

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 17 09:01:42 2020
  DuplicateSignature:
   package:cups:2.3.1-9ubuntu1.1
   Setting up cups (2.3.1-9ubuntu1.1) ...
   Can't locate object method "new" via package 
"Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load 
"Debconf::Element::Noninteractive::Boolean"?) at 
/usr/share/perl5/Debconf/FrontEnd.pm line 68,  line 2.
   dpkg: error processing package cups (--configure):
installed cups package post-installation script subprocess returned error 
exit status 2
  ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  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: cups
  Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed 
cups package post-installation script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.6D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3564
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.sku: D7Z60PC#ACJ
  dmi.product.version: 06911320461610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1879170] Re: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2

2020-05-17 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed
  cups package post-installation script subprocess returned error exit
  status 2

Status in cups package in Ubuntu:
  New

Bug description:
  i am not able to install unetbooting software

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 17 09:01:42 2020
  DuplicateSignature:
   package:cups:2.3.1-9ubuntu1.1
   Setting up cups (2.3.1-9ubuntu1.1) ...
   Can't locate object method "new" via package 
"Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load 
"Debconf::Element::Noninteractive::Boolean"?) at 
/usr/share/perl5/Debconf/FrontEnd.pm line 68,  line 2.
   dpkg: error processing package cups (--configure):
installed cups package post-installation script subprocess returned error 
exit status 2
  ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  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: cups
  Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed 
cups package post-installation script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.6D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3564
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.sku: D7Z60PC#ACJ
  dmi.product.version: 06911320461610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1879170] [NEW] package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2

2020-05-17 Thread hemant

Public bug reported:

i am not able to install unetbooting software

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 17 09:01:42 2020
DuplicateSignature:
 package:cups:2.3.1-9ubuntu1.1
 Setting up cups (2.3.1-9ubuntu1.1) ...
 Can't locate object method "new" via package 
"Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load 
"Debconf::Element::Noninteractive::Boolean"?) at 
/usr/share/perl5/Debconf/FrontEnd.pm line 68,  line 2.
 dpkg: error processing package cups (--configure):
  installed cups package post-installation script subprocess returned error 
exit status 2
ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 2
InstallationDate: Installed on 2020-05-17 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
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: cups
Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups 
package post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.6D
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3564
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 21.47
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion g4 Notebook PC
dmi.product.sku: D7Z60PC#ACJ
dmi.product.version: 06911320461610100
dmi.sys.vendor: Hewlett-Packard

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

Title:
  package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed
  cups package post-installation script subprocess returned error exit
  status 2

Status in cups package in Ubuntu:
  New

Bug description:
  i am not able to install unetbooting software

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 17 09:01:42 2020
  DuplicateSignature:
   package:cups:2.3.1-9ubuntu1.1
   Setting up cups (2.3.1-9ubuntu1.1) ...
   Can't locate object method "new" via package 
"Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load 
"Debconf::Element::Noninteractive::Boolean"?) at 
/usr/share/perl5/Debconf/FrontEnd.pm line 68,  line 2.
   dpkg: error processing package cups (--configure):
installed cups package post-installation script subprocess returned error 
exit status 2
  ErrorMessage: installed cups package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7
  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: cups
  Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed 
cups package post-installation script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present

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

2020-05-17 Thread Josua Dietze

Well, I suppose the maintainers are following this bug report, or at
least they should.

Upstream has confirmed the bug and provided a solution.

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

Title:
  USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

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

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

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

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 16

[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

2020-05-17 Thread Neptilo

In my case, switching to the Nvidia proprietary driver only made things
worse: second screen was not even detected.

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

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 16 19:34:47 2018

[Desktop-packages] [Bug 1879156] Re: Xorg freeze

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  freezing the screen when placing applications such as libreoffice in
  the category of office, games in the category of games, browsers in
  the category of internet, when renewing an application of the category
  the screen freezes, it is only the mouse cursor working having to
  force the shutdown of the notebook.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 09:49:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ZMAX MOBILE 8100 B
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NCL60/61
  dmi.board.vendor: Compal
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: MOBILE 8100 B
  dmi.product.sku: Calpella_Fab
  dmi.product.version: F01
  dmi.sys.vendor: ZMAX
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1879169] [NEW] Thumbs never updated after renaming a bunch of image files

2020-05-17 Thread teo1978

Public bug reported:

I refuse to waste my time reporting this upstream, since Gnome
developers (or at least Nautilus developers) have proven in several
occasions to be a bunch of idiots unable to deal with bug reports (or
with bugs in general). You deal with them.

I had a folder containing a bunch of image files, namely .png files,
named 1.png, 2.png  up to 100.png and more.

I deleted many of them and then renamed the remaining ones to 1.png
through 21.png.

Now I look at the folder and all the thumbs have not been updated. For
example, the thumb of say 5.png is the thumb of the image that used to
be called 5.png before renaming.

Even hitting f5 does not rebuild the thumbs, and if I right-click on the
folder I don't see any option in the context menu to manually force-
rebuild the thumns (which shouldn't be necessary in the first place but
should be something I'd be able to do).

It's obvious that renaming files should invalidate the thumbs cache.
Fucking pathetic.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
CurrentDesktop: Unity
Date: Sun May 17 17:36:04 2020
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'192'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1321x879+1501+562'"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
InstallationDate: Installed on 2013-10-11 (2409 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Thumbs never updated after renaming a bunch of image files

Status in nautilus package in Ubuntu:
  New

Bug description:
  I refuse to waste my time reporting this upstream, since Gnome
  developers (or at least Nautilus developers) have proven in several
  occasions to be a bunch of idiots unable to deal with bug reports (or
  with bugs in general). You deal with them.

  I had a folder containing a bunch of image files, namely .png files,
  named 1.png, 2.png  up to 100.png and more.

  I deleted many of them and then renamed the remaining ones to 1.png
  through 21.png.

  Now I look at the folder and all the thumbs have not been updated. For
  example, the thumb of say 5.png is the thumb of the image that used to
  be called 5.png before renaming.

  Even hitting f5 does not rebuild the thumbs, and if I right-click on
  the folder I don't see any option in the context menu to manually
  force-rebuild the thumns (which shouldn't be necessary in the first
  place but should be something I'd be able to do).

  It's obvious that renaming files should invalidate the thumbs cache.
  Fucking pathetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 17 17:36:04 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'192'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1321x879+1501+562'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (2409 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879156] Re: Xorg freeze

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  freezing the screen when placing applications such as libreoffice in
  the category of office, games in the category of games, browsers in
  the category of internet, when renewing an application of the category
  the screen freezes, it is only the mouse cursor working having to
  force the shutdown of the notebook.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 09:49:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ZMAX MOBILE 8100 B
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NCL60/61
  dmi.board.vendor: Compal
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: MOBILE 8100 B
  dmi.product.sku: Calpella_Fab
  dmi.product.version: F01
  dmi.sys.vendor: ZMAX
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

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

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

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

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

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

2020-05-17 Thread Cedric Rochefolle

That worked, thank you.
I reset to 0 the DisableSwitching configuration /etc/usb_modeswitch.conf
Then I unpack, renamed re-packed the configPack.tar.gz
I inserted the device and it works fine.
Should I submit a request to the "usb-modeswitch-data" package maintainer or 
did you mention you will do it?

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

Title:
  USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1879158] [NEW] congelamento da tela

Public bug reported:

congelamento da tela ao colocar aplicativos como o libreoffice em
categoria de escritorio, jogos na categoria de jogos, navegadores na
categoria de internet, ao renover um aplicativo da categoria a tela
congela, fica somente o cursor do mouse fucionando tendo de forçar o
desligamente do notebook.

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

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

Title:
  congelamento da tela

Status in xorg package in Ubuntu:
  New

Bug description:
  congelamento da tela ao colocar aplicativos como o libreoffice em
  categoria de escritorio, jogos na categoria de jogos, navegadores na
  categoria de internet, ao renover um aplicativo da categoria a tela
  congela, fica somente o cursor do mouse fucionando tendo de forçar o
  desligamente do notebook.

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

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

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

Public bug reported:

freezing the screen when placing applications such as libreoffice in the
category of office, games in the category of games, browsers in the
category of internet, when renewing an application of the category the
screen freezes, it is only the mouse cursor working having to force the
shutdown of the notebook.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 09:49:56 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
InstallationDate: Installed on 2020-05-17 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ZMAX MOBILE 8100 B
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2011
dmi.bios.vendor: Insyde
dmi.bios.version: F.0D
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NCL60/61
dmi.board.vendor: Compal
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: MOBILE 8100 B
dmi.product.sku: Calpella_Fab
dmi.product.version: F01
dmi.sys.vendor: ZMAX
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

** Description changed:

- freezing the screen when placing applications such as libreoffice in the
- category of office, games in the category of games, browsers in the
- category of internet, when renewing an application of the category the
- screen freezes, it is only the cusor working having to force the
- shutdown of the notebook.
+ congelar a tela ao colocar aplicativos como o libreoffice na categoria
+ de escritório, jogos na categoria de jogos, navegadores na categoria de
+ internet, ao renovar um aplicativo da categoria a tela congela.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: xorg 1:7.7+19ubuntu14
- ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
- Uname: Linux 5.4.0-29-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27
- Architecture: amd64
- BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
- CasperMD5CheckResult: skip
- CompositorRunning: None
- CurrentDesktop: ubuntu:GNOME
- Date: Sun May 17 09:49:56 2020
- DistUpgraded: Fresh install
- DistroCodename: focal
- DistroVariant: ubuntu
- ExtraDebuggingInterest: Yes, if not too technical
- GpuHangFrequency: This is the first time
+ ProblemType: Bug 
+ DistroRelease: Ubuntu 20.04 
+ pacote: xorg 1: 7,7 + 19ubuntu14 
+ ProcVersionSign ature: Ubuntu 5.4.0-29.33-generic 5.4.30 
+ Uname: Linux 5.4.0-29-generic x86_64 
+ ApportVersion: 2.20.11-0ubuntu27 
+ Arquitetura: amd64 
+ BootLog: Erro: [Erro 13] Permissão negada: '/var/log/boot.log' 
+ CasperMD5CheckR resultado : pular 
+ CompositorRunning: None 
+ CurrentDesktop: ubuntu: GNOME 
+ Data: Sun 17 de maio 09:49:56 2020 
+ DistUpgraded: Fresh install 
+ DistroCodename: focal 
+ DistroVariant: ubuntu 
+ ExtraDebuggingI interesse: Sim, se não for muito técnico 
+ GpuHangFrequency: Esta é a primeira vez que 
  GraphicsCard:
-  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
-Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics 
Controller [14c0:0051]
- InstallationDate: Installed on 2020-05-17 (0 days ago)
- InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
- MachineType: ZMAX MOBILE 8100 B
-

[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal

2020-05-17 Thread James Swift

I can confirm that under wayland, when my keyboard is disconnected I can
summon the osk by tapping in a text field or swiping up. When the
keyboard is connected, there is no way to summon the osk. There is no
way to summon it under X however.

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

Title:
  On-screen keyboard (OSK) on touch screen does not seem to work at all
  under Xorg in Focal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Focal, the OSK never appears for me under Xorg
  - Does not appear automatically when selecting text fields
  - Cannot be summoned on-demand by swiping up from bottom screen border (which 
worked on Eoan also under Xorg)

  Under Wayland, both these things continued to work after the Focal
  upgrade if the laptop is in tablet mode (but not if it is in regular
  laptop mode - not sure if this changed on upgrade).

  I could repro this on two "2-in-1" fold-able laptops:
  Dell XPS 9575 2-in-1
  Asus Zenbook flip UX561UD.

  (Note: There was an older bug #1760399 about OSK not working under
  Xorg, but this one was fixed in Cosmic)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  8 17:33:36 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (541 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago)

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

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

[Desktop-packages] [Bug 1879153] [NEW] amdgpu prevents poweroff

2020-05-17 Thread Morten Anton Bach Sjøgren

Public bug reported:

Turning off Kubuntu 20.04 stops short of actually powering off the
machine.

The monitors goes into suspend mode, but PC is still powered on and I
have to hold the power button in to turn it off.

I initially suspected an ACPI problem, but I found these two errors in
/var/log/syslog after turning the computer on again:

May 16 02:46:53 desktop kernel: [475329.688676] [ cut here 
]
May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 
dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm 
xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc 
rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm
May 16 02:46:53 desktop kernel: [475329.688783]  mac80211 intel_cstate libarc4 
snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt btusb 
snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev 
input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac 
cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd 
gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea 
sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core 
libahci wmi video pinctrl_cannonlake pinctrl_intel
May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg 
Tainted: GW 5.4.0-29-generic #33-Ubuntu
May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte 
Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 
03/14/2019
May 16 02:46:53 desktop kernel: [475329.688879] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 
48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 
85 56 01 00
May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 
EFLAGS: 00010202
May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 
978c9de001b8 RCX: 
May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 
978c9de001b8 RDI: 9791c8d5
May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: 
bd3c81567554 R09: 
May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: 
 R12: 0001
May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 
9791c8d5 R15: 978c9de001b8
May 16 02:46:53 desktop kernel: [475329.66] FS:  7fe19eb9ca80() 
GS:9791ddb0() knlGS:
May 16 02:46:53 desktop kernel: [475329.67] CS:  0010 DS:  ES:  
CR0: 80050033
May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 
00088a80c006 CR4: 003606e0
May 16 02:46:53 desktop kernel: [475329.68] Call Trace:
May 16 02:46:53 desktop kernel: [475329.688959]  
dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689026]  
dcn20_pipe_control_lock+0x1c/0x20 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689087]  
dc_stream_set_cursor_position+0x128/0x160 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689152]  
handle_cursor_update.isra.0+0x226/0x300 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689217]  
amdgpu_dm_commit_cursors.isra.0+0x60/0x80 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689281]  
amdgpu_dm_commit_planes.constprop.0+0x66d/0xa00 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689283]  ? __kmalloc_node+0x259/0x320
May 16 02:46:53 desktop kernel: [475329.689347]  ? 
dc_resource_state_copy_construct+0x11a/0x150 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689414]

[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal

2020-05-17 Thread James Swift

I am experiencing this issue with my Acer Switch 11 V sw5-173. In 19.10
everything worked as expected. In 20.04 I am unable to summon the osk
whether the keyboard is attached or detached. The only way to enable the
osk is to use the accessibility options in gnome and turn it always on.

This is also being tracked upstream in this mutter ticket:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242

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

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

Title:
  On-screen keyboard (OSK) on touch screen does not seem to work at all
  under Xorg in Focal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Focal, the OSK never appears for me under Xorg
  - Does not appear automatically when selecting text fields
  - Cannot be summoned on-demand by swiping up from bottom screen border (which 
worked on Eoan also under Xorg)

  Under Wayland, both these things continued to work after the Focal
  upgrade if the laptop is in tablet mode (but not if it is in regular
  laptop mode - not sure if this changed on upgrade).

  I could repro this on two "2-in-1" fold-able laptops:
  Dell XPS 9575 2-in-1
  Asus Zenbook flip UX561UD.

  (Note: There was an older bug #1760399 about OSK not working under
  Xorg, but this one was fixed in Cosmic)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  8 17:33:36 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (541 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago)

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

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

[Desktop-packages] [Bug 1878933] Re: Lock screen ignores user input for a few seconds after "Please try again" message

2020-05-17 Thread Thom Wiggers

This bug report is related; but doesn't fully cover OP
https://gitlab.gnome.org/GNOME/gdm/-/issues/181

** Also affects: gdm
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #181
   https://gitlab.gnome.org/GNOME/gdm/-/issues/181

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

Title:
  Lock screen ignores user input for a few seconds after "Please try
  again" message

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

Bug description:
  When I try to unlock my PC from the lock screen, I sometimes enter the
  wrong password. After checking the password (which takes ~1s), the
  lock screen displays the following message:

  "Sorry, that didn't work. Please try again."

  For ~2s after that, keyboard input is ignored, which means that if you
  start typing you password immediately after reading the "try again"
  prompt, the first few characters are discarded and your password is
  incorrect again.

  This is a bad user experience, and I'm not sure what the purpose of
  the delay is.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 16:32:58 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-09 (96 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-10 (4 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread Jesper de Jong

It does have something to do with the NVidia graphics.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread Jesper de Jong

In NVidia X Server Settings, I can switch to Intel graphics. When I do
this and reboot, then fractional scaling works correctly. With NVidia
graphics enabled, it does not work correctly.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread teimcrr

Ubuntu 20.04, nVidia 1060, Dell 2715P 4k

The following settings work for me:
In Display Settings: 
Scale: 200%
Fractional scaling: OFF

In nVidia settings -> xserver display configuration -> advanced
ViewPortIn 5120x2880
ViewPortOut 3840x2160+0+0
Panning: 5120x2880
Save to X configuration file

It gives me 150% scaling and it survives reboot

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-17 Thread Jesper de Jong

This was working fine with the initial release of Focal Fossa, but has
stopped working since a recent update on my Dell XPS 15.

It's an older model (2014) with 3200x1800 screen. I was using 175%
scaling but now it seems to scale everything to 200%, and the Gnome top
bar is too long so the icons on the top right are not visible anymore.

This laptop has both Intel and NVidia graphics. The NVidia X Server
Settings app tells me I have NVidia driver version 390.132 - so it looks
like this does not just happen with NVidia driver 440.64.

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

Title:
[nvidia] Screen scaling 125% gives 200%

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

Bug description:
Procedure used:
1.
Fully updated system via apt update && apt upgrade

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

4.
Select 125% and click the green "use" button top right (it says "Anvend" in
dansih)

5.
Observe that the window has grown a lot, click the "use new settings" button

6.
The window tells me, I am at 200% scaling. The "200%" option is now
highlighted.

7.
Switch back to 100% and file this bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.16
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 09:42:34 2020
InstallationDate: Installed on 2018-01-14 (810 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=da_DK.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1879144] [NEW] Volume output settings reset on analog surround 4.0

2020-05-17 Thread William CHan

Public bug reported:

It seems to be a pulseaudio issue but unsure if it is a settings error.

Version: Ubuntu 20.04 LTS / 20.04
Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
PulseAudio version: 1:13.99.1-1ubuntu3.2

Problem Description:
When manually reduce volume, Balance and Fade level resets when such reduction 
reaches 0 audio output.

This is not the case when I manually mute the audio output (or with a
mute switch)

Intended Outcome:
There should not be any reset at all.

Other information:
It seems to be a problem with pulseaudio. However, I cannot confirm if it is a 
bug from the pulseaudio side or the Ubuntu settings side.

Intended outcome: It should work the same: turning the volume to 0
should not reset the fade settings nor the balance settings.

Check the screencast below for what is going on (youtube link)
(0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

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

** Summary changed:

- Volume output reset settings reset on surround 4.0 
+ Volume output reset settings reset on pulseaudio surround 4.0

** Summary changed:

- Volume output reset settings reset on pulseaudio surround 4.0
+ Volume output settings reset on pulseaudio surround 4.0

** Summary changed:

- Volume output settings reset on pulseaudio surround 4.0
+ Volume output settings reset on analog surround 4.0

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

Title:
  Volume output settings reset on analog surround 4.0

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-05-17 Thread testato

I installed Ubuntu 20.04 on a new hdd and an Nvidia 650TI.  During the 
installation I enabled the use of proprietary drivers and autologin, so the new 
440 drivers are already installed from the first boot. 
Unfortunately the AutoLogin bug is confirmed also on the new Ubuntu LTS and 
therefore imho should have a high priority.
If it can be useful, on the new UbuntuDDE 20.04 the problem does not arise

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1879020] Re: Mouse pointer keeps flashing while fractional scaling is enabled

2020-05-17 Thread Paul White

** Tags added: focal

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

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

Title:
  Mouse pointer keeps flashing while fractional scaling is enabled

Status in mutter package in Ubuntu:
  New

Bug description:
  I'm running 20.04 LTS on Surface Book 2 15',and I connect a external display 
via USB-C dock. I need to use different scaling settings for different 
monitors, so I enabled Fractional Scaling. After that the mouse pointer starts 
flashing all the time, especially in some system apps like settings.
   The internal display is 200% scaling and 100% for the external one.

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

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

[Desktop-packages] [Bug 1879020] [NEW] Mouse pointer keeps flashing while fractional scaling is enabled

You have been subscribed to a public bug:

I'm running 20.04 LTS on Surface Book 2 15',and I connect a external display 
via USB-C dock. I need to use different scaling settings for different 
monitors, so I enabled Fractional Scaling. After that the mouse pointer starts 
flashing all the time, especially in some system apps like settings.
 The internal display is 200% scaling and 100% for the external one.

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


** Tags: bot-comment focal
-- 
Mouse pointer keeps flashing while fractional scaling is enabled
https://bugs.launchpad.net/bugs/1879020
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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

[Desktop-packages] [Bug 1879089] Re: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04

2020-05-17 Thread Paul White

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

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

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1850753
   Ubuntu 19.10 cannot set background to solid color

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

Title:
  Single background colour and colour-gradient options are missing after
  upgrading from 18.04 to 20.04

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The options for selecting a single colour background, or, a colour gradient 
background, are missing in the settings, after upgrading from 18.04LTS to 
20.04LTS. The upgrade was done according to this guide: 
https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/
  Also tried to make a clean install of 20.04LTS on a virtual machine, with the 
same result, those functions are missing.
  Kind regards
  Anton

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

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

[Desktop-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

2020-05-17 Thread Bug Watch Updater

** Changed in: mesa
   Status: Unknown => New

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

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

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

2020-05-17 Thread Leo

** Bug watch added: github.com/KhronosGroup/Vulkan-Tools/issues #403
   https://github.com/KhronosGroup/Vulkan-Tools/issues/403

** Also affects: mesa via
   https://github.com/KhronosGroup/Vulkan-Tools/issues/403
   Importance: Unknown
   Status: Unknown

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

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

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working

2020-05-17 Thread Tom F

The behaviour of Nautilus desktop remains baffling. But I have resolved
the problem on my PC by recreating my user profile and home user folder.

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

Title:
Ubuntu 20.04 Focal Fossa desktop launchers not working

Status in nautilus package in Ubuntu:
Incomplete

Bug description:
Using the procedure here =

https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux

AND OTHERWISE

I have successfully created launchable desktop app shortcuts. But
they stop working: (1) no launch; (2) no right click context to make
launchable; and (3) no app icon. They can even remain in ~/Desktop
but disappear from the desktop view. A logout kills them. Creating
another new launcher is successful and peculiarly triggers the
temporary reactivation of all the others. But euphoria soon dies as
they all revert to inertia later.

My work around at present is to install PCManFM 1.3.1. Navigating to
~/Desktop on PCManFM, my Nautilus created launchers are all visible,
launchable and have the usual colourful app icon features. But they
remain inert in Nautilus.

My Gnome version is: 3.36.1

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

[Desktop-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

2020-05-17 Thread Leo

Got the same outputs:

vulkaninfo
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

vkcube
vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in mesa package in Ubuntu:
  Confirmed

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

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED