[Desktop-packages] [Bug 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION

2020-12-16 Thread Luke Gopher
I Confirm that bug on Ubuntu Focal with release
:1:78.5.1+build1-0ubuntu0.20.04.1

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

Title:
  Lightning: Cannot dismiss reminders. Got a VALUE parameter with an
  illegal type for property: VALUE=DURATION

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

Bug description:
  Cannot dismiss reminders for a recurrence with exceptions. Calendar entries 
like this are generated:
  BEGIN:VALARM
  ACTION:DISPLAY
  DESCRIPTION:My recurrence
  TRIGGER;VALUE=DURATION:-PT120M
  X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
   ter with an illegal type for property: VALUE=DURATION
  END:VALARM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2004 F pulseaudio
   /dev/snd/controlC0:  vectro 2004 F pulseaudio
  BuildID: 20190705212852
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Oct  2 17:50:39 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.sku: T4M40UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1900253] Re: No Sound on ASUS ZenBook UX463FL_Q427FL

2020-12-16 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No Sound on ASUS ZenBook UX463FL_Q427FL

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This seems related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 :

  - same soundcard (Realtek ALC294).
  - Ubuntu 20.04 (kernel - 5.4.0-51-generic #56-Ubuntu SMP)

  - Internal speakers work
  - Jack (heaphones, external speakers) do not (cracking sound apparently 
correlated with laptop activity)

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

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


[Desktop-packages] [Bug 1908469] Re: Cannot install .deb packages opened from Firefox

2020-12-16 Thread Steve Langasek
** Package changed: ubiquity (Ubuntu) => firefox (Ubuntu)

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

Title:
  Cannot install .deb packages opened from Firefox

Status in firefox package in Ubuntu:
  New

Bug description:
  Suppose in Firefox you click a link to a .deb package. A dialog named
  "Opening [filename].deb" opens. If you select "Open with", then the
  .deb file is downloaded, placed in /tmp/mozilla_[username]0/
  directory, then Software Install (as named in the Firefox dialog) is
  started on that .deb file.

  Next, Software Install loads and fails with "Failed to install file:
  not supported".

  If on the other hand, in Firefox's "Opening [filename].deb" dialog, if
  I select "Save File" instead, the .deb file ends up in the user's
  Downloads directory. Software Install works fine with the package
  there.

  I don't want to get too much into solutioning or "why". The main point
  of this bug is that I should not get a weird error just because I
  selected "Open with" instead of "Save File". This happens with a
  vanilla install of Ubuntu, with nothing else installed, so the product
  isn't working in an intuitive way.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 16 19:54:01 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-12-10 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908469] [NEW] Cannot install .deb packages opened from Firefox

2020-12-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Suppose in Firefox you click a link to a .deb package. A dialog named
"Opening [filename].deb" opens. If you select "Open with", then the .deb
file is downloaded, placed in /tmp/mozilla_[username]0/ directory, then
Software Install (as named in the Firefox dialog) is started on that
.deb file.

Next, Software Install loads and fails with "Failed to install file: not
supported".

If on the other hand, in Firefox's "Opening [filename].deb" dialog, if I
select "Save File" instead, the .deb file ends up in the user's
Downloads directory. Software Install works fine with the package there.

I don't want to get too much into solutioning or "why". The main point
of this bug is that I should not get a weird error just because I
selected "Open with" instead of "Save File". This happens with a vanilla
install of Ubuntu, with nothing else installed, so the product isn't
working in an intuitive way.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 16 19:54:01 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2020-12-10 (6 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy ubiquity-20.10.13
-- 
Cannot install .deb packages opened from Firefox
https://bugs.launchpad.net/bugs/1908469
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left

2020-12-16 Thread Kristijan Žic 
I've just transitioned from Unity7 it's a huge UX and ergonomic issue.

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

Title:
  Titlebar buttons incorrectly placed when set to appear on the left

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

Bug description:
  Unexpected button location on settings. Check image as screenshot
  attachment.

  Gnome Tweaks -> move the Titlebar buttons from Right to Left.

  Buttons should be paced on the extreme left -> for gnome-control-
  center they are centrally placed.

  OS: Ubuntu 20.04
  OS Type: 64-bit
  Gnome: 3.36.1
  Windows System: X11 / Xorg

  May the question how be how to reproduce? To switch button on the left
  side.

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

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


[Desktop-packages] [Bug 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all

2020-12-16 Thread Deck Weiss
Sorry, forgot to add aslainfo.

** Attachment added: "alsainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+attachment/5444389/+files/alsainfo.txt

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

Title:
  [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The sound was working just fine. I didn't work with my laptop for
  about half an hour and I didn't change anything that I can think of.
  But suddenly, there were no sounds anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 11 21:20:12 2020
  InstallationDate: Installed on 2020-10-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP410UF.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP410UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook Flip 14 TP410UF
  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/alsa-driver/+bug/1903896/+subscriptions

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


[Desktop-packages] [Bug 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all

2020-12-16 Thread Deck Weiss
Exactly the same problem. Since update yesterday.


Asus Vivobook Flip 14 TP420IA. Realtek ALC256.

Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-33-generic
OS Type: 64-bit
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 15,1 GiB of RAM
Graphics Processor: AMD RENOIR

** Attachment added: "apt_history.log"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+attachment/5444388/+files/apt_history.log

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

Title:
  [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The sound was working just fine. I didn't work with my laptop for
  about half an hour and I didn't change anything that I can think of.
  But suddenly, there were no sounds anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 11 21:20:12 2020
  InstallationDate: Installed on 2020-10-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP410UF.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP410UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook Flip 14 TP410UF
  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/alsa-driver/+bug/1903896/+subscriptions

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


[Desktop-packages] [Bug 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all

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

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

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

Title:
  [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The sound was working just fine. I didn't work with my laptop for
  about half an hour and I didn't change anything that I can think of.
  But suddenly, there were no sounds anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 11 21:20:12 2020
  InstallationDate: Installed on 2020-10-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a_roudgar   1713 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP410UF.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP410UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook Flip 14 TP410UF
  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/alsa-driver/+bug/1903896/+subscriptions

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


[Desktop-packages] [Bug 1908396] Re: laptop display is enabled even though lid is closed

2020-12-16 Thread Daniel van Vugt
Thanks for the bug report. If the issue is fixed in 20.10 then we mark
the overall bug as fixed. If anyone can identify what fixed it exactly
then we would also be able to propose that fix to 20.04.

** Tags added: focal

** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  laptop display is enabled even though lid is closed

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
  Driver: nvidia-455

  This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

  If I boot the laptop with the lid closed, "Screen Display" settings
  shows the laptop display is active, and it's possible to drag a window
  off the screen to where the laptop display is supposed to be (but lid
  is closed, it's off).

  If I then suspend and resume, the screen sizing gets messed up -
  hitting F11 to fullscreen a window on the 2nd monitor results in it
  expanding to fill 2 monitors instead of 1. However, if I open the
  laptop lid, and suspend with the lid open, then F11 fullscreen
  correctly fills 1 monitor as it should. I suspect this sizing issue
  could be caused by the laptop screen being incorrectly included in the
  screen size calculations.

  Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
  driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
  determine if it was kernel issue, but the problem still occurred.

  Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1897530

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

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


[Desktop-packages] [Bug 1893478] Re: Wireless mouse not working

2020-12-16 Thread Daniel van Vugt
This bug is closed. Please open a new bug about your issue.

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

Title:
  Wireless mouse not working

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  This might be link to gdm3
  Running Ubuntu 20.04.1
  Wireless mouse stop working after fresh install of Ubuntu 20.04 and after 
upgrade to 20.04 on another computer.

  The usb dongle is detected according to lsusb
  Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse

  When booting if I select recovery mode and then choose resume,
  everything works fine for this session, but as soon as I reboot then
  mouse stop working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 15:30:34 2020
  InstallationDate: Installed on 2020-05-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109

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

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


[Desktop-packages] [Bug 1894593] Re: Fractional scaling switch doesn't work in Wayland sessions

2020-12-16 Thread Daniel van Vugt
** Changed in: gnome-control-center (Ubuntu)
   Importance: Low => Medium

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

Title:
  Fractional scaling switch doesn't work in Wayland sessions

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

Bug description:
  Hitting the “fractional scaling” toggle in the “Screen Display” tab in
  gnome-control-centre page doesn't work - although the toggle changes
  to the “enabled” state there's no visible effect, and if I switch to a
  different page (or close g-c-c) and then switch back (or reopen g-c-c)
  then the toggle is back in the disabled state.

  Running from the command line, I see;
  (gnome-control-center:171131): display-cc-panel-WARNING **: 13:34:19.407: no 
sunset data, using 16.00

  (gnome-control-center:171131): display-cc-panel-WARNING **:
  13:34:19.407: no sunrise data, using 8.00

  (gnome-control-center:171131): display-cc-panel-CRITICAL **:
  13:34:21.972: file ../panels/display/cc-display-config.c: line 452
  (get_fractional_scaling_key): should not be reached

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0+bcachefs.git20200701.7e04f345-1-generic 
5.8.4
  Uname: Linux 5.8.0+bcachefs.git20200701.7e04f345-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 13:34:44 2020
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (76 days ago)

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

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


[Desktop-packages] [Bug 1908348] Re: Disk capacity in "about" section of the gnome-control-panel

2020-12-16 Thread Daniel van Vugt
Thanks. I'm not sure the developers intend to include external drives in
that sum, and so I'm not sure if this is a bug...

Please open a new issue upstream:

  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/new

and then tell us the new issue ID.


** Summary changed:

- Disk capacity in "about" section of the gnome-control-panel
+ Disk capacity in "about" section of the gnome-control-panel is missing 
external (boot) drive

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

Title:
  Disk capacity in "about" section of the gnome-control-panel is missing
  external (boot) drive

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

Bug description:
   Disk capacity in "about" section of the gnome-control-panel always
  shows internal computer disk space available but not the disk where
  Ubuntu is executed.

  I am executing Ubuntu from and external drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 16 06:35:52 2020
  InstallationDate: Installed on 2020-10-26 (50 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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/1908348/+subscriptions

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


[Desktop-packages] [Bug 1908429] Re: gnome-shell bug journald and syslog all filled up

2020-12-16 Thread Daniel van Vugt
Please run this command:

  ls ~/.local/share/gnome-shell/extensions > local.txt

and then attach the resulting text file here.

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

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

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

** Tags added: performance

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

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

Title:
  gnome-shell bug journald and syslog all filled up

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

Bug description:
  Issue is explained in detail here: https://gitlab.gnome.org/GNOME
  /gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM

2020-12-16 Thread Daniel van Vugt
Oops. It appears this was fixed in gdm3 in 2017. If you have any more
problems then please open new bugs.

** Tags added: a2dp

** No longer affects: gdm3 (Ubuntu Zesty)

** No longer affects: pulseaudio (Ubuntu Zesty)

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

** Changed in: gdm
   Importance: Medium => Unknown

** Changed in: gdm
   Status: Expired => Unknown

** Changed in: gdm
 Remote watch: GNOME Bug Tracker #784856 => gitlab.gnome.org/GNOME/gdm/-/issues 
#323

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/340

** Changed in: pulseaudio
   Importance: Medium => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #57167 => 
gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340

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

** No longer affects: bluez (Ubuntu Xenial)

** No longer affects: gdm3 (Ubuntu Xenial)

** No longer affects: pulseaudio (Ubuntu Xenial)

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

** No longer affects: bluez (Ubuntu)

** No longer affects: pulseaudio (Ubuntu)

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

Title:
  Bluetooth audio devices/profiles are missing after logging in from GDM

Status in gdm:
  Unknown
Status in PulseAudio:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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


[Desktop-packages] [Bug 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

2020-12-16 Thread Daniel van Vugt
** Tags added: regression-update rls-gg-incoming

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

** Tags added: rls-gg-incoming

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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


[Desktop-packages] [Bug 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9

2020-12-16 Thread Daniel van Vugt
That's a good point. We might be able to rule out mutter... Can you
please run this command in Plasma desktop:

  xrandr --verbose > plasmaxrandr.txt

and attach the resulting file here?


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

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

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

Title:
  HDMI monitor detected but black screen (has a preferred mode but no
  current mode) with Intel UHD graphics on kernel 5.9

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS.

  The problem:

  When i connect to my external monitor (a Samsung BX2250) via HDMI, the
  screen is detected (i can see it in display settings) but the external
  monitor remains black. Seams like a bad frequency or resolution. I
  tried adding a new mode to xrandr with no luck. Also i tried different
  versions of kernels from 5.4 to 5.9.

  I am using Ubuntu 20.10

  This is my lspci

  0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal 
Subsytem
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
  00:14.5 SD Host controller: Intel Corporation Device 02f5
  00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host 
Controller
  00:16.0 Communication controller: Intel Corporation Comet Lake Management 
Engine Interface
  00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
  00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
  00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI 
(flash) Controller
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01)

  inxi -Gx output:

  Graphics:  Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 
v: kernel bus ID: 00:02.0 
 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 
1-2:2 
 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 
20.2.1 direct render: Yes 

  xrandr output (with hdmi cable connected to external monitor):

  Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384
  eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y 
axis) 309mm x 173mm
 1366x768  60.06*+  40.04  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  HDMI-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +  50.0059.94  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  74.9859.90  
 1280x960  60.00  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.00

[Desktop-packages] [Bug 1862373] Re: Hexchat displays "is ready" notification for every message

2020-12-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1825710 ***
https://bugs.launchpad.net/bugs/1825710

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 1825710, 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 1825710
   Remove "Application is ready" notification

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

Title:
  Hexchat displays "is ready" notification for every message

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If the Hexchat window is not in focus, Hexchat will display a
  notification with the name of the Hexchat window in quotes and 'is
  ready' (eg, '"Avital_ @ freenode / ##linux - Hexchat" is ready') for
  every message received in the channel on the first network connected.
  If it is a direct message or a message with a mention of my name, the
  correct notification overrides it. I am connected to 2 networks and it
  will only push the notification when messages are received in the
  first network. Under Settings > Preferences > Alerts, "Show
  notifications on: Channel Message" is not checked. This was not an
  issue running Bionic but began immediately upon upgrading to Focal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hexchat 2.14.3-2build1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 09:09:28 2020
  ExecutablePath: /usr/bin/hexchat
  InstallationDate: Installed on 2019-07-20 (202 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: hexchat
  UpgradeStatus: Upgraded to focal on 2020-02-06 (0 days ago)

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

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


[Desktop-packages] [Bug 1908462] [NEW] sierre inesperado por utilizacion de teclado

2020-12-16 Thread Cesar Forero
Public bug reported:

uso de teclado cierra la aplicacion

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 84.0+build3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cesar  1285 F pulseaudio
BuildID: 20201211215739
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 16 19:45:22 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-12-11 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.39.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.39.0/24 dev wlo1 proto kernel scope link src 192.168.39.157 metric 600
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=84.0/20201211215739 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.45
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8320
dmi.board.vendor: HP
dmi.board.version: 19.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd07/02/2019:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn8320:rvr19.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-bs0xx
dmi.product.sku: 1GR60LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  sierre inesperado por utilizacion de teclado

Status in firefox package in Ubuntu:
  New

Bug description:
  uso de teclado cierra la aplicacion

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 84.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cesar  1285 F pulseaudio
  BuildID: 20201211215739
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 16 19:45:22 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-12-11 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.39.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.39.0/24 dev wlo1 proto kernel scope link src 192.168.39.157 metric 
600
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  Profile0PrefSources: 

[Desktop-packages] [Bug 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9

2020-12-16 Thread Juan Manuel Diaz
I tried with Plasma desktop... Same result.

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

Title:
  HDMI monitor detected but black screen (has a preferred mode but no
  current mode) with Intel UHD graphics on kernel 5.9

Status in gnome-control-center package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS.

  The problem:

  When i connect to my external monitor (a Samsung BX2250) via HDMI, the
  screen is detected (i can see it in display settings) but the external
  monitor remains black. Seams like a bad frequency or resolution. I
  tried adding a new mode to xrandr with no luck. Also i tried different
  versions of kernels from 5.4 to 5.9.

  I am using Ubuntu 20.10

  This is my lspci

  0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal 
Subsytem
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
  00:14.5 SD Host controller: Intel Corporation Device 02f5
  00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host 
Controller
  00:16.0 Communication controller: Intel Corporation Comet Lake Management 
Engine Interface
  00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
  00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
  00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI 
(flash) Controller
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01)

  inxi -Gx output:

  Graphics:  Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 
v: kernel bus ID: 00:02.0 
 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 
1-2:2 
 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 
20.2.1 direct render: Yes 

  xrandr output (with hdmi cable connected to external monitor):

  Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384
  eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y 
axis) 309mm x 173mm
 1366x768  60.06*+  40.04  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  HDMI-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +  50.0059.94  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  74.9859.90  
 1280x960  60.00  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0072.8166.6760.0059.94  
 720x400   70.08  
  DP-1 

[Desktop-packages] [Bug 1385362] Re: package doc-base 0.10.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2020-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package doc-base - 0.11

---
doc-base (0.11) unstable; urgency=medium

  [ Lev Lamberov ]
  * Fix typo in documentation

  [ Eduard Bloch ]
  * Fix typo in German translation

  [ Robert Luberda ]
  * Initial Portuguese translation of manpage (closes: #964798). Thanks
to Américo Monteiro.
  * Fix a long-standing issue with doc-base trigger failures on upgrades of
packages that provided doc-base files from which install-docs could not
generate output control file in /var/lib/doc-base documents.  In such a
case doc-base did not store information about input /usr/share/doc-base
files in its files database, what resulted in trigger failure on later
upgrade of the package (closes: #735418, #931705, LP: #1385362,
LP: #1607755, LP: #1726384, LP: #1755880).
  * Remove support for scrollkeeper/rarian, as the packages have been
already removed from Debian (closes: #928635). Unfuzzy translations
of documentation.
  * Bump debhelper's compat to 13.
  * Standards-Version: 4.5.1.

 -- Robert Luberda   Tue, 15 Dec 2020 08:09:48 +0100

** Changed in: doc-base (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package doc-base 0.10.6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  Fix Released

Bug description:
  During upgrade (via upgrade-manager) to 14.10 from 14.04.

  14.10 booted after the failed update.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: doc-base 0.10.6
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 23 18:37:34 2014
  DuplicateSignature: package:doc-base:0.10.6:subprocess installed 
post-installation script returned error exit status 3
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2013-08-21 (429 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: doc-base
  Title: package doc-base 0.10.6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 3
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago)

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

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


[Desktop-packages] [Bug 1607755] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2020-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package doc-base - 0.11

---
doc-base (0.11) unstable; urgency=medium

  [ Lev Lamberov ]
  * Fix typo in documentation

  [ Eduard Bloch ]
  * Fix typo in German translation

  [ Robert Luberda ]
  * Initial Portuguese translation of manpage (closes: #964798). Thanks
to Américo Monteiro.
  * Fix a long-standing issue with doc-base trigger failures on upgrades of
packages that provided doc-base files from which install-docs could not
generate output control file in /var/lib/doc-base documents.  In such a
case doc-base did not store information about input /usr/share/doc-base
files in its files database, what resulted in trigger failure on later
upgrade of the package (closes: #735418, #931705, LP: #1385362,
LP: #1607755, LP: #1726384, LP: #1755880).
  * Remove support for scrollkeeper/rarian, as the packages have been
already removed from Debian (closes: #928635). Unfuzzy translations
of documentation.
  * Bump debhelper's compat to 13.
  * Standards-Version: 4.5.1.

 -- Robert Luberda   Tue, 15 Dec 2020 08:09:48 +0100

** Changed in: doc-base (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  Fix Released

Bug description:
  Upgrading 14.04 LTS to 16.04.1

  Running partial upgrade after initial upgrade failed to complete, and a 
helpful box popped up saying:
  The upgrade will continue but the 'doc-base' package may not be in a working 
state. Please consider submitting a bug report about it.

  So I am submitting a bug report.

  The best I can do to help is copy this:

  Setting up doc-base (0.10.7) ...
  Processing 134 added doc-base files...
  Cannot open file `/usr/share/doc-base/ocaml-doc-ocaml' for reading: No such 
file or directory.
  dpkg: error processing package doc-base (--configure):
   subprocess installed post-installation script returned error exit status 3
  dpkg: dependency problems prevent configuration of dwww:
   dwww depends on doc-base (>= 0.8.12); however:
Package doc-base is not configured yet.

  dpkg: error processing package dwww (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.
dpkg: dependency problems prevent configuration of 
ubuntu-desktop:
   ubuntu-desktop depends on doc-base; however:
Package doc-base is not configured yet.

  dpkg: error processing package ubuntu-desktop (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.
Errors were encountered while processing:
   doc-base
   dwww
   ubuntu-desktop
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: doc-base 0.10.7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 20:49:53 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2012-11-02 (1365 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: doc-base
  Title: package doc-base 0.10.7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726384] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2020-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package doc-base - 0.11

---
doc-base (0.11) unstable; urgency=medium

  [ Lev Lamberov ]
  * Fix typo in documentation

  [ Eduard Bloch ]
  * Fix typo in German translation

  [ Robert Luberda ]
  * Initial Portuguese translation of manpage (closes: #964798). Thanks
to Américo Monteiro.
  * Fix a long-standing issue with doc-base trigger failures on upgrades of
packages that provided doc-base files from which install-docs could not
generate output control file in /var/lib/doc-base documents.  In such a
case doc-base did not store information about input /usr/share/doc-base
files in its files database, what resulted in trigger failure on later
upgrade of the package (closes: #735418, #931705, LP: #1385362,
LP: #1607755, LP: #1726384, LP: #1755880).
  * Remove support for scrollkeeper/rarian, as the packages have been
already removed from Debian (closes: #928635). Unfuzzy translations
of documentation.
  * Bump debhelper's compat to 13.
  * Standards-Version: 4.5.1.

 -- Robert Luberda   Tue, 15 Dec 2020 08:09:48 +0100

** Changed in: doc-base (Ubuntu)
   Status: New => Fix Released

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  Fix Released

Bug description:
  After upgrade upon rebooting would NOT recognize my password

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: doc-base 0.10.7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  Date: Sat Oct 21 13:23:51 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2016-04-09 (561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: doc-base
  Title: package doc-base 0.10.7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1755880] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2020-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package doc-base - 0.11

---
doc-base (0.11) unstable; urgency=medium

  [ Lev Lamberov ]
  * Fix typo in documentation

  [ Eduard Bloch ]
  * Fix typo in German translation

  [ Robert Luberda ]
  * Initial Portuguese translation of manpage (closes: #964798). Thanks
to Américo Monteiro.
  * Fix a long-standing issue with doc-base trigger failures on upgrades of
packages that provided doc-base files from which install-docs could not
generate output control file in /var/lib/doc-base documents.  In such a
case doc-base did not store information about input /usr/share/doc-base
files in its files database, what resulted in trigger failure on later
upgrade of the package (closes: #735418, #931705, LP: #1385362,
LP: #1607755, LP: #1726384, LP: #1755880).
  * Remove support for scrollkeeper/rarian, as the packages have been
already removed from Debian (closes: #928635). Unfuzzy translations
of documentation.
  * Bump debhelper's compat to 13.
  * Standards-Version: 4.5.1.

 -- Robert Luberda   Tue, 15 Dec 2020 08:09:48 +0100

** Changed in: doc-base (Ubuntu)
   Status: New => Fix Released

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  Fix Released

Bug description:
  $ update-manager
  /usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying 
a version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
from gi.repository import Gtk
  /usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right 
version gets loaded.
from gi.repository import Dbusmenu, Unity
  /usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Unity was imported without specifying a version first. Use 
gi.require_version('Unity', '7.0') before import to ensure that the right 
version gets loaded.
from gi.repository import Dbusmenu, Unity
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 3.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  billy@billy-P35-DS3P:~$ ^C
  billy@billy-P35-DS3P:~$ 
  billy@billy-P35-DS3P:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: doc-base 0.10.7
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

2020-12-16 Thread Lukas Svoboda
Workaround for Ubuntu 20.04(.1): downgrade package from

gnome-shell-extension-appindicator/focal-updates,focal-updates
33.1-0ubuntu0.20.04.1 all [upgradable from: 33-1]

to

gnome-shell-extension-appindicator/focal,focal,now 33-1 all
[installed,upgradable to: 33.1-0ubuntu0.20.04.1]

using command

sudo apt install gnome-shell-extension-appindicator=33-1

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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


[Desktop-packages] [Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-16 Thread Brian Murray
Ah actually this could happen if you set "Never" in the control panel
but either manually created /var/lib/apport/autoreport or installed the
apport-noui package.

Unpacking apport-noui (2.20.11-0ubuntu55) ...
Setting up apport-noui (2.20.11-0ubuntu55) ...
bdmurray@clean-hirsute-amd64:~$ gdbus introspect --system --only-properties 
--dest com.ubuntu.WhoopsiePreferences --object-path 
/com/ubuntu/WhoopsiePreferences
node /com/ubuntu/WhoopsiePreferences {
  interface com.ubuntu.WhoopsiePreferences {
properties:
  readonly b ReportCrashes = false;
  readonly b ReportMetrics = true;
  readonly b AutomaticallyReportCrashes = true;
  };
};

I think that's a different bug with gnome-control-center not reading the
current state of things when starting up.

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

Title:
  diagnostics panel can leave automatic crash reporting enabled

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Focal:
  Incomplete
Status in gnome-control-center source package in Groovy:
  Incomplete
Status in gnome-control-center source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not
  removed but the panel continues to show "Never".

  * Test case

  - change the automatic report option in settings to automatic and then
  to never, the /var/lib/apport/autoreport file should be removed

  * Regression potential

  The patch modifies the whoopsie configuration, check that the service
  status is right for the 3 auto/manual/never options

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1906877/+subscriptions

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


[Desktop-packages] [Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-16 Thread Brian Murray
I'm not sure how you would get it in a state where reporting=false and
autoreport=true. These are the dbus settings for the 3 possible states
in hirsute with the new version of gnome-control-center.

"Never"
WhoopsiePreferences
node /com/ubuntu/WhoopsiePreferences {
  interface com.ubuntu.WhoopsiePreferences {
properties:
  readonly b ReportCrashes = false;
  readonly b ReportMetrics = true;
  readonly b AutomaticallyReportCrashes = false;
  };
};

"Automatic"
bdmurray@clean-hirsute-amd64:~$ gdbus introspect --system --only-properties 
--dest com.ubuntu.WhoopsiePreferences --object-path 
/com/ubuntu/WhoopsiePreferences
node /com/ubuntu/WhoopsiePreferences {
  interface com.ubuntu.WhoopsiePreferences {
properties:
  readonly b ReportCrashes = true;
  readonly b ReportMetrics = true;
  readonly b AutomaticallyReportCrashes = true;
  };
};

"Manual"
bdmurray@clean-hirsute-amd64:~$ gdbus introspect --system --only-properties 
--dest com.ubuntu.WhoopsiePreferences --object-path /com/ubuntu/
WhoopsiePreferences
node /com/ubuntu/WhoopsiePreferences {
  interface com.ubuntu.WhoopsiePreferences {
properties:
  readonly b ReportCrashes = true;
  readonly b ReportMetrics = true;
  readonly b AutomaticallyReportCrashes = false;
  };
};

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

Title:
  diagnostics panel can leave automatic crash reporting enabled

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Focal:
  Incomplete
Status in gnome-control-center source package in Groovy:
  Incomplete
Status in gnome-control-center source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not
  removed but the panel continues to show "Never".

  * Test case

  - change the automatic report option in settings to automatic and then
  to never, the /var/lib/apport/autoreport file should be removed

  * Regression potential

  The patch modifies the whoopsie configuration, check that the service
  status is right for the 3 auto/manual/never options

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1906877/+subscriptions

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


[Desktop-packages] [Bug 1862373] Re: Hexchat displays "is ready" notification for every message

2020-12-16 Thread Mattia Rizzolo
To me it looks pretty clear that it's a gnome-shell bug, also seeing the
gitlab.gnome.org bug.  Reassigning.

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

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

Title:
  Hexchat displays "is ready" notification for every message

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If the Hexchat window is not in focus, Hexchat will display a
  notification with the name of the Hexchat window in quotes and 'is
  ready' (eg, '"Avital_ @ freenode / ##linux - Hexchat" is ready') for
  every message received in the channel on the first network connected.
  If it is a direct message or a message with a mention of my name, the
  correct notification overrides it. I am connected to 2 networks and it
  will only push the notification when messages are received in the
  first network. Under Settings > Preferences > Alerts, "Show
  notifications on: Channel Message" is not checked. This was not an
  issue running Bionic but began immediately upon upgrading to Focal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hexchat 2.14.3-2build1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 09:09:28 2020
  ExecutablePath: /usr/bin/hexchat
  InstallationDate: Installed on 2019-07-20 (202 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: hexchat
  UpgradeStatus: Upgraded to focal on 2020-02-06 (0 days ago)

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

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


[Desktop-packages] [Bug 1862373] [NEW] Hexchat displays "is ready" notification for every message

2020-12-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If the Hexchat window is not in focus, Hexchat will display a
notification with the name of the Hexchat window in quotes and 'is
ready' (eg, '"Avital_ @ freenode / ##linux - Hexchat" is ready') for
every message received in the channel on the first network connected. If
it is a direct message or a message with a mention of my name, the
correct notification overrides it. I am connected to 2 networks and it
will only push the notification when messages are received in the first
network. Under Settings > Preferences > Alerts, "Show notifications on:
Channel Message" is not checked. This was not an issue running Bionic
but began immediately upon upgrading to Focal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: hexchat 2.14.3-2build1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  7 09:09:28 2020
ExecutablePath: /usr/bin/hexchat
InstallationDate: Installed on 2019-07-20 (202 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: hexchat
UpgradeStatus: Upgraded to focal on 2020-02-06 (0 days ago)

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


** Tags: amd64 apport-bug focal
-- 
Hexchat displays "is ready" notification for every message 
https://bugs.launchpad.net/bugs/1862373
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell 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 1844815] Re: appindicators for startup applications missing from top bar upon login

2020-12-16 Thread Lukas Svoboda
Also affects 20.04 since some update in last few days.

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

Title:
  appindicators for startup applications missing from top bar upon login

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

Bug description:
  I have two startup applications configured, flameshot and yubioath-
  desktop. After upgrading this morning from 19.04 to 19.10, these two
  applications are being started when I log in, but their appindicator
  icons are not showing up in the top bar. Restarting gnome-shell with
  Alt-F2 r does not help. To make the icons show up I have to kill and
  restart the two applications. This is a regression from 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-appindicator 30-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:33:31 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-appindicator
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

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

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


[Desktop-packages] [Bug 1895721] Re: Wayland not allowing Fractional Scaling to be set

2020-12-16 Thread Leslie Chou
*** This bug is a duplicate of bug 1894593 ***
https://bugs.launchpad.net/bugs/1894593

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

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

Title:
  Wayland not allowing Fractional Scaling to be set

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

Bug description:
  Setting Fractional Scaling in the X11 Gnome Session is working fine. I
  can set the 3000x2000 screen to 150%.

  In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't
  stick, and I don't see any fractional scaling percentage options show
  up.

  (Running a slightly customized 5.9-rc5 kernel to get backlight
  working, but otherwise everything is pretty ordinary for some values
  of ordinary.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.37.91-1ubuntu1
  Uname: Linux 5.9.0-rc5-dpcdon x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 15 13:40:08 2020
  InstallationDate: Installed on 2020-08-24 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200728)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908429] Re: gnome-shell bug journald and syslog all filled up

2020-12-16 Thread Lillo Gullo
This is the king of message filling up the logs:

Nov 06 16:21:40 delly gnome-shell[5259]: Attempting to run a JS callback during 
garbage collection. This is most likely caused by destroying a Clutter actor or 
GTK widget with ::destroy signal connected, or using the destroy(), dispose(), 
or remove() vfuncs. Because it would crash the application, it has been blocke>
Nov 06 16:21:40 delly gnome-shell[5259]: The offending callback was 
SourceFunc().

Also note that gnome-shell takes 100% CPU

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

Title:
  gnome-shell bug journald and syslog all filled up

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Issue is explained in detail here: https://gitlab.gnome.org/GNOME
  /gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908429] [NEW] gnome-shell bug journald and syslog all filled up

2020-12-16 Thread Lillo Gullo
Public bug reported:

Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/1868

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Dec 16 18:56:56 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-01 (258 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-shell bug journald and syslog all filled up

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Issue is explained in detail here: https://gitlab.gnome.org/GNOME
  /gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908278] Re: Nvidia 340.108 fails to install with kernels 5.10.x - new patches needeed

2020-12-16 Thread ppp
UPDATE

...and Debian is the winner! And the first obviously!

Tested on Sparkylinux (Debian testing) with nvidia-graphics-drivers-
legacy-340xx (340.108-10) unstable.

System seems working good at the moment.

For those interested driver's metadata is this:

nvidia-graphics-drivers-legacy-340xx (340.108-10) unstable;
urgency=medium

  * Backport drm_prime_pages_to_sg_has_drm_device_arg changes
from 455.45.01 to fix kernel module build for Linux 5.10.
  * Use a version=4 watch file.

 -- Andreas Beckmann   Tue, 15 Dec 2020 22:23:56 +0100

and may be found here:

https://packages.debian.org/sid/nvidia-legacy-340xx-driver

And here you are part of log during kernel 5.10.1 install after
installing aforementioned video driver:

<>

Hope to see an updated driver for Ubuntu soon.

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

Title:
  Nvidia 340.108 fails to install with kernels 5.10.x - new patches
  needeed

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

Bug description:
  As suggested by moderator Daniel van Vugt (vanvugt) I opened this new
  bug report:

  Nvidia 340.108 fails to install with kernels 5.10.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.10 is available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Thanks for your great contribution to community and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908278/+subscriptions

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


[Desktop-packages] [Bug 1908396] Re: laptop display is enabled even though lid is closed

2020-12-16 Thread Chris Bainbridge
Another symptom is that opening and then closing the laptop lid leaves
two of the external monitors unusable - the desktop images on the
monitors are unchanged but windows can't be interacted with. The only
way I have found to fix this is to open a terminal on the one working
monitor, and then run a script to cycle the two affected monitors off
and on:

xrandr \
  --output DP-1 --off \
  --output HDMI-0 --off

sleep 3

xrandr \
  --output DP-1 --auto --rotate left --right-of DP-1-1 \
  --output HDMI-0 --auto --rotate left --right-of DP-1

After this, all the external monitors are working ok.

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

Title:
  laptop display is enabled even though lid is closed

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
  Driver: nvidia-455

  This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

  If I boot the laptop with the lid closed, "Screen Display" settings
  shows the laptop display is active, and it's possible to drag a window
  off the screen to where the laptop display is supposed to be (but lid
  is closed, it's off).

  If I then suspend and resume, the screen sizing gets messed up -
  hitting F11 to fullscreen a window on the 2nd monitor results in it
  expanding to fill 2 monitors instead of 1. However, if I open the
  laptop lid, and suspend with the lid open, then F11 fullscreen
  correctly fills 1 monitor as it should. I suspect this sizing issue
  could be caused by the laptop screen being incorrectly included in the
  screen size calculations.

  Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
  driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
  determine if it was kernel issue, but the problem still occurred.

  Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1897530

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

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


[Desktop-packages] [Bug 1777285]

2020-12-16 Thread Richard Elkins
Since there seems to be no interest nor resource to fix the source code
where I indicated in comment 9, just forget it.  My work-around works
fine.

I marked this report as RESOLVED and WONTFIX.

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

Title:
  [upstream] Batch libreoffice --convert-to offers no way to wait for
  document completion

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Opinion

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

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

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


[Desktop-packages] [Bug 1777285] Re: [upstream] Batch libreoffice --convert-to offers no way to wait for document completion

2020-12-16 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Incomplete => Won't Fix

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

Title:
  [upstream] Batch libreoffice --convert-to offers no way to wait for
  document completion

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Opinion

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

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

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


[Desktop-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM

2020-12-16 Thread Saroumane
Hello,
I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 
bluetooth speaker.
I had in logs :
`src/service.c:btd_service_connect() a2dp-sink profile connect failed for 
F8:DF:15:7F:ED:AA: Protocol not available`

I found a workaround here 
https://askubuntu.com/questions/1172000/a2dp-sink-profile-connect-failed
```
$ pactl load-module module-bluetooth-policy
$ pactl load-module module-bluetooth-discover
```

I did not understand why these commands were mandatory as I already have
them in `/etc/pulse/default.pa`

Then I checked my `~/.config/pulse/default.pa`  and found this :
```
#!/usr/bin/pulseaudio -nF
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415

# load system wide configuration
.include /etc/pulse/default.pa

### unload driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
  unload-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
  unload-module module-bluetooth-discover
.endif
```

So here, we are : today, with
- Ubuntu 20.10
- Pulseaudio 1:13.99.2-1ubuntu2.1
- BlueZ 5.55-0ubuntu1.1

=> I do not reproduce the original bug.

=> Moreover, the now unnecessary workaround in
`~/.config/pulse/default.pa` is preventing normal use for bluetooth
devices.

**Workaround for the workaround** : comment the lines in 
`~/.config/pulse/default.pa`
```
#!/usr/bin/pulseaudio -nF
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415

# load system wide configuration
.include /etc/pulse/default.pa

### unload driver modules for Bluetooth hardware
#.ifexists module-bluetooth-policy.so
#  unload-module module-bluetooth-policy
#.endif
#

#.ifexists module-bluetooth-discover.so
#  unload-module module-bluetooth-discover
#.endif
```

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

Title:
  Bluetooth audio devices/profiles are missing after logging in from GDM

Status in gdm:
  Expired
Status in PulseAudio:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged
Status in gdm3 source package in Xenial:
  Triaged
Status in pulseaudio source package in Xenial:
  Triaged
Status in gdm3 source package in Zesty:
  Triaged
Status in pulseaudio source package in Zesty:
  Triaged
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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


[Desktop-packages] [Bug 1793334] Re: Chromium does not pick default pulseaudio sink

2020-12-16 Thread Nicolas Göddel
I just tested it with this version of Chrome on Ubuntu 20.04.1 LTS

Version 88.0.4324.41 (Offizieller Build) beta (64-Bit)

Normal soundouput like videos and phone rings (MS Teams) use my selected sink, 
in my case the headphones.
But as soon as I want to use the microphone it uses my internal speakers and 
microphone of the laptop instead of my USB headset which still is selected in 
the pulseaudio settings. I have to switch back and forth to finally be able to 
use my headset within the browser. And that procedure is needed for every call 
I make. Really annoying.

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

Title:
  Chromium does not pick default pulseaudio sink

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When changing the default sink (builtin audio) to USB audio (PCM2902) 
headphone, all desktop uses the new default sink.
  All but Chromium (and Chrome).
  For both Chromium (and Chrome), I have to change the output device in the 
application tab (PA).  As soon as the audio pauses in Chrome/Chromium, it will 
resume in the builtin output audio device sink.  This happens on a per tab 
basis (probably different process).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 19 11:54:57 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share/plasma:/home/raul/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-05-12 (1591 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Load-Avg-1min: 1.06
  Load-Processes-Running-Percent:   0.1%
  MachineType: Notebook P870KM_KM1
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ba6a2d10-738f-42dc-9b8a-e68c8cc5d368 ro rootflags=subvol=@
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (145 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P870KM_KM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P870KM_KM1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1908415] [NEW] libreoffice opens samba share files in read-only mode

2020-12-16 Thread Kiriaki Konstantinidou
Public bug reported:

Since the upgrade of the system to Ubuntu 18, I have a problem opening
libreoffice documents residing in samba shares.

Opening the documents from the Nautilus results in the message "Document file 
... is locked for editing by Unknown user". 
Opening a libreoffice file from the command line results in the message:
"cannot open path of the current working directory: Permission denied".

For opening text files:

>From Nautilus: read-write opening is ok
>From command line (e.g. vi): Can't open file for writing

Other operations, like creating new files/folders and deleting
files/folders are ok both from the command line and from Nautilus.

The file systems are mounted with gvfsd-fuse.
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

The user/group/permissions of the files in the shares seem ok.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs 1.36.1-0ubuntu1.3.3
ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 16 16:17:09 2020
InstallationDate: Installed on 2019-11-13 (398 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  libreoffice opens samba share files in read-only mode

Status in gvfs package in Ubuntu:
  New

Bug description:
  Since the upgrade of the system to Ubuntu 18, I have a problem opening
  libreoffice documents residing in samba shares.

  Opening the documents from the Nautilus results in the message "Document file 
... is locked for editing by Unknown user". 
  Opening a libreoffice file from the command line results in the message:
  "cannot open path of the current working directory: Permission denied".

  For opening text files:
  
  From Nautilus: read-write opening is ok
  From command line (e.g. vi): Can't open file for writing

  Other operations, like creating new files/folders and deleting
  files/folders are ok both from the command line and from Nautilus.

  The file systems are mounted with gvfsd-fuse.
  gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

  The user/group/permissions of the files in the shares seem ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 16 16:17:09 2020
  InstallationDate: Installed on 2019-11-13 (398 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908023] Re: Installing libgbm1 will make other packages removed

2020-12-16 Thread Shih-Yuan Lee
** No longer affects: hwe-next

** No longer affects: mesa (Ubuntu)

** Summary changed:

- Installing libgbm1 will make other packages removed
+ installation stopped by an exception from mark_install() in Cache class of 
python3-apt

** Description changed:

- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
- Ubuntu 20.04/20.04.1
+ Exception in the installation
  
- 2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
- libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1
+ Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation:
+ Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last):
+ Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/share/ubiquity/plugininstall.py", line 235, in run
+ Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras()
+ Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras
+ Aug 12 19:26:59 ubuntu /plugininstall.py: 
self.do_install(filtered_extra_packages)
+ Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install
+ Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg)
+ Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install
+ Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError(
+ Aug 12 19:26:59 ubuntu /plugininstall.py: 
ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to 
conflicts.
  
- 3) What you expected to happen
- Not so many packages will be removed when executing `apt-get --yes install 
libgbm1`.
+ This happen in oem project because we have lots pkg to upgrade during
+ installation because the design of factory process need it.
  
- 4) What happened instead
- Executing `apt-get --yes install libgbm1` will make many other packages to be 
removed.
+ As package list have certain dependency, and the the order that we get
+ the pkg from the python set object is not good for underlying apt
+ engine, then exception will raise.

** Changed in: oem-priority
   Status: Confirmed => In Progress

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

Title:
  installation stopped by an exception from mark_install() in Cache
  class of python3-apt

Status in OEM Priority Project:
  In Progress

Bug description:
  Exception in the installation

  Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation:
  Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last):
  Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/share/ubiquity/plugininstall.py", line 235, in run
  Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras()
  Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras
  Aug 12 19:26:59 ubuntu /plugininstall.py: 
self.do_install(filtered_extra_packages)
  Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install
  Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg)
  Aug 12 19:26:59 ubuntu /plugininstall.py: File 
"/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install
  Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError(
  Aug 12 19:26:59 ubuntu /plugininstall.py: 
ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to 
conflicts.

  This happen in oem project because we have lots pkg to upgrade during
  installation because the design of factory process need it.

  As package list have certain dependency, and the the order that we get
  the pkg from the python set object is not good for underlying apt
  engine, then exception will raise.

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

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


[Desktop-packages] [Bug 1905422] Re: CoinMP Solver not Available, option requires coinmp to be promoted

2020-12-16 Thread Adolfo Jayme
** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  CoinMP Solver not Available, option requires coinmp to be promoted

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Hi! LibreOffice Calc supports the CoinMP Linear Solver, which is an
  excellent solver to be used in spreadsheets and makes LO Calc superior
  to other office suites in that regard.

  However, the build provided by this PPA does not come with CoinMP
  Solver enabled (see Tools > Solver > Options). I posted a question at
  Ask LibreOffice and I was informed that CoinMP is enabled by default
  during build and maybe the PPA maintainers chose to disable it.

  https://ask.libreoffice.org/en/question/240836/coinmp-solver-on-
  libreoffice-calc/

  In fact, I built LibreOffice from source and CoinMP was there.
  However, building from source is not convenient and I'd like to use
  the PPA.

  Is it possible that CoinMP Solver be included in future builds of
  LibreOffice provided by this PPA?

  I am currently using LibreOffice 7.0.3.1 on Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1908348] Re: Disk capacity in "about" section of the gnome-control-panel

2020-12-16 Thread Luis Plaza
Hi Daniel!

hope you are fine. Thank you for the fast response!

Here are my two disks. The external drive from where I boot with Ubuntu
is sda, and the internal drive nvme0n1 which has Windows10. gnome-
control-center shows 238,5G as my disk space and not 897,8G


sda   8:00   1,8T  0 disk 
├─sda18:10   512M  0 part /boot/efi
├─sda28:20 1K  0 part 
├─sda58:50 897,8G  0 part /
└─sda68:60 964,8G  0 part /trabajo
sr0  11:01  1024M  0 rom  
nvme0n1 259:00 238,5G  0 disk 
├─nvme0n1p1 259:10   529M  0 part 
├─nvme0n1p2 259:20   100M  0 part 
├─nvme0n1p3 259:3016M  0 part 
├─nvme0n1p4 259:40   122G  0 part 
├─nvme0n1p5 259:50   636M  0 part 
└─nvme0n1p6 259:60 115,3G  0 part


sudo parted -l

Modelo: LaCie Mobile Drive (scsi)
Disco /dev/sda: 2000GB
Tamaño de sector (lógico/físico): 512B/4096B
Tabla de particiones: msdos
Indicadores de disco: 

Numero  Inicio  Fin Tamaño  Tipo  Sistema de archivos  Banderas
 1  1049kB  538MB   537MB   primary   fat32esp
 2  539MB   2000GB  2000GB  extended
 5  539MB   964GB   964GB   logical   ext4 arranque
 6  964GB   2000GB  1036GB  logical   ntfs


Modelo: PC SN520 NVMe WDC 256GB (nvme)
Disco /dev/nvme0n1: 256GB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: gpt
Indicadores de disco: 

Numero  Inicio  FinTamaño  Sistema de archivos  Nombre  
  Banderas
 1  1049kB  556MB  555MB   ntfs Basic data partition
  oculta, diag
 2  556MB   661MB  105MB   fat32EFI system partition
  arranque, esp
 3  661MB   677MB  16,8MB   Microsoft reserved 
partition  msftres
 4  677MB   132GB  131GB   ntfs Basic data partition
  msftdata
 6  132GB   255GB  124GB   fat32DATOS   
  msftdata
 5  255GB   256GB  667MB   ntfs 
  oculta, diag


Hope this helps )

Luis

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

Title:
  Disk capacity in "about" section of the gnome-control-panel

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

Bug description:
   Disk capacity in "about" section of the gnome-control-panel always
  shows internal computer disk space available but not the disk where
  Ubuntu is executed.

  I am executing Ubuntu from and external drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 16 06:35:52 2020
  InstallationDate: Installed on 2020-10-26 (50 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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/1908348/+subscriptions

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


[Desktop-packages] [Bug 1908407] [NEW] /usr/libexec/gnome-terminal-server:11:fixup_offsets:fixup_offsets:fixup_offsets:fixup_offsets:fixup_offsets

2020-12-16 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-terminal.  This problem was most recently seen with package version 
3.36.2-1ubuntu1~20.04, the problem page at 
https://errors.ubuntu.com/problem/04e5eec522e6f376d13668ce9d024fecfdaa6f3c 
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/.

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


** Tags: eoan focal

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

Title:
  /usr/libexec/gnome-terminal-
  
server:11:fixup_offsets:fixup_offsets:fixup_offsets:fixup_offsets:fixup_offsets

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-terminal.  This problem was most recently seen with package version 
3.36.2-1ubuntu1~20.04, the problem page at 
https://errors.ubuntu.com/problem/04e5eec522e6f376d13668ce9d024fecfdaa6f3c 
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/ubuntu/+source/gnome-terminal/+bug/1908407/+subscriptions

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
So, from #21 I'm on 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25
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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1908334

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Ubuntu Foundations Team Bug Bot
The attachment "multiple_AES_stylus.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
Cups shows only one of them (attachment3)

** Attachment added: "Screenshot from 2020-12-16 13-31-45.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444207/+files/Screenshot%20from%202020-12-16%2013-31-45.png

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
(attachment2)

** Attachment added: "Screenshot from 2020-12-16 13-29-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444205/+files/Screenshot%20from%202020-12-16%2013-29-53.png

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
I switched to the latest kernel now. After removing all printers, the
one described in paragraph one of #1 keeps getting re-detected.
(attachment 1)

Applications show two of them, where the first is "gathering
information" and cannot print. (attachment2 in the following post)

** Attachment added: "Screenshot from 2020-12-16 13-28-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444204/+files/Screenshot%20from%202020-12-16%2013-28-53.png

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1893478] Re: Wireless mouse not working

2020-12-16 Thread lesar
Me too have problem:
I'm on Ubuntu 20.04 64bit on rpi4 8GB usb boot
I'm writing using a normal Logitec mouse because the wireless MOSART mouse not 
work.


** Attachment added: "journalctl -b0 > mouse.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1893478/+attachment/5444200/+files/mouse.txt

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

Title:
  Wireless mouse not working

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  This might be link to gdm3
  Running Ubuntu 20.04.1
  Wireless mouse stop working after fresh install of Ubuntu 20.04 and after 
upgrade to 20.04 on another computer.

  The usb dongle is detected according to lsusb
  Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse

  When booting if I select recovery mode and then choose resume,
  everything works fine for this session, but as soon as I reboot then
  mouse stop working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 28 15:30:34 2020
  InstallationDate: Installed on 2020-05-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109

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

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


[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

2020-12-16 Thread launcher of pad's
issue still present after installing
libspice-client-glib-2.0-8_0.38-2ubuntu1_amd64.deb
libspice-client-gtk-3.0-5_0.38-2ubuntu1_amd64.deb
spice-client-glib-usb-acl-helper_0.38-2ubuntu1_amd64.deb
and rebooting

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-gtk package in Ubuntu:
  Fix Released
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-gtk source package in Focal:
  Triaged
Status in spice-protocol source package in Focal:
  Triaged
Status in spice-vdagent source package in Focal:
  Invalid
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908334] acpidump.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444195/+files/acpidump.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] UdevDb.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1908334/+attachment/5444194/+files/UdevDb.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] ProcModules.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444193/+files/ProcModules.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] ProcInterrupts.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444192/+files/ProcInterrupts.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


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

2020-12-16 Thread Vedran Rafaelic
apport information

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

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] ProcCpuinfo.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444189/+files/ProcCpuinfo.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


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

2020-12-16 Thread Vedran Rafaelic
apport information

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

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] PrintingPackages.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444188/+files/PrintingPackages.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Lsusb-v.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444187/+files/Lsusb-v.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Lsusb-t.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444186/+files/Lsusb-t.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Lsusb.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1908334/+attachment/5444185/+files/Lsusb.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Lspci.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1908334/+attachment/5444183/+files/Lspci.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Lspci-vt.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444184/+files/Lspci-vt.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] KernLog.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444181/+files/KernLog.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Dependencies.txt

2020-12-16 Thread Vedran Rafaelic
apport information

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

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Locale.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1908334/+attachment/5444182/+files/Locale.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] CurrentDmesg.txt

2020-12-16 Thread Vedran Rafaelic
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444179/+files/CurrentDmesg.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
apport information

** Tags added: apport-collected focal

** Description changed:

  Settings -> Printers automatically adds "EPSON_L3160_Series" device but
  it is unusable. I cannot remove it as it keeps getting automatically
  added. It is also completely unusable and its "Printing Options" shows
  blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON
  L3160 Series".
  
  When I search for printers it gets detected again, now as Name: "L3160",
  Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess
  these automatically detected drivers are fine because it is printing
  (although it also has some issues).
  
  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information" status.
  After the second one is added, the first one disappears from the list in
  the applications, although it is still present in the
  Settings->Printers.
  
  
  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui
  
  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it
  
  3. When I wait a bit more in the Add... search, I get 3 printers (check
  attachement). The one that comes up immediately (the first one) is the
  working one from description above. But the third one also works. I
  guess all 3 point to the same physical printer.
  
  Why is this happening and can it be improved?
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.14
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-11-16 (395 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
+ MachineType: HP OMEN by HP Laptop 17-cb0xxx
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-control-center
+ PackageArchitecture: amd64
+ Papersize: a4
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
+ Tags:  focal
+ Uname: Linux 5.4.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/05/2019
+ dmi.bios.vendor: AMI
+ dmi.bios.version: F.16
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 8603
+ dmi.board.vendor: HP
+ dmi.board.version: 45.38
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP OMEN
+ dmi.product.name: OMEN by HP Laptop 17-cb0xxx
+ dmi.product.sku: 7NG00EA#BED
+ dmi.sys.vendor: HP

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1908334/+attachment/5444178/+files/CupsErrorLog.txt

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  

[Desktop-packages] [Bug 1908396] Re: laptop display is enabled even though lid is closed

2020-12-16 Thread Chris Bainbridge
** Attachment added: "display_settings.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+attachment/5444196/+files/display_settings.png

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

Title:
  laptop display is enabled even though lid is closed

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
  Driver: nvidia-455

  This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

  If I boot the laptop with the lid closed, "Screen Display" settings
  shows the laptop display is active, and it's possible to drag a window
  off the screen to where the laptop display is supposed to be (but lid
  is closed, it's off).

  If I then suspend and resume, the screen sizing gets messed up -
  hitting F11 to fullscreen a window on the 2nd monitor results in it
  expanding to fill 2 monitors instead of 1. However, if I open the
  laptop lid, and suspend with the lid open, then F11 fullscreen
  correctly fills 1 monitor as it should. I suspect this sizing issue
  could be caused by the laptop screen being incorrectly included in the
  screen size calculations.

  Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
  driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
  determine if it was kernel issue, but the problem still occurred.

  Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1897530

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

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


[Desktop-packages] [Bug 1908396] Re: laptop display is enabled even though lid is closed

2020-12-16 Thread Chris Bainbridge
** Attachment added: "journal.gz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+attachment/5444197/+files/journal.gz

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

Title:
  laptop display is enabled even though lid is closed

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
  Driver: nvidia-455

  This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

  If I boot the laptop with the lid closed, "Screen Display" settings
  shows the laptop display is active, and it's possible to drag a window
  off the screen to where the laptop display is supposed to be (but lid
  is closed, it's off).

  If I then suspend and resume, the screen sizing gets messed up -
  hitting F11 to fullscreen a window on the 2nd monitor results in it
  expanding to fill 2 monitors instead of 1. However, if I open the
  laptop lid, and suspend with the lid open, then F11 fullscreen
  correctly fills 1 monitor as it should. I suspect this sizing issue
  could be caused by the laptop screen being incorrectly included in the
  screen size calculations.

  Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
  driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
  determine if it was kernel issue, but the problem still occurred.

  Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1897530

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

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


[Desktop-packages] [Bug 1908396] [NEW] laptop display is enabled even though lid is closed

2020-12-16 Thread Chris Bainbridge
Public bug reported:

Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
Driver: nvidia-455

This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

If I boot the laptop with the lid closed, "Screen Display" settings
shows the laptop display is active, and it's possible to drag a window
off the screen to where the laptop display is supposed to be (but lid is
closed, it's off).

If I then suspend and resume, the screen sizing gets messed up - hitting
F11 to fullscreen a window on the 2nd monitor results in it expanding to
fill 2 monitors instead of 1. However, if I open the laptop lid, and
suspend with the lid open, then F11 fullscreen correctly fills 1 monitor
as it should. I suspect this sizing issue could be caused by the laptop
screen being incorrectly included in the screen size calculations.

Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
determine if it was kernel issue, but the problem still occurred.

Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1897530

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

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

Title:
  laptop display is enabled even though lid is closed

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors.
  Driver: nvidia-455

  This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok.

  If I boot the laptop with the lid closed, "Screen Display" settings
  shows the laptop display is active, and it's possible to drag a window
  off the screen to where the laptop display is supposed to be (but lid
  is closed, it's off).

  If I then suspend and resume, the screen sizing gets messed up -
  hitting F11 to fullscreen a window on the 2nd monitor results in it
  expanding to fill 2 monitors instead of 1. However, if I open the
  laptop lid, and suspend with the lid open, then F11 fullscreen
  correctly fills 1 monitor as it should. I suspect this sizing issue
  could be caused by the laptop screen being incorrectly included in the
  screen size calculations.

  Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455
  driver, so I tested the 5.8.18 linux kernel with 20.04 to try and
  determine if it was kernel issue, but the problem still occurred.

  Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1897530

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

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


[Desktop-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Vedran Rafaelic
(add missing screenshot)
Now I don't think this CUPS-BRF-Printer is related as it is shown even if my 
printer is turned off.

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

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Attachment added: "Screenshot from 2020-12-16 12-11-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444176/+files/Screenshot%20from%202020-12-16%2012-11-41.png

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

Title:
  Printer managed wrongly in Settings -> Printers

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

Bug description:
  Settings -> Printers automatically adds "EPSON_L3160_Series" device
  but it is unusable. I cannot remove it as it keeps getting
  automatically added. It is also completely unusable and its "Printing
  Options" shows blank. "Printing Details" shows Address: null, Driver:
  "EPSON EPSON L3160 Series".

  When I search for printers it gets detected again, now as Name:
  "L3160", Address: "localhost" Driver: "EPSON L3160 Series,
  driverless". I guess these automatically detected drivers are fine
  because it is printing (although it also has some issues).

  Before adding this second one the first one is shown in the list of
  printing applications, but keeps saying "Retrieving information"
  status. After the second one is added, the first one disappears from
  the list in the applications, although it is still present in the
  Settings->Printers.


  1. Don't know if this printer gets automatically re-added, or it just
  disappeares from the Settings UI when it is not actually deleted.
  Because CUPS web ui, and the applications are not showing the one that
  keeps comming back in the Settings->Printers ui

  2. If it keeps getting re-added why is it not automatically set up as
  when I go Add... and click on it

  3. When I wait a bit more in the Add... search, I get 3 printers
  (check attachement). The one that comes up immediately (the first one)
  is the working one from description above. But the third one also
  works. I guess all 3 point to the same physical printer.

  Why is this happening and can it be improved?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (395 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1908334] [NEW] Printer managed wrongly in Settings -> Printers

2020-12-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Settings -> Printers automatically adds "EPSON_L3160_Series" device but
it is unusable. I cannot remove it as it keeps getting automatically
added. It is also completely unusable and its "Printing Options" shows
blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON
L3160 Series".

When I search for printers it gets detected again, now as Name: "L3160",
Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess
these automatically detected drivers are fine because it is printing
(although it also has some issues).

Before adding this second one the first one is shown in the list of
printing applications, but keeps saying "Retrieving information" status.
After the second one is added, the first one disappears from the list in
the applications, although it is still present in the
Settings->Printers.


1. Don't know if this printer gets automatically re-added, or it just
disappeares from the Settings UI when it is not actually deleted.
Because CUPS web ui, and the applications are not showing the one that
keeps comming back in the Settings->Printers ui

2. If it keeps getting re-added why is it not automatically set up as
when I go Add... and click on it

3. When I wait a bit more in the Add... search, I get 3 printers (check
attachement). The one that comes up immediately (the first one) is the
working one from description above. But the third one also works. I
guess all 3 point to the same physical printer.

Why is this happening and can it be improved?

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


** Tags: bot-comment printer
-- 
Printer managed wrongly in Settings -> Printers
https://bugs.launchpad.net/bugs/1908334
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups 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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-12-16 Thread Helmut Stult
The problem is your last patch

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pinctrl
/pinctrl-amd.c?h=v5.10=47a0001436352c9853d72bf2071e85b316d688a2

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

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

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

2020-12-16 Thread Lukas Svoboda
Since certain update this same behavior occurs on Ubuntu 20.04. Gnome
shell appindicator icons are not shown for applications set to start
automatically with user log in. Tested with copyq and owncloud-client.
Tray icons appear when the the respective app is started manually after
user logs in.

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Bin Li
Jonas,

 I built the debug packages with these two patches for testing, would
you like to help test them? Thanks!

** Attachment added: "libwacom2.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059/+attachment/5444147/+files/libwacom2.tar.gz

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Bin Li
I tried below two patches, it could let my Yoga Gen5 works fine.
I could find pen setting at gnome-control-center when the pen touch the screen.

I could customize the second button as right click.

056a:51b9 Wacom Co., Ltd Pen and multitouch sensor


commit a864679083c035eb08a75cf084a6564d589c0b1c
Author: Jason Gerecke 
Date:   Fri Nov 1 11:51:20 2019 -0700

Add multiple AES stylus definitions

Adds definitions for many different AES styli. The precise information
about supported features is hard to come by, but in general most pens
have two buttons (one of which is treated as an eraser) and can only
report pressure. A few exceptions are known or suspected and their
data has been set accordingly.

commit 8652aa3376bfb0e833af3704dc2ab7948958cd8f
Author: Jason Gerecke 
Date:   Tue Oct 29 15:26:51 2019 -0700

Add isdv4-aes stylus group to all AES sensors

AES sensors determined based on comments and HID descriptors available
at the wacom-hid-descriptors repository, where available. Some pen/sensor
combinations may not truly be compatible with each other, but it difficult
to know a priori which are problematic. This ultimately doesn't matter
*too* much, however, since the ID list is primarily used by tools like
GNOME Control Center that just need a rough idea of what pens might work
with a given tablet during configuration.


** Attachment added: "aes_pen.png"
   
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059/+attachment/5444143/+files/aes_pen.png

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1908373] Re: [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU

2020-12-16 Thread Daniel van Vugt
Is it just the login screen that's black or the whole boot process?

If you can, please boot in recovery mode and then run:

  apport-collect 1908373
  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => ubuntu

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

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

** Tags added: focal

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

Title:
   [Seal MT][Caribou]20.04 X59,Black screen appears when installing
  Ubuntu on AMD 540 graphics card and CML CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  [Reproduce Steps]
  1. Connect the system via 540 graphics card +CML CUP.
  2. Clean install Ubuntu 20.04
  2. A black screen appears on the system.

  [Result]
  Expected Result
  OS can be installed normally.

  [Actual Result]
  Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

  The reproduce steps :
  Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

  Others info:
  VNP on RKL+UMA
  VNP on CML+singel 550
  VNP on CML +single RX640
  VNP on RKL +single 540
  VP on CML+UMA
  VP on CML+singel 540

  [Additional Information]
  1. Test Vault ID: adhoc
  2. Checkbox test case ID : NA
  3. BIOS Version: 0.5.28
  4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
  5. SKU: OptiPlex 5090
  6. CPU: CML ES QSRK
  7. GPU: singel 540
  8. PIMS-27206 / Launchpad:#1906140 

  Failure rate: 3/3 times

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Bin Li
Here is the patch used for libwacom 1.3-2ubuntu1.

commit a864679083c035eb08a75cf084a6564d589c0b1c
Author: Jason Gerecke 
Date: Fri Nov 1 11:51:20 2019 -0700

Add multiple AES stylus definitions

** Patch added: "multiple_AES_stylus.patch"
   
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059/+attachment/5444144/+files/multiple_AES_stylus.patch

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Bin Li
Here is the patch used for 1.3-2ubuntu1, I removed the errors of
merging.

commit 8652aa3376bfb0e833af3704dc2ab7948958cd8f
Author: Jason Gerecke 
Date: Tue Oct 29 15:26:51 2019 -0700

Add isdv4-aes stylus group to all AES sensors

** Patch added: "isdv4-aes_stylus_group.patch"
   
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059/+attachment/5444145/+files/isdv4-aes_stylus_group.patch

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1908373] Re: [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU

2020-12-16 Thread Vivi-Tsai
Sorry.report wrong place

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

Title:
   [Seal MT][Caribou]20.04 X59,Black screen appears when installing
  Ubuntu on AMD 540 graphics card and CML CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  [Reproduce Steps]
  1. Connect the system via 540 graphics card +CML CUP.
  2. Clean install Ubuntu 20.04
  2. A black screen appears on the system.

  [Result]
  Expected Result
  OS can be installed normally.

  [Actual Result]
  Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

  The reproduce steps :
  Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

  Others info:
  VNP on RKL+UMA
  VNP on CML+singel 550
  VNP on CML +single RX640
  VNP on RKL +single 540
  VP on CML+UMA
  VP on CML+singel 540

  [Additional Information]
  1. Test Vault ID: adhoc
  2. Checkbox test case ID : NA
  3. BIOS Version: 0.5.28
  4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
  5. SKU: OptiPlex 5090
  6. CPU: CML ES QSRK
  7. GPU: singel 540
  8. PIMS-27206 / Launchpad:#1906140 

  Failure rate: 3/3 times

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

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


[Desktop-packages] [Bug 1908373] [NEW] [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU

2020-12-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

[Reproduce Steps]
1. Connect the system via 540 graphics card +CML CUP.
2. Clean install Ubuntu 20.04
2. A black screen appears on the system.

[Result]
Expected Result
OS can be installed normally.

[Actual Result]
Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

The reproduce steps :
Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

Others info:
VNP on RKL+UMA
VNP on CML+singel 550
VNP on CML +single RX640
VNP on RKL +single 540
VP on CML+UMA
VP on CML+singel 540

[Additional Information]
1. Test Vault ID: adhoc
2. Checkbox test case ID : NA
3. BIOS Version: 0.5.28
4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
5. SKU: OptiPlex 5090
6. CPU: CML ES QSRK
7. GPU: singel 540
8. PIMS-27206 / Launchpad:#1906140 

Failure rate: 3/3 times

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


** Tags: checkbox-test dm-reviewed fossa-cubone-rkl fossa-seadra-rkl
-- 
 [Seal MT][Caribou]20.04 X59,Black screen appears when installing Ubuntu on AMD 
540 graphics card and CML CPU
https://bugs.launchpad.net/bugs/1908373
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell 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 1908373] Re: [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU

2020-12-16 Thread Zorro Zhang
** Tags removed: odm-bug white-whale

** Tags added: dm-reviewed

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

Title:
   [Seal MT][Caribou]20.04 X59,Black screen appears when installing
  Ubuntu on AMD 540 graphics card and CML CPU

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

Bug description:
  [Reproduce Steps]
  1. Connect the system via 540 graphics card +CML CUP.
  2. Clean install Ubuntu 20.04
  2. A black screen appears on the system.

  [Result]
  Expected Result
  OS can be installed normally.

  [Actual Result]
  Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

  The reproduce steps :
  Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

  Others info:
  VNP on RKL+UMA
  VNP on CML+singel 550
  VNP on CML +single RX640
  VNP on RKL +single 540
  VP on CML+UMA
  VP on CML+singel 540

  [Additional Information]
  1. Test Vault ID: adhoc
  2. Checkbox test case ID : NA
  3. BIOS Version: 0.5.28
  4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
  5. SKU: OptiPlex 5090
  6. CPU: CML ES QSRK
  7. GPU: singel 540
  8. PIMS-27206 / Launchpad:#1906140 

  Failure rate: 3/3 times

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

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


[Desktop-packages] [Bug 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

2020-12-16 Thread Bin Li
The pen from Yoga is not Pen Pro, it's just a two button pen, while the
Pen Pro has extra button on top.

** Attachment added: "pen_penpro.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059/+attachment/5444142/+files/pen_penpro.jpg

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal

2020-12-16 Thread Daniel van Vugt
Ah right, yes. I agree. Such a long list of extensions really should be
expected to be broken already as extensions often are. I don't think
it's sensible to block on those.

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

Title:
  [SRU] Update gnome-shell to 3.36.7 in Focal

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

Bug description:
  [Impact]

  This is the current GNOME 3.36.x stable update, including some fixes
  and translation updates.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS

  3.36.7
  ==
  * Fix potential stack overflow in libcroco [Michael; !1404]
  * Fix system action search regressions [Florian; #3169]
  * Fix week number alignment when using font-scaling [Joonas; !1415]
  * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, 
!1451, #2230, !1423]

  Contributors:
  Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, 
Bastien Nocera, Daniel van Vugt

  Translators:
  Marek Černocký [cs]

  3.36.6
  ==
  * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071]
  * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420]

  Contributors:
  Sebastian Keller, Zephaniah E. Loss-Cutler-Hull

  Translators:
  Goran Vidović [hr], Balázs Úr [hu]

  3.36.5
  ==
  * Fix extension updates when many extensions are installed [Jeremias; !1363]
  * Fix missing icons in on-screen keyboard [Emre; #2631, #3007]
  * Fix delay when showing calendar events [Sebastian; #2992]
  * Fix app picker regressions on small displays [Sebastian; #2234, !1375, 
!1378]
  * Fix top bar navigation when NumLock is active [Olivier; #550]
  * Delay login animation until wallpaper has loaded [Michael; #734996]
  * Revert changes that caused mispositioning in overview in multi-monitor 
setups [Robert; #2971]
  * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997]
  * Fix stuck grab when destroying open popup menu [Florian; #3022]
  * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, 
!1381, #3037, #3005, !1386, !1390]

  Contributors:
  Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian 
Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias 
Ortega, Ray Strode, Emre Uyguroglu

  Translators:
  Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR]

  [Test case]

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

  GNOME Shell and its components should continue working well.

  The verification is going to include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [Regression potential]

  There have been fixes in various places: system actions search in
  different languages, alignment of week numbers in calendar menu, lock
  screen, scaling of app icons on Hi-dpi displays, extension updates,
  missing icons in OSK and showing calendar events in calendar menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 19:40:03 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-26 (198 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908373] [NEW] [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU

2020-12-16 Thread Vivi-Tsai
Public bug reported:

[Reproduce Steps]
1. Connect the system via 540 graphics card +CML CUP.
2. Clean install Ubuntu 20.04
2. A black screen appears on the system.

[Result]
Expected Result
OS can be installed normally.

[Actual Result]
Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

The reproduce steps :
Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

Others info:
VNP on RKL+UMA
VNP on CML+singel 550
VNP on CML +single RX640
VNP on RKL +single 540
VP on CML+UMA
VP on CML+singel 540

[Additional Information]
1. Test Vault ID: adhoc
2. Checkbox test case ID : NA
3. BIOS Version: 0.5.28
4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
5. SKU: OptiPlex 5090
6. CPU: CML ES QSRK
7. GPU: singel 540
8. PIMS-27206 / Launchpad:#1906140 

Failure rate: 3/3 times

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


** Tags: checkbox-test fossa-cubone-rkl fossa-seadra-rkl odm-bug white-whale

** Tags added: checkbox-test fossa-cubone-rkl fossa-seadra-rkl odm-bug
white-whale

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

Title:
   [Seal MT][Caribou]20.04 X59,Black screen appears when installing
  Ubuntu on AMD 540 graphics card and CML CPU

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

Bug description:
  [Reproduce Steps]
  1. Connect the system via 540 graphics card +CML CUP.
  2. Clean install Ubuntu 20.04
  2. A black screen appears on the system.

  [Result]
  Expected Result
  OS can be installed normally.

  [Actual Result]
  Clean install Ubuntu 20.04. After "Copying installation logs", the system 
reboots and the screen goes black. The Ubuntu system does not install 
successfully.

  The reproduce steps :
  Insert the U disk -> power on SUT -> error log will appear -> select the hard 
disk to install OS -> processing of copy files -> auto restart -> Dell logo 
show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on 
RKL +X59.

  Others info:
  VNP on RKL+UMA
  VNP on CML+singel 550
  VNP on CML +single RX640
  VNP on RKL +single 540
  VP on CML+UMA
  VP on CML+singel 540

  [Additional Information]
  1. Test Vault ID: adhoc
  2. Checkbox test case ID : NA
  3. BIOS Version: 0.5.28
  4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59)
  5. SKU: OptiPlex 5090
  6. CPU: CML ES QSRK
  7. GPU: singel 540
  8. PIMS-27206 / Launchpad:#1906140 

  Failure rate: 3/3 times

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

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


[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal

2020-12-16 Thread Amr Ibrahim
I meant that my reply to comment #3 that those broken extensions should
not be considered as regressions with gnome-shell 3.36.7 because they
are already broken from the beginning.

All of those extensions are already up-to-date upstream and in Debian.
It’s that Ubuntu is always ahead of Debian in GNOME releases when an
Ubuntu release is about to happen and the Debian sync freeze is in
effect. I explained that here: https://discourse.ubuntu.com/t/scope-of-
gnome-mru/18041/24?u=amr-ibrahim

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

Title:
  [SRU] Update gnome-shell to 3.36.7 in Focal

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

Bug description:
  [Impact]

  This is the current GNOME 3.36.x stable update, including some fixes
  and translation updates.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS

  3.36.7
  ==
  * Fix potential stack overflow in libcroco [Michael; !1404]
  * Fix system action search regressions [Florian; #3169]
  * Fix week number alignment when using font-scaling [Joonas; !1415]
  * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, 
!1451, #2230, !1423]

  Contributors:
  Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, 
Bastien Nocera, Daniel van Vugt

  Translators:
  Marek Černocký [cs]

  3.36.6
  ==
  * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071]
  * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420]

  Contributors:
  Sebastian Keller, Zephaniah E. Loss-Cutler-Hull

  Translators:
  Goran Vidović [hr], Balázs Úr [hu]

  3.36.5
  ==
  * Fix extension updates when many extensions are installed [Jeremias; !1363]
  * Fix missing icons in on-screen keyboard [Emre; #2631, #3007]
  * Fix delay when showing calendar events [Sebastian; #2992]
  * Fix app picker regressions on small displays [Sebastian; #2234, !1375, 
!1378]
  * Fix top bar navigation when NumLock is active [Olivier; #550]
  * Delay login animation until wallpaper has loaded [Michael; #734996]
  * Revert changes that caused mispositioning in overview in multi-monitor 
setups [Robert; #2971]
  * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997]
  * Fix stuck grab when destroying open popup menu [Florian; #3022]
  * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, 
!1381, #3037, #3005, !1386, !1390]

  Contributors:
  Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian 
Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias 
Ortega, Ray Strode, Emre Uyguroglu

  Translators:
  Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR]

  [Test case]

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

  GNOME Shell and its components should continue working well.

  The verification is going to include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [Regression potential]

  There have been fixes in various places: system actions search in
  different languages, alignment of week numbers in calendar menu, lock
  screen, scaling of app icons on Hi-dpi displays, extension updates,
  missing icons in OSK and showing calendar events in calendar menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 19:40:03 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-26 (198 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1908358] Re: gnome-control-center crashes on start

2020-12-16 Thread Paul White
** Package changed: ubuntu => gnome-control-center (Ubuntu)

** Tags added: focal

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

Title:
  gnome-control-center crashes on start

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

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  gnome-control-center:
Installed: 1:3.36.4-0ubuntu2
Candidate: 1:3.36.4-0ubuntu2
Version table:
   *** 1:3.36.4-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  samba-libs:
Installed: 2:4.11.6+dfsg-0ubuntu1.6
Candidate: 2:4.11.6+dfsg-0ubuntu1.6
Version table:
   *** 2:4.11.6+dfsg-0ubuntu1.6 500
  500 http://ru.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:4.11.6+dfsg-0ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  When I start gnome-control-center it crashes with error:

  $ gnome-control-center 
  gnome-control-center: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/samba/libclidns.so.0: undefined symbol: 
ndr_pull_dns_name_packet, version NDR_NBT_0.0.1

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

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


[Desktop-packages] [Bug 1908358] [NEW] gnome-control-center crashes on start

2020-12-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Description:Ubuntu 20.04.1 LTS
Release:20.04

gnome-control-center:
  Installed: 1:3.36.4-0ubuntu2
  Candidate: 1:3.36.4-0ubuntu2
  Version table:
 *** 1:3.36.4-0ubuntu2 500
500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1-1ubuntu5 500
500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages

samba-libs:
  Installed: 2:4.11.6+dfsg-0ubuntu1.6
  Candidate: 2:4.11.6+dfsg-0ubuntu1.6
  Version table:
 *** 2:4.11.6+dfsg-0ubuntu1.6 500
500 http://ru.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:4.11.6+dfsg-0ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages

When I start gnome-control-center it crashes with error:

$ gnome-control-center 
gnome-control-center: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/samba/libclidns.so.0: undefined symbol: 
ndr_pull_dns_name_packet, version NDR_NBT_0.0.1

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


** Tags: bot-comment
-- 
gnome-control-center crashes on start
https://bugs.launchpad.net/bugs/1908358
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center 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 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5

2020-12-16 Thread Jim Persson
I've had the "Desktop Icons" disabled for a while now, and it doesn't
solve the problem but it feels like it is less frequent.

It most often happens when I open a new terminal.

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

Title:
  toggling down object GInotifyFileMonitor that's already queued to
  toggle up ... GNOME Shell crashed with signal 5

Status in gjs:
  Unknown
Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215

  ---

  A couple of times a day, I'm noticing all of the window dressing
  suddenly disappear from all of my open applications, then a second or
  two later returning.  Opening up /var/log/syslog I see:

  Jun  6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
  Jun  6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid 
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
  Jun  6 20:47:40 eva gnome-shell[335243]: toggling down object 
GInotifyFileMonitor that's already queued to toggle down
  Jun  6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
  Jun  6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 
0x557e3a0446a0 ==
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=5/TRAP
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jun  6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 3.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
  Jun  6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
  Jun  6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID 
vendor "ACI", prod id 8434
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using hsync ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync 
+vsync (60.0 kHz eP)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync 
-vsync (56.5 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync 
(49.7 kHz e)
  Jun  6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625