date:20200424

You have been subscribed to a public bug:

Ubuntu 18.04 unknown display Samsung S19A100N, u can fix it?
I plug in in VGA.

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


** Tags: bot-comment
-- 
Unknown display
https://bugs.launchpad.net/bugs/1874881
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-24 Thread Hui Wang

Please remove snd_hda_intel: dmic_detect=0, you must set dmic_detect=0
somewhere.

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1811504] Re: Scan with HP LaserJet Pro MFP M28a fails

2020-04-24 Thread pi4630

** Summary changed:

- Scan with HP Laserjet Pro M28 fails
+ Scan with HP LaserJet Pro MFP M28a fails

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

Title:
  Scan with HP LaserJet Pro MFP M28a fails

Status in hplip package in Ubuntu:
  Fix Released

Bug description:
  I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I
  always get this error when scanning using SANE:

  error: SANE: Error during device I/O (code=9)

  I’ve installed hplip hplip-plugins and any other dependencies listed
  in hp-check but without luck.

  any hints?

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

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

[Desktop-packages] [Bug 1825593] Re: Display: 100% scale not remembered when X11 Fractional Scaling is enabled

2020-04-24 Thread Daniel Rammelt

On fresh install of 20.04, 2 x LG 4K displays, AMD 5600XT GPU

Apr 25 13:28:28 xxx systemd[1798]: Starting GNOME Shell on X11...
Apr 25 13:28:28 xxx gnome-shell[10304]: Enabling experimental feature
'x11-randr-fractional-scaling'
Apr 25 13:28:28 xxx /usr/lib/gdm3/gdm-x-session[10123]: (II) AMDGPU(0): EDID
vendor "GSM", prod id 23305
...
Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config file
'/home/xxx/.config/monitors.xml': Logical monitors not adjacent

In the monitors.xml I notice that when fractional scaling and 150% scale
my second monitor is set to 5120. When set with fractional scaling
off and 200% the is 3840.

** Attachment added: "With fractional scaling on"

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+attachment/5360020/+files/monitors.xml.fractional-scaling-on

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

Title:
Display: 100% scale not remembered when X11 Fractional Scaling is
enabled

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

Bug description:
After upgrading to 19.04, I enabled the experimental 'x11-randr-
fractional-scaling' setting. If I set scaling to 125, 150, or 200%,
the setting is remembered and used the next time I log in. If I set
scaling to 100%, however, the next time I log in the scaling switches
back to 200% automatically. I only want to use fractional scaling for
external monitors.

Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
screen. Pretty standard configuration. I have my DisplaySize set to
294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

I have been unable to find an appropriate combination of settings
where 168 DPI is respected for accurate font rendering, while at the
same time not scaling up the rest of the UI to unusable proportions.
Fractional scaling seems to be the only way to adjust some Gnome UI
elements.

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

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

[Desktop-packages] [Bug 1874964] [NEW] Secondary display in portrait mode renders incorrectly

2020-04-24 Thread Jeff Lyon

Public bug reported:

Using the Ubuntu 20.04 settings app to setup multiple monitors creates
broken xrandr settings. Using the app to set a 3840x2160 primary monitor
in Landscape and 1920x1080 in Right Portrait, the primary monitor ends
up with a "virtual resolution" of 4680x2160 which creates a horizontal
panning effect at the monitor boundary and pushes the secondary
monitor's content far off to the side.

Running xrandr shows the following (truncated for readability -
screenshot attached)

Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected 1080x1920+3840+0 left (normal left inverted right x axis y axis) 
527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0
   1920x1080 60.00 +  60.00*   59.9450.0023.98  
   ...
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 
697mm x 392mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0

The correct result for DP-4 would be 3840x2160. I will set this manually
but wanted to report the problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:42:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 22:53:21 2020
DistUpgraded: 2020-04-24 21:48:22,001 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696]
InstallationDate: Installed on 2019-07-30 (270 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Micro-Star International Co., Ltd. MS-7B09
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
dmi.bios.date: 11/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.C0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd11/14/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B09
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug focal possible-manual-nvidia-install resolution ubuntu

** Attachment added: "Screenshot from 2020-04-24 23-02-48.png"
   
https://bugs.launchpad.net/bugs/1874964/+attachment/5360022/+files/Screenshot%20from%202020-04-24%2023-02-48.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subs

[Desktop-packages] [Bug 1825593] Re: Display: 100% scale not remembered when X11 Fractional Scaling is enabled

2020-04-24 Thread Daniel Rammelt

** Attachment added: "With fractional scaling off"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+attachment/5360021/+files/monitors.xml.fractional-scaling-off

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

Title:
  Display: 100% scale not remembered when X11 Fractional Scaling is
  enabled

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

Bug description:
  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

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

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

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

2020-04-24 Thread Amartya Ghosh

Can you tell me how to do that??


On Sat, 25 Apr 2020 at 03:11, Sebastien Bacher  wrote:

> Could you add the journal log?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874717
>
> Title:
>   devices cannot connect to ubuntu hotspot
>
> Status in network-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
>   based internet connection to my ubuntu system via the hotspot
>   connection to my other devices.I am able to connect to my hospot
>   though. My ethernet connection works fine hotspot too but my devices
>   report:"This device has no connection to internet."Earlier in v18.04
>   it worked fine.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubuntu-release-upgrader-core 1:20.04.18
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashDB: ubuntu
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 24 17:49:30 2020
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: dist-upgrade
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   VarLogDistupgradeTermlog:
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 20.04
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   IpRoute:
>default via 10.20.2.1 dev enp2s0 proto static metric 100
>10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric
> 100
>10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric
> 600
>169.254.0.0/16 dev enp2s0 scope link metric 1000
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: network-manager 1.22.10-1ubuntu1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Tags:  focal
>   Uname: Linux 5.4.0-26-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.22.10  connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874717/+subscriptions
>

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: In

[Desktop-packages] [Bug 1874962] Re: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from othe

2020-04-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz',
  which is different from other instances of package
  libpango-1.0-0:amd64

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Rendering issues with the monospace default font (DejaVu Mono Book)
  led me to try and downgrade the libpango packages, which in turn
  caused this problem with the system packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpango-1.0-0 1.42.4-7~deb10u1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 23:15:13 2020
  DuplicateSignature:
   package:libpango-1.0-0:1.42.4-7~deb10u1
   Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over 
(1.42.4-7~deb10u1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
  InstallationDate: Installed on 2014-09-11 (2052 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: pango1.0
  Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1874962/+subscriptions

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

[Desktop-packages] [Bug 1874962] [NEW] package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from ot

2020-04-24 Thread S7SoSt

Public bug reported:

Rendering issues with the monospace default font (DejaVu Mono Book) led
me to try and downgrade the libpango packages, which in turn caused this
problem with the system packages.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpango-1.0-0 1.42.4-7~deb10u1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 23:15:13 2020
DuplicateSignature:
 package:libpango-1.0-0:1.42.4-7~deb10u1
 Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over (1.42.4-7~deb10u1) 
...
 dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
InstallationDate: Installed on 2014-09-11 (2052 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: pango1.0
Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz',
  which is different from other instances of package
  libpango-1.0-0:amd64

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Rendering issues with the monospace default font (DejaVu Mono Book)
  led me to try and downgrade the libpango packages, which in turn
  caused this problem with the system packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpango-1.0-0 1.42.4-7~deb10u1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 23:15:13 2020
  DuplicateSignature:
   package:libpango-1.0-0:1.42.4-7~deb10u1
   Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over 
(1.42.4-7~deb10u1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
  InstallationDate: Installed on 2014-09-11 (2052 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: pango1.0
  Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1874962/+subscriptions

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

[Desktop-packages] [Bug 1867987] Re: Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left]

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

Title:
  Two possible sounds output, when playing movie from youtube, output is
  set to wrong one automatically after 5 seconds [, Realtek ALC283,
  Black Headphone Out, Left] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I start playing movie in Firefox and there is no sound coming out. I open 
sound configuration and change 
  "Output Device" from "HDMI / DispalyPort - Built in Audio" to "Headphones - 
Built in Audio"

  Sound starts to play and then after 5 seconds it stops again.

  When I open sound configuration again, I can change "Output Device"
  again and sound plays again for 5 seconds and then it is turned off.

  I play sound using my display built in device connected through HDMI
  cable and also using audio cable. Sound is not working through HDMI
  cable. It is working using audio cable or headphones.

  My expectation is, when I set output device to be audio cable - it
  will not be changed to HDMI cable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lmlich 1369 F pulseaudio
   /dev/snd/pcmC1D0c:   lmlich 1369 F...m pulseaudio
   /dev/snd/pcmC1D0p:   lmlich 1369 F...m pulseaudio
   /dev/snd/controlC0:  lmlich 1369 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 21:09:40 2020
  InstallationDate: Installed on 2019-12-27 (82 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulseAudioLog:
   bře 18 21:02:14 lmquiet dbus-daemon[770]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.42' (uid=125 pid=979 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
   bře 18 21:02:31 lmquiet systemd[972]: pulseaudio.service: Succeeded.
   bře 18 21:02:42 lmquiet systemd[972]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [, Realtek ALC283, Black Headphone Out, Left] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0354.2016.0120.0912
  dmi.board.name: NUC5i3RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H41000-503
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0354.2016.0120.0912:bd01/20/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i3RYB:rvrH41000-503:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1858292] Re: gjs-console crashed with signal 5

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

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

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

Title:
  gjs-console crashed with signal 5

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  gjs-console crashed and gnome-shell crashed with it

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gjs 1.52.5-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  4 20:50:08 2020
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2019-10-06 (90 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: gjs 
/home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js
  Signal: 5
  SourcePackage: gjs
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   gjs_value_from_explicit_array () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
   ffi_closure_unix64_inner () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_closure_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

apport information

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

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

Title:
  Steam is shown on Gnome as being "unknown" without any icon, even
  though the steam launcher is simply downloading an update and the icon
  appears on previous versions of Ubuntu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I installed Steam, the launcher opened. However, instead of
  showing the icon, which the Gnome launchpad did, the side-bar showed
  no icon and only showed "Unknown" as the title, even though the window
  is titled "steam".

  To reproduce, simply download Steam from the steam website, run dpkg
  -i on the deb, and run the launcher after downloading the
  prerequisites.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 21:36:35 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-control-center', 'update-manager', 'firefox', 'apport-gtk', 
'transmission-gtk']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Steam is shown on Gnome as being "unknown" without any icon, even
  though the steam launcher is simply downloading an update and the icon
  appears on previous versions of Ubuntu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I installed Steam, the launcher opened. However, instead of
  showing the icon, which the Gnome launchpad did, the side-bar showed
  no icon and only showed "Unknown" as the title, even though the window
  is titled "steam".

  To reproduce, simply download Steam from the steam website, run dpkg
  -i on the deb, and run the launcher after downloading the
  prerequisites.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 21:36:35 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-control-center', 'update-manager', 'firefox', 'apport-gtk', 
'transmission-gtk']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1874950] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1874950/+attachment/5359959/+files/ShellJournal.txt

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

Title:
  Steam is shown on Gnome as being "unknown" without any icon, even
  though the steam launcher is simply downloading an update and the icon
  appears on previous versions of Ubuntu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I installed Steam, the launcher opened. However, instead of
  showing the icon, which the Gnome launchpad did, the side-bar showed
  no icon and only showed "Unknown" as the title, even though the window
  is titled "steam".

  To reproduce, simply download Steam from the steam website, run dpkg
  -i on the deb, and run the launcher after downloading the
  prerequisites.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 21:36:35 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-control-center', 'update-manager', 'firefox', 'apport-gtk', 
'transmission-gtk']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1874950] [NEW] Steam is shown on Gnome as being "unknown" without any icon, even though the steam launcher is simply downloading an update and the icon appears on previous vers

Public bug reported:

When I installed Steam, the launcher opened. However, instead of showing
the icon, which the Gnome launchpad did, the side-bar showed no icon and
only showed "Unknown" as the title, even though the window is titled
"steam".

To reproduce, simply download Steam from the steam website, run dpkg -i
on the deb, and run the launcher after downloading the prerequisites.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 21:36:35 2020
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
 b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-control-center', 'update-manager', 'firefox', 'apport-gtk', 
'transmission-gtk']"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2020-04-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
 
InstallationDate: Installed on 2020-04-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: gnome-shell 3.36.1-5ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
Tags:  focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True

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


** Tags: amd64 apport-bug apport-collected focal

** Attachment added: "Screenshot from 2020-04-24 21-40-58.png"
   
https://bugs.launchpad.net/bugs/1874950/+attachment/5359953/+files/Screenshot%20from%202020-04-24%2021-40-58.png

** Tags added: apport-collected

** Description changed:

  When I installed Steam, the launcher opened. However, instead of showing
  the icon, which the Gnome launchpad did, the side-bar showed no icon and
  only showed "Unknown" as the title, even though the window is titled
  "steam".
  
  To reproduce, simply download Steam from the steam website, run dpkg -i
  on the deb, and run the launcher after downloading the prerequisites.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 21:36:35 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-control-center', 'update-manager', 'firefox', 'apport-gtk', 
'transmission-gtk']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ GsettingsChanges:
+  
+ InstallationDate: Installed on 2020-04-25 (0 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: gnome-shell 3.36.1-5ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForU

[Desktop-packages] [Bug 1852860] Re: Display settings not saved across sessions if fractional scaling is used

2020-04-24 Thread Daniel Rammelt

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

Same issue here on fresh install of 20.04

Apr 25 13:28:28 xxx systemd[1798]: Starting GNOME Shell on X11...
Apr 25 13:28:28 xxx gnome-shell[10304]: Enabling experimental feature 
'x11-randr-fractional-scaling'
Apr 25 13:28:28 xxx /usr/lib/gdm3/gdm-x-session[10123]: (II) AMDGPU(0): EDID 
vendor "GSM", prod id 23305
...
Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config file 
'/home/xxx/.config/monitors.xml': Logical monitors not adjacent

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

Title:
  Display settings not saved across sessions if fractional scaling is
  used

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

Bug description:
  I am using:

  - Ubuntu 19.10
  - Nvidia gtx1080
  - nvidia xserver installed
  - two 4k monitors

  
  I changed the scaling and order of monitors in Ubuntu Display settings.

  However when I reboot or logout/login the display settings reset and i
  have to set them all over again each time.

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

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

[Desktop-packages] [Bug 1874941] [NEW] lag and hangs

2020-04-24 Thread Jofen Kihlström

Public bug reported:

Since upgrading from ubuntu 18.04 I have not been able to stream video
from youtube without the video freezing for a second or two every 30
seconds. Also when filling out this form the text lag. This has not been
the case on this computer when using 18.04, 19.04 or 19.10.

This performance issue renders the computer hard to use for work and I
am almost completly certain that it is xorg or some other graphics
issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 25 01:52:12 2020
DistUpgraded: 2020-04-23 23:49:11,187 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
MachineType: HUAWEI MACH-WX9
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e5a15015-60f2-4474-a116-bd9e25289d5f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
dmi.bios.date: 03/15/2019
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.28
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M13
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M13
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
dmi.product.family: MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C189
dmi.product.version: M13
dmi.sys.vendor: HUAWEI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal performance ubuntu

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

Title:
  lag and hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading from ubuntu 18.04 I have not been able to stream video
  from youtube without the video freezing for a second or two every 30
  seconds. Also when filling out this form the text lag. This has not
  been the case on this computer when using 18.04, 19.04 or 19.10.

  This performance issue renders the computer hard to use for work and I
  am almost completly certain that it is xorg or some other graphics
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 01:52:12 2020
  DistUpgraded: 2020-04-23 23:49:11,187 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e5a15015-60f2-4474-a116-bd9e25289d5f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M13
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dm

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

2020-04-24 Thread Gilyén András

This bug also affects me on a fresh 20.04 install ...

To Jacob: You can just copy the link, by right clicking the "join meeting" 
button, then open a terminal and type
$ xdg-open "zoommtg://...[your meeting link]..."

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1784163] Re: gnome-initial-setup hangs enabling livepatch

2020-04-24 Thread Navjot

I can confirm that this issue is still present in Ubuntu 20.04.

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

Title:
  gnome-initial-setup hangs enabling livepatch

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

Bug description:
  I just upgraded from Artful to Bionic. gnome-initial-setup ran. It
  asked me if I wanted to enable Livepatch, and I agreed. I believe my
  Internet connection was working fine at the time. It gave me a
  username/password prompt. After entering those in it asked me for a
  2FA code. After entering that in, I got a spinner with "Connecting..."
  in the bottom left, but nothing further happens. It's been about ten
  minutes hung like that.

  I tried to click the Cancel button but nothing happened. Then I tried
  to close the app from the bar on the left (right click -> Quit) but
  nothing happened.

  After the previous actions, netstat reports no TCP connections on IPv4
  nor IPv6. It's appears not to be "Connecting" to anything.

  Expected: at least some kind of timeout reporting failure so I can
  progress with any other "initial setup" actions.

  A few things about my installation:

  I installed this laptop with Artful initially, around the beta1
  milestone. I dist upgraded it to Artful after release. Before
  upgrading to Bionic I made sure it was fully up to date.

  apport-bug didn't work. After I click Send, I got no browser prompt to
  finish my report. This might be because I have an unusual Firefox
  setup (multiple profiles).

  I noticed that I have bionic-proposed enabled. This is unintentional.
  It seems likely that I had artful-proposed enabled for test purposes
  previously. I did have a pin deprioritising it, but it refers to
  artful specifically so doesn't seem to have acted on Bionic, so
  unfortunately I've ended up upgrading all the way up to bionic-
  proposed.

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

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

[Desktop-packages] [Bug 1852023] Re: Wayland doesn't work in GMA500

2020-04-24 Thread James

Wayland now works for the psb/cdv variants of gma500 as of kernel
version v5.6 using the open source mainline kernel unaccelerated gma500
driver.

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

Title:
  Wayland doesn't work in GMA500

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I had to disable Wayland in GDM3 in order to be able to login.
  I guess an udev rule to disable Wayland for GMA500 is all that is needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 19:14:19 2019
  DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller [1179:fc10]
  InstallationDate: Installed on 2012-07-29 (2660 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: TOSHIBA TOSHIBA NB515
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago)
  dmi.bios.date: 4/3/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Dolphin10
  dmi.product.name: TOSHIBA NB515
  dmi.product.sku: PLL72P-013LM1
  dmi.product.version: PLL72P-013LM1
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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
  xserver.bootTime: Mon Jul  1 17:43:10 2019
  xserver.configfile: default
  xserver.errors:
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

2020-04-24 Thread Pablo Carballo

** Description changed:

- My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
- now screen resolution is 800x600. I verified the detected version of
- NVIDIA driver and I realized it was 440, but correct version is 390.
- Finally I changed version to 390 and now the graphics are  working OK.
+ My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
+ I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.
  
- This issue was not present in previous versions (19.10 and 18.04)
+ This is the output for the command "$ lspci -nn":
+ 
+ 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
+ 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)
+ 
+ 
+ This is the output for the command "# ubuntu-drivers devices":
+ 
+ == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
+ modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
+ vendor   : NVIDIA Corporation
+ model: GF116 [GeForce GTX 550 Ti]
+ driver   : nvidia-driver-435 - distro non-free
+ driver   : nvidia-driver-390 - distro non-free
+ driver   : nvidia-driver-440 - distro non-free recommended
+ driver   : nvidia-340 - distro non-free
+ driver   : xserver-xorg-video-nouveau - distro free builtin
+ 
+ The version 440 is recommended, but it's not correct for this model (390
+ should be recommended instead)
+ 
+ 
+ The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

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

Bug description:
  My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
  I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.

  This is the output for the command "$ lspci -nn":

  01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

  
  This is the output for the command "# ubuntu-drivers devices":

  == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
  modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GF116 [GeForce GTX 550 Ti]
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  The version 440 is recommended, but it's not correct for this model
  (390 should be recommended instead)

  
  The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

2020-04-24 Thread Pablo Carballo

** Tags added: driver

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

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

Bug description:
  My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
  now screen resolution is 800x600. I verified the detected version of
  NVIDIA driver and I realized it was 440, but correct version is 390.
  Finally I changed version to 390 and now the graphics are  working OK.

  This issue was not present in previous versions (19.10 and 18.04)

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

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

[Desktop-packages] [Bug 1848643] Re: [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No sound at all

2020-04-24 Thread Gong Chen

Thanks Daniel. It works for me.

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

Title:
  [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  it can not automatic switching between speakers and headphone.
  The question is similar 
with:https://community.clearlinux.org/t/automatic-switching-between-speakers-and-headphones/916

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 18 15:45:57 2019
  InstallationDate: Installed on 2019-10-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  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:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [WRT-WX9, Realtek ALC256, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.19
  dmi.board.name: WRT-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.19:bd08/12/2019:svnHUAWEI:pnWRT-WX9:pvrM1020:rvnHUAWEI:rnWRT-WX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook
  dmi.product.name: WRT-WX9
  dmi.product.sku: C233
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI

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

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

[Desktop-packages] [Bug 1874930] [NEW] package gnome-initial-setup (not installed) failed to install/upgrade: Versuch, »/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop« zu überschreiben, we

2020-04-24 Thread Leonie 🏳️‍🌈

Public bug reported:

This message just popped up so I hit send

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: gnome-initial-setup (not installed)
ProcVersionSignature: Ubuntu 5.4.0-7625.29~1587437458~20.04~2960161-generic 
5.4.30
Uname: Linux 5.4.0-7625-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 23 17:49:19 2020
ErrorMessage: Versuch, 
»/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop« zu überschreiben, 
welches auch in Paket pop-gnome-initial-setup 3.36.1~1587055870~20.04~0f10d6b 
ist
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: gnome-initial-setup
Title: package gnome-initial-setup (not installed) failed to install/upgrade: 
Versuch, »/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop« zu 
überschreiben, welches auch in Paket pop-gnome-initial-setup 
3.36.1~1587055870~20.04~0f10d6b ist
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package gnome-initial-setup (not installed) failed to install/upgrade:
  Versuch, »/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop«
  zu überschreiben, welches auch in Paket pop-gnome-initial-setup
  3.36.1~1587055870~20.04~0f10d6b ist

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  This message just popped up so I hit send

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gnome-initial-setup (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-7625.29~1587437458~20.04~2960161-generic 
5.4.30
  Uname: Linux 5.4.0-7625-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 23 17:49:19 2020
  ErrorMessage: Versuch, 
»/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop« zu überschreiben, 
welches auch in Paket pop-gnome-initial-setup 3.36.1~1587055870~20.04~0f10d6b 
ist
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: gnome-initial-setup
  Title: package gnome-initial-setup (not installed) failed to install/upgrade: 
Versuch, »/etc/xdg/autostart/gnome-initial-setup-copy-worker.desktop« zu 
überschreiben, welches auch in Paket pop-gnome-initial-setup 
3.36.1~1587055870~20.04~0f10d6b ist
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874914] Re: screen size too big / title bar on second screen

2020-04-24 Thread anderson.de...@gmail.com

If I make any adjustments via nvidia settings (such as slightly
repositioning the screens) everything goes back to normal.

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

Title:
  screen size too big / title bar on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
   virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2018-05-23 (702 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1874914] Re: screen size too big / title bar on second screen

2020-04-24 Thread anderson.de...@gmail.com

Yes, my second screen (1920x1200) is rotated.

Bug #1874567 says the rotation doesn't work, that it stays in landscape.
My screen rotation does work correctly.

When using the nouveau drivers it never gets past the purple boot screen
(tho I can ssh in fine).

When I scroll to the right, the title bar lines up correctly to the
first screen.  (Another pic attached.)  Notice also the backgrounds
overlap.


** Attachment added: "IMG_20200424_145615.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874914/+attachment/5359859/+files/IMG_20200424_145615.jpg

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

Title:
  screen size too big / title bar on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
   virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2018-05-23 (702 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

Re: [Desktop-packages] [Bug 1874562] Re: MTP android device (usb) doesn't appear in files

2020-04-24 Thread Thjorven Rubach

Thanks for the reply.

The relevant journactl output (at least from what I can guess) follows, 
I attached both full command outputs as txt files. It reconnects because 
you have to change from no data transfer to file transfer in the android 
settings, but I did the same in 18.04 and it worked there.


Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: new high-speed USB 
device number 20 using xhci_hcd
Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: New USB device found, 
idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40
Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: Product: Pixel 2
Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: Manufacturer: Google
Apr 24 14:48:39 thjorvens-laptop kernel: usb 3-2: SerialNumber: HT84L1A01541
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: USB disconnect, device 
number 20
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: new high-speed USB 
device number 21 using xhci_hcd
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: New USB device found, 
idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: Product: Pixel 2
Apr 24 14:48:52 thjorvens-laptop kernel: usb 3-2: Manufacturer: Google


** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/bugs/1874562/+attachment/5359857/+files/journalctl.txt

** Attachment added: "mtp.txt"
   https://bugs.launchpad.net/bugs/1874562/+attachment/5359858/+files/mtp.txt

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

Title:
  MTP android device (usb) doesn't appear in files

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Steps to recreate this:

  Connect an android phone to the computer
  enable file sharing from the notification

  Expected:
  Be able to access the phone from the file application

  Currently:
  Doesn't show up.

  This was working in 18.04. I can also see the device using lsusb as
  `Bus 003 Device 017: ID 18d1:4ee1 Google Inc. Nexus Device (MTP)`. If
  I can help debugging this further please guide me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 16:48:53 2020
  GsettingsChanges: b'org.gnome.nautilus.preferences' 
b'search-filter-time-type' b"'last_used'"
  InstallationDate: Installed on 2020-02-07 (76 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-24 Thread Adam Dyess

full hardware profile: https://linux-
hardware.org/index.php?probe=c17da47049

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1874925] [NEW] Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-24 Thread Adam Dyess

Public bug reported:

Internal Microphone doesn't show up as an audio source.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  addyess   106482 F pulseaudio
 /dev/snd/controlC1:  addyess   106482 F pulseaudio
 /dev/snd/controlC0:  addyess   106482 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Fri Apr 24 16:56:54 2020
InstallationDate: Installed on 2019-11-05 (171 days ago)
InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 863F
dmi.board.vendor: HP
dmi.board.version: 54.13
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
dmi.product.sku: 8LK66UA#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1811504] [NEW] Scan with HP Laserjet Pro M28 fails

You have been subscribed to a public bug:

I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I
always get this error when scanning using SANE:

error: SANE: Error during device I/O (code=9)

I’ve installed hplip hplip-plugins and any other dependencies listed in
hp-check but without luck.

any hints?

** Affects: hplip (Ubuntu)
 Importance: Undecided
 Status: Fix Released

-- 
Scan with HP Laserjet Pro M28 fails
https://bugs.launchpad.net/bugs/1811504
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to hplip 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 1874626] Re: dav path not complete

Thanks

** Changed in: nautilus (Ubuntu)
   Status: New => Triaged

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

Title:
  dav path not complete

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  If I open this kind of path (Nextcloud):
  davs://{SERVER}/remote.php/dav/files/{USER@DOMAIN}

  Nautilus shows me the correct directory but setup the rootpath to
  davs://{SERVER}/remote.php/dav/

  The Problem is, that I'n not able to use the mounted path for anything
  because I'm not able to navigate into the directory /files/

  Please change behavior that way that if I enter a directory path to
  open a path, it should be set as the route of the Mount in whole.

  Ubuntu 19.10

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

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

[Desktop-packages] [Bug 1865071] Re: Power indicator doesn't show when charging (eoan)

The upower log has 
state:   discharging
likely a kernel issue rather than userspace one

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

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

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

Title:
  Power indicator doesn't show when charging (eoan)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt 
 wrote:
  No problem. I suggest the least confusing way for us to discuss that new
  problem is to open a new bug by running:

    ubuntu-bug gnome-shell

  -- 
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1845578

  
  This is almost the same issue as my previous bug with disco, but I've noticed 
that if I'm plugged in before I boot, then the indicator knows it.  But not if 
I plug in while the computer is awake or suspended/hibernating.  If I plug in 
while it's suspended or hibernating, the indicator doesn't update.


  jen@jenius:~$ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 27 10:41:44 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-18 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago)

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

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

[Desktop-packages] [Bug 1874914] Re: screen size too big / title bar on second screen

Thank you for your bug report. Do you use your second screen as rotated?
Sounds a bit similar to bug #1874567. Do you get the issue if you
disable the nvidia binary driver?

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

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

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

Title:
  screen size too big / title bar on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
   virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2018-05-23 (702 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1811504] Re: Scan with HP Laserjet Pro M28 fails

2020-04-24 Thread pi4630

** Summary changed:

- scan with Laserjet MFP-M28 fails
+ Scan with HP Laserjet Pro M28 fails

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

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

Title:
  Scan with HP Laserjet Pro M28 fails

Status in hplip package in Ubuntu:
  Fix Released

Bug description:
  I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I
  always get this error when scanning using SANE:

  error: SANE: Error during device I/O (code=9)

  I’ve installed hplip hplip-plugins and any other dependencies listed
  in hp-check but without luck.

  any hints?

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

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

[Desktop-packages] [Bug 1874845] Re: No keyboard interaction on desktop icons

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

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 1868924, 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 1868924
a desktop launcher icon can not be activated by focusing and pressing enter

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

Title:
No keyboard interaction on desktop icons

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
New

Bug description:
Hi,
There is no keyboard interaction on desktop icons (arrow keys have no effect,
enter key won't open files, etc.).

How to reproduce :
1) have some icons on your desktop.
2) select it with mouse
3) try to move using arrow keys, or open it with enter : nothing happens

Fresh install of focal...
Am I doing something wrong?

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

[Desktop-packages] [Bug 1874848] Re: Opening folders lead to ghost pages to be created

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

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 1870847, 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 1870847
   App grid has too many page dots on right

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

Title:
  Opening folders lead to ghost pages to be created

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When opening folders, the shell creates many ghost pages (demo
  attached in webm format). Clicking on the page 'dots' doesn't do
  anything for the ghost pages.

  Disabling remember-app-usage solves this bug, because it removes the
  Frequents/All apps tab at the bottom of the application menu that
  seems to be 'clashing' with the folder display.

  Display resolution is 1366x768 on a 14 inch laptop display. Laptop is
  the HP Pavilion x360 Convertible 14-ba0xx using Intel HD Graphics 620.

  This bug did not occur under GNOME 3.34 on Ubuntu 19.10, where this
  current install was upgraded from. This also occurs on fresh
  installations of Ubuntu 20.04.

  Moreover, while not possibly directly related to this issue, the app
  running dots below the app names don't have enough padding and clash
  with the text (screenshot attached).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 23:46:03 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-22 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

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

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

[Desktop-packages] [Bug 1865824] Re: Upgrade to 20.04 removes saved fingerprints

2020-04-24 Thread Brian Murray

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  Upgrade to 20.04 removes saved fingerprints

Status in Release Notes for Ubuntu:
  Fix Released
Status in fprintd package in Ubuntu:
  Confirmed

Bug description:
  18.04 Ubuntu MATE upgraded to 20.04 Ubuntu MATE on 2 March 2020.

  T430N

  Upgrade competes and reboots. Upon reboot login screen appears and
  there is no prompt to login using fingerprint scanner.

  After login using password the user needs to:

  run fprintd-enroll and fingerprints are enrolled.

  On logout/reboot login using fingerprint scanner is available.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fprintd 1.90.1-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Mar  2 22:21:29 2020
  InstallationDate: Installed on 2019-12-05 (88 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: fprintd
  UpgradeStatus: Upgraded to focal on 2020-03-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1865824/+subscriptions

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

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

Could you add the journal log?

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

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

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

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

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

[Desktop-packages] [Bug 1865411] Re: Need to restart Network Manager frequently

2020-04-24 Thread Daniel

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  Need to restart Network Manager frequently

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My WiFi connection keeps stopping to work every once in a while
  (sometimes as often as every 10 minutes).

  Restarting NetworkManager usually resolves this problem. But I am not
  sure why that is the case. I do not think there is a connectivity
  issue as it happens even when I am right next to the access point.

  I have a standard Intel Wireless chip and use GNOME shell with some
  extensions. Nothing exotic.

  Note this happened on eoan as well as focal (and maybe even before
  that).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.8-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 19:56:11 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-07-09 (236 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/fish
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.8   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread Mathew Hodson

** Tags removed: verification-needed

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

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

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

[Desktop-packages] [Bug 1754702] Re: Delay before you can type after switching input source

2020-04-24 Thread Stanislav

I just have installed Ubuntu 20.04 and this bug is still there (after
switching layout everything on system freezes on a second). I had
created question on askubuntu for 19.10 version
https://askubuntu.com/questions/1211801/ubuntu-19-10-change-keyboard-
language-freeze with video that displays freeze
https://youtu.be/zIb2p1n80pA

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

Title:
  Delay before you can type after switching input source

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

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

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

[Desktop-packages] [Bug 1874916] [NEW] whatsapp doesn't recognize chromium snap user agent

2020-04-24 Thread Carlos Pita

Public bug reported:

At some time there was the issue of Whatsapp not recognizing the user
agent of Chromium, which was closed because it was the understanding
that the problem should be fixed by Whatsapp and not Ubuntu:

https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1808853?comments=all

I agree with the rationale there, but later Whatsapp seems to indeed
have fixed that, at least according to Olivier Tilloy:

> It looks like whatsapp fixed the user agent detection for the chromium
ubuntu packages, this is now working fine. However it's still refusing
to work with the chromium snap package.


(see 
https://groups.google.com/a/chromium.org/forum/#!msg/chromium-discuss/MbfH-OZGbLc/4JhhGlg-CgAJ)

So, since Canonical has reasons to promote the snap Chromium package as
the official Chromium package, which is announced as supported by
Ubuntu, it seems to me that the snap bug does belong here.

I'm reporting the problem for:
  * Chromium snap latest/stable 81.0.4044.122 2020-04-23
  * Ubuntu 20.04

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  whatsapp doesn't recognize chromium snap user agent

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  At some time there was the issue of Whatsapp not recognizing the user
  agent of Chromium, which was closed because it was the understanding
  that the problem should be fixed by Whatsapp and not Ubuntu:

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1808853?comments=all

  I agree with the rationale there, but later Whatsapp seems to indeed
  have fixed that, at least according to Olivier Tilloy:

  > It looks like whatsapp fixed the user agent detection for the
  chromium ubuntu packages, this is now working fine. However it's still
  refusing to work with the chromium snap package.

  
  (see 
https://groups.google.com/a/chromium.org/forum/#!msg/chromium-discuss/MbfH-OZGbLc/4JhhGlg-CgAJ)

  So, since Canonical has reasons to promote the snap Chromium package
  as the official Chromium package, which is announced as supported by
  Ubuntu, it seems to me that the snap bug does belong here.

  I'm reporting the problem for:
* Chromium snap latest/stable 81.0.4044.122 2020-04-23
* Ubuntu 20.04

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

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

[Desktop-packages] [Bug 1874914] [NEW] screen size too big / title bar on second screen

2020-04-24 Thread anderson.de...@gmail.com

Public bug reported:

The title bar stretches ~1/2 way onto the second screen.
Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
Picture attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 14:00:34 2020
DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
 virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701]
InstallationDate: Installed on 2018-05-23 (702 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67GD
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10206-207
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "picture of screen size error"
   
https://bugs.launchpad.net/bugs/1874914/+attachment/5359828/+files/IMG_20200424_140123.jpg

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

Title:
  screen size too big / title bar on second screen

Status in xorg package in Ubuntu:
  New

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-04-24 Thread David Bridson

I'm experiencing the same problem on a fresh install of Ubuntu Mate
20.04 on a Dell XPS 13 9350.

Sound works correctly using the internal speakers. If you plug in analog
headphones to the 3.5mm jack, there is no sound from the headphones or
the internal speakers. All relevant options are unmuted in Sound
Settings. The Speaker Test exhibits the same behaviour.

Analog headphones worked correctly on this system under 18.04.

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Status in gnome-control-center:
Unknown
Status in PulseAudio:
New
Status in gnome-control-center package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in gnome-control-center source package in Focal:
Invalid
Status in pulseaudio source package in Focal:
In Progress

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

2020-04-24 Thread Pablo Carballo

Set the most probable package.

** Package changed: ubuntu => ubuntu-drivers-common (Ubuntu)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

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

Bug description:
  My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
  now screen resolution is 800x600. I verified the detected version of
  NVIDIA driver and I realized it was 440, but correct version is 390.
  Finally I changed version to 390 and now the graphics are  working OK.

  This issue was not present in previous versions (19.10 and 18.04)

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

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

[Desktop-packages] [Bug 1874874] [NEW] Focal detects wrong driver version 440 for NVIDIA GTX 550

You have been subscribed to a public bug:

My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
now screen resolution is 800x600. I verified the detected version of
NVIDIA driver and I realized it was 440, but correct version is 390.
Finally I changed version to 390 and now the graphics are  working OK.

This issue was not present in previous versions (19.10 and 18.04)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment focal nvidia
-- 
Focal detects wrong driver version 440 for NVIDIA GTX 550
https://bugs.launchpad.net/bugs/1874874
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ubuntu-drivers-common 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

Re: [Desktop-packages] [Bug 1872842] Re: PCI/internal sound card not detected

2020-04-24 Thread Michael

Follow-up, and bug can be closed, hardware issue.

For the record, I do think that the frustration in the original bug 
report does point out that there is a need for a low level testing tool, 
to help identify if it is an actual hardware issue, or a problem with 
detection, or the drivers etc..

Out of frustration, I ended up calling the vendor (Lenovo) and while I 
haven't been happy with their hardware historically, and don't laugh 
that I ended up buying a ThinkCentre for a Linux station, I was 
pleasantly surprised with their support.

I was able to get a hold of a human almost right away, but I do think 
that Lenovo has a known hardware issue, that they only tell people about 
if they call for support.  AS soon as I mentioned 'audio' problems, he 
surprised me by not questioning it at all, and that 'they would send a 
technician out to replace the motherboard'.

(I thought he would at least put me through a testing song and dance, 
but no, no questions asked.. 4 minutes later off the phone)

Took about 10 days, but true to their word, motherboard was shipped, and 
technician showed up, replaced the motherboard, and all sound devices 
detected on boot, immediately.  (No changes need to sound configuration)

I guess it passes the hardware compatability with 16.04 ;)

Thanks all for your comments though.. but consider that some form of 
'testing' tool, should have come to the conclusion this was a hardware 
issue and saved me a few days of learning low level alsa/sound.

On 2020-04-14 5:44 p.m., Hui Wang wrote:
> Is there an audio enable option in the BIOS? Maybe it is disabled?
> 
> Or the codec is damaged physically? You could install the newer kernel
> to verify if the codec is good or not, if it is good and newer kernel
> could work, then we will bisect the kernel to find the fix for this
> issue.
>

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Upsstream says try a newer kernel, but I am on the LTS HWE kernels for
  Xenial, and want to solve this on this version.  This is a Think
  Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads,
  but finds no codecs.  This is the onboard audio card, and don't think
  they have chnaged it much in years, so I expect that at least SOME
  codecs should be detected.  Played with various alsa conf settings, no
  joy..

  options snd-hda-intel single_cmd=1
  options snd-hda-intel probe_mask=1
  options snd-hda-intel model=thinkpad
  options snd-hda-intel position_fix=3

  Tried model(s) generic, and auto.. always the same in bootup..

  [   12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
  [   12.830129] snd_hda_intel :00:1f.3: no codecs found!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr 14 15:00:59 2020
  InstallationDate: Installed on 2019-11-03 (163 days ago)
  InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1ZKT23A
  dmi.board.name: 313C
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305181519567
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710e
  dmi.product.name: 10UR001JUS
  dmi.product.version: ThinkCentre M710e
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423

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

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

[Desktop-packages] [Bug 933394] Re: mscompress creates files with wrong header on amd64

2020-04-24 Thread zapman

** Changed in: mscompress (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  mscompress creates files with wrong header on amd64

Status in mscompress package in Ubuntu:
  Fix Released

Bug description:
  When I compress a file with mscompress on Ubuntu 10.04.4 LTS amd64,
  the compressed file is indeed created with "_" appended to the file
  name; but when I try to decompress that file with msexpand I get the
  following error message: "This is not a MS-compressed file" -- and the
  file is expanded correctly. A file command on the compressed item
  returns only "data", whereas it should be "MS Compress archive data".

  I tried with an Ubuntu 10.04.3 i386 LiveCD with which the file command
  returned the correct answer and msexpand didn't return any error
  messages, so it's probably an architecture problem. Many thanks to
  Stefan Handschuh, the developer of jAOLT, who advised to use the file
  command and suggested that the header could be incorrect.

  A terminal output would probably be more explanatory:

  zapman@ubuntu:~/mscompress_test$ mscompress -V
  mscompress version 0.3 (yellow) Mar  7 2010 
  zapman@ubuntu:~/mscompress_test$ mscompress TODO.txt 
  zapman@ubuntu:~/mscompress_test$ dir
  TODO.txt  TODO.txt_
  zapman@ubuntu:~/mscompress_test$ file TODO.txt_ 
  TODO.txt_: data
  zapman@ubuntu:~/mscompress_test$ mv TODO.txt .. #so that msexpand doesn't say 
"File exists"
  zapman@ubuntu:~/mscompress_test$ msexpand TODO.txt_ 
  TODO.txt_: This is not a MS-compressed file
  zapman@ubuntu:~/mscompress_test$ dir
  TODO.txt  TODO.txt_

  You can see the reply of the file command which should have been "MS
  Compress archive data" instead of just "data", and the error message
  from msexpand which says "This is not a MS-compressed file" and which
  shouldn't have appeared.

  Additional information: lsb_release -rd returns: 
  Description:  Ubuntu 10.04.4 LTS
  Release:  10.04
  uname -a returns:
  Linux ubuntu 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC 2012 
x86_64 GNU/Linux
  apt-cache policy mscompress returns:
  mscompress:
Installed: 0.3-3build1
Candidate: 0.3-3build1
Version table:
   *** 0.3-3build1 0
  500 ftp://ftp.rrzn.uni-hannover.de/pub/mirror/linux/ubuntu/ 
lucid/main Packages
  100 /var/lib/dpkg/status

  PS: You may also want to take a look at the Debian bug n° 600549 for
  this package on . It even includes a patch :)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mscompress 0.3-3build1
  ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
  Uname: Linux 2.6.32-38-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 3b8b1e94677feb8b107502acb9f14c2c
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Thu Feb 16 11:00:48 2012
  ProcEnviron:
   LANGUAGE=en_AU:en_GB:en
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SourcePackage: mscompress

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

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Norbert

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874626] Re: dav path not complete

2020-04-24 Thread AdlerHorst

The Link to the Gnome bug tracker at at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME is not anymore correct.
Gnome moved their bug tracker.

I created a new Issue.
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1465

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

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

Title:
  dav path not complete

Status in nautilus package in Ubuntu:
  New

Bug description:
  If I open this kind of path (Nextcloud):
  davs://{SERVER}/remote.php/dav/files/{USER@DOMAIN}

  Nautilus shows me the correct directory but setup the rootpath to
  davs://{SERVER}/remote.php/dav/

  The Problem is, that I'n not able to use the mounted path for anything
  because I'm not able to navigate into the directory /files/

  Please change behavior that way that if I enter a directory path to
  open a path, it should be set as the route of the Mount in whole.

  Ubuntu 19.10

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

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

Re: [Desktop-packages] [Bug 1865071] Re: Power indicator doesn't show when charging (eoan)

2020-04-24 Thread Jen

jen@jenius:~$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
   native-path:  AC0
   power supply: yes
   updated:  Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago)
   has history:  no
   has statistics:   no
   line-power
     warning-level:   none
     online:  yes
     icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
   native-path:  BAT0
   vendor:   ASUSTeK
   model:    ASUS Battery
   power supply: yes
   updated:  Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago)
   has history:  yes
   has statistics:   yes
   battery
     present: yes
     rechargeable:    yes
     state:   discharging
     warning-level:   none
     energy:  14.208 Wh
     energy-empty:    0 Wh
     energy-full: 33.409 Wh
     energy-full-design:  37.13 Wh
     energy-rate: 15.809 W
     voltage: 7.85 V
     time to empty:   53.9 minutes
     percentage:  42%
     capacity:    89.9785%
     technology:  lithium-ion
     icon-name:  'battery-good-symbolic'
   History (charge):
     1587756140    42.000    discharging
     1587756076    43.000    discharging
   History (rate):
     1587756140    15.809    discharging
     1587756076    15.001    discharging

Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
   native-path:  hidpp_battery_0
   model:    Wireless Mouse MX Master
   serial:   4060-e6-d2-a0-c0
   power supply: no
   updated:  Fri 24 Apr 2020 12:21:16 PM MST (65 seconds ago)
   has history:  yes
   has statistics:   yes
   mouse
     present: yes
     rechargeable:    yes
     state:   unknown
     warning-level:   none
     battery-level:   unknown
     percentage:  50% (should be ignored)
     icon-name:  'battery-missing-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
   power supply: yes
   updated:  Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago)
   has history:  no
   has statistics:   no
   battery
     present: yes
     state:   discharging
     warning-level:   none
     energy:  14.208 Wh
     energy-full: 33.409 Wh
     energy-rate: 15.809 W
     time to empty:   53.9 minutes
     percentage:  42%
     icon-name:  'battery-good-symbolic'

Daemon:
   daemon-version:  0.99.11
   on-battery:  no
   lid-is-closed:   no
   lid-is-present:  yes
   critical-action: PowerOff


On 4/17/20 12:20 AM, Sebastien Bacher wrote:
> Thank you for your bug report. Could you add a 'upower -d' log when
> getting the issue?
>
> ** Changed in: gnome-shell (Ubuntu)
> Importance: Undecided => Low
>
> ** 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/1865071

Title:
  Power indicator doesn't show when charging (eoan)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt 
 wrote:
  No problem. I suggest the least confusing way for us to discuss that new
  problem is to open a new bug by running:

    ubuntu-bug gnome-shell

  -- 
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1845578

  
  This is almost the same issue as my previous bug with disco, but I've noticed 
that if I'm plugged in before I boot, then the indicator knows it.  But not if 
I plug in while the computer is awake or suspended/hibernating.  If I plug in 
while it's suspended or hibernating, the indicator doesn't update.


  jen@jenius:~$ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 27 10:41:44 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-18 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago)

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

-- 
Mailing list: https://launchpad

[Desktop-packages] [Bug 1871359] Re: Ubuntu Cant switch languages- shortcut alt+shift doesnt work

2020-04-24 Thread Gunnar Hjalmarsson

On 2020-04-24 20:20, Kangarooo Jānis wrote:
> Well cant switch keyboard

If you have added some keyboard layout(s), so you have two or more
layouts available, I'm pretty sure you can switch between them using the
default shortcut + (or by using the input source menu in
the top bar).

> and default in other OS is left sides alt+shift

In Ubuntu/GNOME it's not. But, as I explained in a previous comment,
there is a way to make + work.

I don't see a bug here, so closing. If you need help with using Ubuntu,
please seek support in for instance some of the places mentioned here:

https://ubuntu.com/support/community-support

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

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

Title:
  Ubuntu Cant switch languages- shortcut alt+shift doesnt work

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

Bug description:
  Ubuntu Cant switch languages- shortcut alt+shift doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 10:59:16 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874837] Re: package chromium-browser (not installed) failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1

That warning can be safely ignored. Glad to know that the reinstall
worked.

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  »neues chromium-browser-Skript des Paketes pre-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  This happens while installing chromium (snap) with synaptic, together
  with different other applications.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 17:17:36 2020
  ErrorMessage: »neues chromium-browser-Skript des Paketes 
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
»neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab 
den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870424] Re: Can not add server cert

2020-04-24 Thread mike Bernson

1 hit the 3 dots in upper conner
2 Hit the Privcay and Security
3 hit authorities tab
4 hit the import button

Then I get:
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied


I just try the import now and it worked.

I assume the problem was fixed as it now show me my home directory and allow me 
to import the
need certs for local domains so that https does not cause the popup when 
accessing 
local machines

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

Title:
  Can not add server cert

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  When I try to add Server Cert to chromium-browser I get the following message
  Could Not read the contents of void
  Error opening directory '/var/lib/snap/void': Permission denied

  This worked on 18.04 but not 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+tCACEcAQS1IhN4Au+Vo1Q1tSYPUFQBAQEBAQEBAQEBAQEBAQEBUtAAoPBwPoAwIDUAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WkFOMDQuMiAKAZoCAw8A4wWAAOYGBQFgYCgAqg==
   modes: 3840x2160
  Date: Thu Apr  2 15:55:40 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   pool/home  zfs1.3T  148G  1.2T  12% /home
   tmpfs  tmpfs   32G   45M   32G   1% /dev/shm
   pool/home  zfs1.3T  148G  1.2T  12% /home
  InstallationDate: Installed on 2020-03-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QNCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic 
root=UUID=6973399c-724d-4607-985d-9426190dc41b ro VGA=1920x1080
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   7Done2020-04-01T21:41:35-04:00  2020-04-01T21:41:52-04:00  
Auto-refresh snap "chromium"
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.162 
(f2c5dd6138153bb0658091205bd1a1717f16081a-refs/branch-heads/3987@{#1034})
  Snap.ChromiumVersion: Chromium 80.0.3987.162 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QNCTO1WW:pvrThinkPadP53:rvnLENOVO:rn20QNCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P53
  dmi.product.name: 20QNCTO1WW
  dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53
  dmi.product.version: ThinkPad P53
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1874871] Re: Wrong screen offset dual monitors

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

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

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

Title:
  Wrong screen offset dual monitors

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I change screen position in gnome-settings, or reboot computer screens 
overlap.
  I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:55:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02]
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_efifg2@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_efifg2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871360] Re: Ubuntu Cant find keyboard layout languages

2020-04-24 Thread Gunnar Hjalmarsson

Thanks, now I understand. If the Latvian locale has been generated, the
Latvian layouts are not shown under "Other", but a Latvian item should
be shown in one of the previous views.

Can you please let us know the output of this terminal command:

locale -a | grep ^lv

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

Title:
  Ubuntu Cant find keyboard layout languages

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

Bug description:
  Ubuntu Cant find keyboard layout languages
  List is empty when filtering as in image: "latvian"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:13 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874893] [NEW] Shouldn't hardcode gnome-software

2020-04-24 Thread Ken VanDine

Public bug reported:

Currently the app chooser dialog hardcodes gnome-software as the app to
launch to find software.  This should use the system default.  For
example on 20.04 it should launch snap-store.ubuntu-software.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xdg-desktop-portal-gtk 1.6.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 15:01:56 2020
InstallationDate: Installed on 2019-11-04 (171 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: Upgraded to focal on 2020-02-05 (79 days ago)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Medium
 Assignee: James Henstridge (jamesh)
 Status: Triaged

** Affects: xdg-desktop-portal-gtk (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: xdg-desktop-portal-gtk (Ubuntu Focal)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
 Assignee: (unassigned) => James Henstridge (jamesh)

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: New => Triaged

** Also affects: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Shouldn't hardcode gnome-software

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gtk source package in Bionic:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  Currently the app chooser dialog hardcodes gnome-software as the app
  to launch to find software.  This should use the system default.  For
  example on 20.04 it should launch snap-store.ubuntu-software.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-desktop-portal-gtk 1.6.0-1build1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:01:56 2020
  InstallationDate: Installed on 2019-11-04 (171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: Upgraded to focal on 2020-02-05 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1874893/+subscriptions

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

[Desktop-packages] [Bug 1874891] [NEW] gnome-software crashes when clicking updates on Ubuntu 20.04

2020-04-24 Thread Luís Louro

Public bug reported:

I installed Ubuntu 20.04 beta. It all went well, and Ubuntu Software was 
running properly.
Then Ubuntu 20.04 final was out and I saw updates on Ubuntu software. I tried 
the Updates tab and Ubuntu Software is crashing when I click Updates.

I tried running snap-store from command line. I get this when I click
Updates:

18:51:11:0231 Gs  automatically prevented from changing kind on 
system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable
 from runtime to unknown!
18:51:19:0935 Gtk gtk_widget_realize: assertion 'widget->priv->anchored || 
GTK_IS_INVISIBLE (widget)' failed
18:51:19:0935 Gtk gtk_widget_realize: assertion 'widget->priv->anchored || 
GTK_IS_INVISIBLE (widget)' failed
**
Gtk:ERROR:../gtk/gtkwidget.c:12393:gtk_widget_real_map: assertion failed: 
(_gtk_widget_get_realized (widget))
Bail out! Gtk:ERROR:../gtk/gtkwidget.c:12393:gtk_widget_real_map: assertion 
failed: (_gtk_widget_get_realized (widget))
Abortado (núcleo despejado)


lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

gnome-software:
  Instalado: (nenhum)
  Candidato: 3.36.0-0ubuntu3
  Tabela de Versão:
 3.36.0-0ubuntu3 500
500 http://pt.archive.ubuntu.com/ubuntu focal/main amd64 Packages

I expected doing some updates since it shows 7 updates to do.
What happen: gnome-software crashed withou any message.

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

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

Title:
  gnome-software crashes when clicking updates on Ubuntu 20.04

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04 beta. It all went well, and Ubuntu Software was 
running properly.
  Then Ubuntu 20.04 final was out and I saw updates on Ubuntu software. I tried 
the Updates tab and Ubuntu Software is crashing when I click Updates.

  I tried running snap-store from command line. I get this when I click
  Updates:

  18:51:11:0231 Gs  automatically prevented from changing kind on 
system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable
 from runtime to unknown!
  18:51:19:0935 Gtk gtk_widget_realize: assertion 'widget->priv->anchored || 
GTK_IS_INVISIBLE (widget)' failed
  18:51:19:0935 Gtk gtk_widget_realize: assertion 'widget->priv->anchored || 
GTK_IS_INVISIBLE (widget)' failed
  **
  Gtk:ERROR:../gtk/gtkwidget.c:12393:gtk_widget_real_map: assertion failed: 
(_gtk_widget_get_realized (widget))
  Bail out! Gtk:ERROR:../gtk/gtkwidget.c:12393:gtk_widget_real_map: assertion 
failed: (_gtk_widget_get_realized (widget))
  Abortado (núcleo despejado)

  
  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  gnome-software:
Instalado: (nenhum)
Candidato: 3.36.0-0ubuntu3
Tabela de Versão:
   3.36.0-0ubuntu3 500
  500 http://pt.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I expected doing some updates since it shows 7 updates to do.
  What happen: gnome-software crashed withou any message.

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

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

Sorry for all, "Fix Released" information for status isn't true, it's my
mistake.

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1865870] Re: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"

2020-04-24 Thread René Walendy

I have the impression that this bug was caused by a broken plymouth
update. After updating plymouth to the newest version, the issue went
away and I didn't have any problems ever since.

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

Title:
  [nvidia] xorg via gdm-x-session fails to start with "Cannot run in
  framebuffer mode. Please specify busIDs for all framebuffer devices"

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After performing apt dist-upgrade and rebooting, plymouth doesn't run
  in full resolution and the graphical session won't start. The system
  is stuck on a blinking cursor. A full log file is attached. Here is
  the error:

  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"modesetting"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"fbdev"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: 
"fbdevhw"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"vesa"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE)
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error:
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in 
framebuffer mode. Please specify busIDsfor all framebuffer devices

  Interestingly, pressing Ctrl+Alt+F1 when the system is stuck
  successfully starts the XServer and brings up the login screen. While
  I experience some font rendering issues, most things seem to work fine
  after that.

  lsb_release -rd 
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  uname -a
  Linux  5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx
  graphics:

  lshw -c video
*-display 
 Beschreibung: VGA compatible controller
 Produkt: TU106M [GeForce RTX 2060 Mobile]
 Hersteller: NVIDIA Corporation
 Physische ID: 0
 Bus-Informationen: pci@:01:00.0
 Version: a1
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom
 Konfiguration: driver=nvidia latency=0
 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07
*-display
 Beschreibung: VGA compatible controller
 Produkt: UHD Graphics 630 (Mobile)
 Hersteller: Intel Corporation
 Physische ID: 2
 Bus-Informationen: pci@:00:02.0
 Version: 00
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom
 Konfiguration: driver=i915 latency=0
 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff 
ioport:5000(Größe=64) memory:c-d

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

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874886] [NEW] Ubuntu 20.04 I cannot set different default application for .zip and .mcsz files

2020-04-24 Thread Vijay

Public bug reported:

Ubuntu 20.04 I cannot set different default application for .zip and
.mcsz files

I right click a .zip file in Nautilus, go to "Properties" and choose
Archive Manager, but now the OS will try to open all my .mcsz files with
Archive Manager.  I right click a .mcsz file and select MuseScore, now
all .zip files open in MuseScore (error).

I would ideally like to open .zip files with Archive Manager and .mcsz
files with MuseScore by default.  Is this fixable or a bug?

Thank you,
Vijay

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

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

Title:
  Ubuntu 20.04 I cannot set different default application for .zip and
  .mcsz files

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 I cannot set different default application for .zip and
  .mcsz files

  I right click a .zip file in Nautilus, go to "Properties" and choose
  Archive Manager, but now the OS will try to open all my .mcsz files
  with Archive Manager.  I right click a .mcsz file and select
  MuseScore, now all .zip files open in MuseScore (error).

  I would ideally like to open .zip files with Archive Manager and .mcsz
  files with MuseScore by default.  Is this fixable or a bug?

  Thank you,
  Vijay

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

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  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/1874851/+subscriptions

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

[Desktop-packages] [Bug 1874882] [NEW] chromium-browser: intermittent display glitch when more than 1 window open

2020-04-24 Thread indigocat

Public bug reported:

When using Chromium, and there's 2 or more windows open, an intermittent
hardware glitch is triggered, as if the screen was divided into a small
quadrant grid, and these quadrants were horizontally and vertically
skewed & degraded into particles.

The glitch happens in a 1/4-second, at random intervals between events.

OS: Ubuntu 18.04 / elementaryOS 5.1.3
Processor: Intel i5 540M  (ThinkPad laptop)
Video: NVidia NVS 3100M (using proprietary driver 340.108)
Chromium version: 80.0.3987.163 (Build oficial) Built on Ubuntu

It only happens in Chromium or Chrome, since version 70+.
Firefox does not exhibit this behavior.

Logging out from the user session and logging back in and reopening
Chromium/Chrome makes the triggered glitch disappear.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When using Chromium, and there's 2 or more windows open, an intermittent
  hardware glitch is triggered, as if the screen was divided into a small
  quadrant grid, and these quadrants were horizontally and vertically
  skewed & degraded into particles.
  
  The glitch happens in a 1/4-second, at random intervals between events.
  
  OS: Ubuntu 18.04 / elementaryOS 5.1.3
  Processor: Intel i5 540M  (ThinkPad laptop)
  Video: NVidia NVS 3100M (using proprietary driver 340.108)
  Chromium version: 80.0.3987.163 (Build oficial) Built on Ubuntu
  
  It only happens in Chromium or Chrome, since version 70+.
  Firefox does not exhibit this behavior.
+ 
+ Logging out from the user session and logging back in and reopening
+ Chromium/Chrome makes the triggered glitch disappear.

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

Title:
  chromium-browser: intermittent display glitch when more than 1 window
  open

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When using Chromium, and there's 2 or more windows open, an
  intermittent hardware glitch is triggered, as if the screen was
  divided into a small quadrant grid, and these quadrants were
  horizontally and vertically skewed & degraded into particles.

  The glitch happens in a 1/4-second, at random intervals between
  events.

  OS: Ubuntu 18.04 / elementaryOS 5.1.3
  Processor: Intel i5 540M  (ThinkPad laptop)
  Video: NVidia NVS 3100M (using proprietary driver 340.108)
  Chromium version: 80.0.3987.163 (Build oficial) Built on Ubuntu

  It only happens in Chromium or Chrome, since version 70+.
  Firefox does not exhibit this behavior.

  Logging out from the user session and logging back in and reopening
  Chromium/Chrome makes the triggered glitch disappear.

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

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

[Desktop-packages] [Bug 1874415] Re: chromedriver doesn't work with the snap package, without --headless

2020-04-24 Thread Marius Gedminas

Here's my minimal example:

#!/usr/bin/env python3
import time
import sys
from selenium import webdriver

options = webdriver.chrome.options.Options()
if '--headless' in sys.argv:
options.add_argument("headless")
driver = webdriver.Chrome(options=options)
driver.get("https://ubuntu.com";)
time.sleep(1)
print(driver.current_url)
driver.quit()


I can run python3 ex.py --headless, and it works (prints https://ubuntu.com 
after 10 seconds).
I can run it without --headless and I get 

selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome 
failed to start: exited abnormally.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location 
/snap/chromium/current/command-chromium.wrapper is no longer running, so 
ChromeDriver is assuming that Chrome has crashed.)

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

Title:
  chromedriver doesn't work with the snap package, without --headless

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been
  unable to run Robot Framework tests using SeleniumLibrary with Chrome.
  I keep getting errors from chromedriver:

  
  Parent suite setup failed:
  WebDriverException: Message: unknown error: Chrome failed to start: exited 
abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location 
/snap/chromium/current/command-chromium.wrapper is no longer running, so 
ChromeDriver is assuming that Chrome has crashed.)

  
  Things work somewhat better when I ask chromium to run in headless mode, 
although I still get weird failures partway through the test suite (I think on 
the first test that uses Select Window): TimeoutException: Message: timeout: 
Timed out receiving message from renderer: 300.000.

  It would be easier to debug this if I could _see_ what the browser is
  doing, which brings us back to the original problem: non-headless
  chromium doesn't work in 19.10.

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

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

[Desktop-packages] [Bug 1871359] Re: Ubuntu Cant switch languages- shortcut alt+shift doesnt work

2020-04-24 Thread Kangarooo Jānis

Well cant switch keyboard and default in other OS is left sides
alt+shift

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

Title:
  Ubuntu Cant switch languages- shortcut alt+shift doesnt work

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

Bug description:
  Ubuntu Cant switch languages- shortcut alt+shift doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 10:59:16 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1871360] Re: Ubuntu Cant find keyboard layout languages

2020-04-24 Thread Kangarooo Jānis

List is empty when filtering as in image: "latvian"

** Description changed:

  Ubuntu Cant find keyboard layout languages
+ List is empty when filtering as in image: "latvian"
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:13 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ubuntu Cant find keyboard layout languages

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

Bug description:
  Ubuntu Cant find keyboard layout languages
  List is empty when filtering as in image: "latvian"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:13 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874871] [NEW] Wrong screen offset dual monitors

2020-04-24 Thread Lukáš Eret

Public bug reported:

When I change screen position in gnome-settings, or reboot computer screens 
overlap.
I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 19:55:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02]
InstallationDate: Installed on 2020-04-23 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_efifg2@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_efifg2 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.90
dmi.board.name: B450M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Image of overlapping"
   
https://bugs.launchpad.net/bugs/1874871/+attachment/5359708/+files/IMG_20200424_200414.jpg

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

Title:
  Wrong screen offset dual monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  When I change screen position in gnome-settings, or reboot computer screens 
overlap.
  I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:55:09 2020
  DistUpg

[Desktop-packages] [Bug 1874842] Re: Fonts installed using msttfcorefonts package (ttf-mscorefonts-installer) are not detected by some sites

Erasing text "Helvetica," from font family rule on Github using
inspector fixes display of arial font somehow

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

Title:
  Fonts installed using msttfcorefonts package (ttf-mscorefonts-
  installer) are not detected by some sites

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Linux 20.04 LTS upgraded from 18.04 LTS, Firefox 75.0 
(75.0+build3-0ubuntu1, amd64)
  When viewing some sites such as facebook or github the fonts are not being 
displayed correctly. Other system fonts are used instead. The expected result 
would be to have fonts displayed correctly w/o unneded system file modification 
if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Apr 24 18:29:17 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:733
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile4PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profile5Extensions: extensions.sqlite corrupt or missing
  Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile5Locales: extensions.sqlite corrupt or missing
  Profile5PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile5PrefSources: prefs.js
  Profile5Themes: extensions.sqlite corrupt or missing
  Profile6Extensions: extensions.sqlite corrupt or missing
  Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile6Locales: extensions.sqlite corrupt or missing
  Profile6PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile6PrefSources: prefs.js
  Profile6Themes: extensions.sqlite corrupt or missing
  Profile7Extensions: extensions.sqlite corrupt or missing
  Profile7IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile7Locales: extensions.sqlite corrupt or missing
  Profile7PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile7PrefSources: prefs.js
  Profile7Themes: extensions.sqlite corrupt or missing
  Profile8Extensions: extensions.sqlite corrupt or missing
  Profile8IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile8Locales: extensions.sqlite corrupt or missin

[Desktop-packages] [Bug 1874856] Re: Unwanted mouse trail

2020-04-24 Thread Christians

** Attachment removed: "mousetrail.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874856/+attachment/5359627/+files/mousetrail.jpg

** Attachment added: "mousetrail.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874856/+attachment/5359700/+files/mousetrail.jpg

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

Title:
  Unwanted mouse trail

Status in xorg package in Ubuntu:
  New

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers as
  well as nouveau on my GeFOrce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:59:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X580VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Apr 24 16:45:55 2020
  xserver.configfile: default
  xserver.errors:
   NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
   NVIDIA(G0): Failing initialization of X screen
   systemd-logind: failed to release device: Device not taken
   systemd-logind: failed to release device: Device not taken
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1874842] Re: Fonts installed using msttfcorefonts package (ttf-mscorefonts-installer) are not detected by some sites

Github font family: 
font-family: -apple-system,BlinkMacSystemFont,Segoe 
UI,Helvetica,Arial,sans-serif,Apple Color Emoji,Segoe UI Emoji;
Actually used font: sans-serif (incorrect)
Facebook font family:
font-family: Helvetica, Arial, sans-serif;
Actually used font: Arial (correct), though text input fields has a space below

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

Title:
  Fonts installed using msttfcorefonts package (ttf-mscorefonts-
  installer) are not detected by some sites

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Linux 20.04 LTS upgraded from 18.04 LTS, Firefox 75.0 
(75.0+build3-0ubuntu1, amd64)
  When viewing some sites such as facebook or github the fonts are not being 
displayed correctly. Other system fonts are used instead. The expected result 
would be to have fonts displayed correctly w/o unneded system file modification 
if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Apr 24 18:29:17 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:733
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile4PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profile5Extensions: extensions.sqlite corrupt or missing
  Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile5Locales: extensions.sqlite corrupt or missing
  Profile5PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile5PrefSources: prefs.js
  Profile5Themes: extensions.sqlite corrupt or missing
  Profile6Extensions: extensions.sqlite corrupt or missing
  Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile6Locales: extensions.sqlite corrupt or missing
  Profile6PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile6PrefSources: prefs.js
  Profile6Themes: extensions.sqlite corrupt or missing
  Profile7Extensions: extensions.sqlite corrupt or missing
  Profile7IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile7Locales: extensions.sqlite corrupt or missing
  Profile7PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile7PrefSources: prefs.js
  Profile7Themes: extensions.sqlite corrupt or missing
  Profile

[Desktop-packages] [Bug 1874862] [NEW] Touch inputs not detected

2020-04-24 Thread Will Ethridge

Public bug reported:

touch inputs are not detected by Ubuntu on this tablet. I'm not sure the
touch screen hardware is detected at all by Ubuntu. I tried cat
/dev/input/eventX (replacing X with every option listed) and not once
got any reaction to touching the screen.

I can provide more information and troubleshooting if asked, I just need
to know what to look for.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.5.0-050500-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:27:45 2020
DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2020-01-22 (92 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0603:0002 Novatek Microelectronics Corp. 
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
 |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
 |__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
MachineType: MicroElectronics TW102
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic 
root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-01-26 (88 days ago)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.17
dmi.board.asset.tag: Default string
dmi.board.name: H8811C
dmi.board.vendor: EMDOOR
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: EMDOOR
dmi.chassis.version: 1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1:
dmi.product.family: WinBook
dmi.product.name: TW102
dmi.product.sku: 585497
dmi.product.version: 1
dmi.sys.vendor: MicroElectronics
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Touch inputs not detected

Status in xorg package in Ubuntu:
  New

Bug description:
  touch inputs are not detected by Ubuntu on this tablet. I'm not sure
  the touch screen hardware is detected at all by Ubuntu. I tried cat
  /dev/input/eventX (replacing X with every option listed) and not once
  got any reaction to touching the screen.

  I can provide more information and troubleshooting if asked, I just
  need to know what to look for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.5.0-050500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:27:45 2020
  DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [808

[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-24 Thread Dan Streetman

** Tags added: block-proposed-bionic block-proposed-eoan block-proposed-
focal

** Changed in: network-manager (Ubuntu Eoan)
   Status: Won't Fix => In Progress

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems par

[Desktop-packages] [Bug 1859043] Re: thunderbird completely broken after upgrade

2020-04-24 Thread axoin

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

sorry missing text:

after downgrading from 1:68.7.0+build1-0ubuntu0.16.04.2 to
1:60.9.1+build1-0ubuntu0.16.04.1 it works perfectly again, with the
exact same profile folder!

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

Title:
  thunderbird completely broken after upgrade

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When trying to start thunderbird 1.68 with my 1.60 profile, the
  following error appears:

  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: 
TypeError: accountManager is undefined

  The result is a completely unusable thunderbird: the main window
  opens, but there are no messages and it is not possible to open any
  secondary window.

  Downgrading to 1.60 (from disco) solves this issue.

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

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

[Desktop-packages] [Bug 1874842] Re: Fonts installed using msttfcorefonts package (ttf-mscorefonts-installer) are not detected by some sites

Github example (public repository): https://github.com/minetest/minetest/issues
The labels are displaying incorrectly even on a new profile
Facebook main page input labels are showing gap below text larger then above 
text when logging in.

** Attachment added: "Github layout (broken labels)"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874842/+attachment/5359676/+files/Screenshot_2020-04-24%20minetest%20minetest.png

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

Title:
  Fonts installed using msttfcorefonts package (ttf-mscorefonts-
  installer) are not detected by some sites

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Linux 20.04 LTS upgraded from 18.04 LTS, Firefox 75.0 
(75.0+build3-0ubuntu1, amd64)
  When viewing some sites such as facebook or github the fonts are not being 
displayed correctly. Other system fonts are used instead. The expected result 
would be to have fonts displayed correctly w/o unneded system file modification 
if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Apr 24 18:29:17 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:733
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile4PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profile5Extensions: extensions.sqlite corrupt or missing
  Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile5Locales: extensions.sqlite corrupt or missing
  Profile5PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile5PrefSources: prefs.js
  Profile5Themes: extensions.sqlite corrupt or missing
  Profile6Extensions: extensions.sqlite corrupt or missing
  Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile6Locales: extensions.sqlite corrupt or missing
  Profile6PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile6PrefSources: prefs.js
  Profile6Themes: extensions.sqlite corrupt or missing
  Profile7Extensions: extensions.sqlite corrupt or missing
  Profile7IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile7Locales: extensions.sqlite corrupt or missing
  Profile7PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:gr

[Desktop-packages] [Bug 1874842] Re: Fonts installed using msttfcorefonts package (ttf-mscorefonts-installer) are not detected by some sites

** Attachment added: "Facebook layout (broken text inputs)"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874842/+attachment/5359677/+files/Screenshot_2020-04-24%20%E2%80%9EFacebook%E2%80%9C%20%E2%80%93%20prisijunkite%20arba%20u%C5%BEsiregistruokite.png

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

Title:
  Fonts installed using msttfcorefonts package (ttf-mscorefonts-
  installer) are not detected by some sites

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Linux 20.04 LTS upgraded from 18.04 LTS, Firefox 75.0 
(75.0+build3-0ubuntu1, amd64)
  When viewing some sites such as facebook or github the fonts are not being 
displayed correctly. Other system fonts are used instead. The expected result 
would be to have fonts displayed correctly w/o unneded system file modification 
if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Apr 24 18:29:17 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:733
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4Plugins: Shockwave Flash - 
/usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin)
  Profile4PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profile5Extensions: extensions.sqlite corrupt or missing
  Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile5Locales: extensions.sqlite corrupt or missing
  Profile5PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile5PrefSources: prefs.js
  Profile5Themes: extensions.sqlite corrupt or missing
  Profile6Extensions: extensions.sqlite corrupt or missing
  Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile6Locales: extensions.sqlite corrupt or missing
  Profile6PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile6PrefSources: prefs.js
  Profile6Themes: extensions.sqlite corrupt or missing
  Profile7Extensions: extensions.sqlite corrupt or missing
  Profile7IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile7Locales: extensions.sqlite corrupt or missing
  Profile7PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile7PrefSources: prefs.js
  Profile7Themes: extensions.sqlite corrupt or missing
  Profile8Extensions: extensions.sqlite corrupt or missing
  Profil

[Desktop-packages] [Bug 1859043] Re: thunderbird completely broken after upgrade

2020-04-24 Thread axoin

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

I do not think this is a duplicate. My global-messages-db.sqlite is
fine, as all I did on Ubuntu 16.04 was downgrade thunderbird version.

Download from
https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.16.04.1/+build/18178755

and then

sudo dpkg -i thunderbird_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb
thunderbird-gnome-support_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb
thunderbird-locale-de_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb
thunderbird-locale-en_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb
thunderbird-locale-en-us_60.9.1+build1-0ubuntu0.16.04.1_all.deb xul-ext-
lightning_60.9.1+build1-0ubuntu0.16.04.1_amd64.deb


so the reason is something else.

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

Title:
  thunderbird completely broken after upgrade

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When trying to start thunderbird 1.68 with my 1.60 profile, the
  following error appears:

  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: 
TypeError: accountManager is undefined

  The result is a completely unusable thunderbird: the main window
  opens, but there are no messages and it is not possible to open any
  secondary window.

  Downgrading to 1.60 (from disco) solves this issue.

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

2020-04-24 Thread Adrien Jarthon

For the record I recently noticed the 30 leaked processes started taking
all my CPU (all at the same time, maybe when an update was downloaded).
They were all running in infinite loop and I couldn't see the "sleep 60"
in their children any more in htop. I didn't investigate more as I had
to quickly kill them to recover my machine. This is really too
experimental and dangerous.

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

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

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

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

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

2020-04-24 Thread Stefano Coronado

Public bug reported:

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


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

xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


3) What you expected to happen

Being able to switch between "Frequent" and "All" within GNOME App menu

4) What happened instead


The screen froze
The screen not to freeze

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:18:07 2020
DistUpgraded: 2020-04-24 12:33:58,057 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
InstallationDate: Installed on 2019-06-09 (319 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5523994d-c0c4-49a7-8e11-4d2ce9de39d9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.43
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.36
dmi.chassis.asset.tag: CNU2250G4C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029CD1:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: B8Q56UP
dmi.product.version: A1029CD1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

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

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

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen

  Being able to switch between "Frequent" and "All" within GNOME App
  menu

  4) What happened instead

  
  The screen froze
  The screen not to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:18:07 2020
  DistUpgraded: 2020-04-24 12:33:58,057 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No

[Desktop-packages] [Bug 1870450] Re: Firefox takes a moment before being reactive after launch

** Description changed:

+ Description from duplicate bug report:
+ 
+ Hi,
+ 
+ on a freshly installed Ubuntu Budgie 19.10, I've noticed Firefox is kind of 
slow at start :
+ ⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking 
cursor anywhere )
+ ⋅ then cursor eventually appears in address bar but blinking slowly and not 
usable,
+ ⋅ still, clicking anywhere has no effect, or effect delayed much later,
+ ⋅ a moment later, cursor blinks at its usual pace and Firefox becomes 
responsive as expected.
+ The whole process takes 30 seconds to 1 minute and Firefox runs rather ok 
later on with some slow moments though ( sometimes tabs are slow to react, or 
any interactions with buttons in FF menu ).
+ 
+ Same behavior in safe-mode ( without any FF addons )
+ 
+ Same without any Budgie applets regarding app-menu ( such as pixel-saver
+ or global-menu applets ).
+ 
+ see also :
+ ⋅ 
https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-slow-to-start/3265
+ ⋅ https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/813775
+ 
+ =
+ 
+ 
  Hi,
  
  sorry for duplicata, I did not know how to add info on the other same
  bug, see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869597
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 74.0+build3-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  django 6230 F pulseaudio
-  /dev/snd/controlC1:  django 6230 F pulseaudio
-  /dev/snd/pcmC1D0p:   django 6230 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  django 6230 F pulseaudio
+  /dev/snd/controlC1:  django 6230 F pulseaudio
+  /dev/snd/pcmC1D0p:   django 6230 F...m pulseaudio
  BuildID: 20200309095159
  Channel: Unavailable
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr  3 02:04:06 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:732
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-03-22 (11 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  IpRoute:
-  default via 192.168.1.254 dev enp3s0 proto static metric 100 
-  169.254.0.0/16 dev enp3s0 scope link metric 1000 
-  192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.99 metric 100
+  default via 192.168.1.254 dev enp3s0 proto static metric 100
+  169.254.0.0/16 dev enp3s0 scope link metric 1000
+  192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.99 metric 100
  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:732
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
-  Profile1 (Default) - LastVersion=None/None (Out of date)
-  Profile0 - LastVersion=74.0/20200309095159 (In use)
+  Profile1 (Default) - LastVersion=None/None (Out of date)
+  Profile0 - LastVersion=74.0/20200309095159 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

Title:
  Firefox takes a moment before being reactive after launch

Status in firefox package in Ubuntu:
  New

Bug description:
  Description from duplicate bug report:

  Hi,

[Desktop-packages] [Bug 1870424] Re: Can not add server cert

Can you please share detailed steps to reproduce the problem?

Note that starting with 19.10, chromium is a snap package, and it is
strictly confined, which would explain why it cannot read the contents
of certain directories on your system. This will require more
information to be investigated though.

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

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

Title:
  Can not add server cert

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  When I try to add Server Cert to chromium-browser I get the following message
  Could Not read the contents of void
  Error opening directory '/var/lib/snap/void': Permission denied

  This worked on 18.04 but not 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+tCACEcAQS1IhN4Au+Vo1Q1tSYPUFQBAQEBAQEBAQEBAQEBAQEBUtAAoPBwPoAwIDUAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WkFOMDQuMiAKAZoCAw8A4wWAAOYGBQFgYCgAqg==
   modes: 3840x2160
  Date: Thu Apr  2 15:55:40 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   pool/home  zfs1.3T  148G  1.2T  12% /home
   tmpfs  tmpfs   32G   45M   32G   1% /dev/shm
   pool/home  zfs1.3T  148G  1.2T  12% /home
  InstallationDate: Installed on 2020-03-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QNCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic 
root=UUID=6973399c-724d-4607-985d-9426190dc41b ro VGA=1920x1080
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   7Done2020-04-01T21:41:35-04:00  2020-04-01T21:41:52-04:00  
Auto-refresh snap "chromium"
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.162 
(f2c5dd6138153bb0658091205bd1a1717f16081a-refs/branch-heads/3987@{#1034})
  Snap.ChromiumVersion: Chromium 80.0.3987.162 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QNCTO1WW:pvrThinkPadP53:rvnLENOVO:rn20QNCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P53
  dmi.product.name: 20QNCTO1WW
  dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53
  dmi.product.version: ThinkPad P53
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-24 Thread Dan Streetman

** Description changed:

  [Impact]
  
  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill block/unblock.
- Adding a sleep before calling nmcli fixes the issue.
  
  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz
  
  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -
  
  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18
  
  [Test Case]
  
  Assume that test vm and host are ppc64
  
  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
  
  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled
  
  second 'enabled' should be 'disabled' but not updated properly.
  
  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.
  
  [Regression Potential]
  
- No regression potential. The fix touches only the testcase shipped with
- the source package and it doesn't change the binary package. The sleep
- time added is very small, so no possibility of causing testcase timeout.
+ This fixes testcase only, so any regression would cause incorrect test
+ pass/fail, and might cause other missed bugs.
+ 
+ [scope]
+ 
+ this is needed for all releases.  Debian does not include this
+ autopkgtest, and so does not need this fix.
  
  [Other Info]
+ 
+ this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
+ starting up 'systemd-rfkill.service' for any change.  On a 1-cpu system
+ (which all autopkgtest instances for network-manager are), this service
+ startup sometimes blocks the uevent from reaching network-manager before
+ the autopkgtest proceeds to call nmcli to check the rfkill status.  This
+ causes the test case to fail.
+ 
+ There are (at least) 2 options to fix this:
+ 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
+ 2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status
+ 
+ This does not need to be fixed outside the test case, as normal nmcli
+ use should be not done by users in a script immediately after changing
+ rfkill state, nor is there anything that either rfkill or nmcli could
+ even do to address this (technically, nmcli could internally issue a
+ 'udevadm settle' every time it's called, but that seems paranoid and
+ extreme).
+ 
+ [original description]
  
  On ppc64el architecture, it was observed that a fix for systemd is also
  needed (see bug 1734908) for the testcase to be successful.
  
  # original test case
  
  2.1. Download network-manager package source code
  $ apt-get source network-manager
  
  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

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

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in

[Desktop-packages] [Bug 1874837] Re: package chromium-browser (not installed) failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1

2020-04-24 Thread Holger Lindemann

sudo apt install --reinstall chromium-browser

That works, but ended with this warning:

Warnung: /snap/bin wurde nicht in »$PATH« gefunden. Wenn Sie die Sitzung seit 
der Installation von
 snapd nicht neu gestartet haben, versuchen Sie bitte dieses. Für 
weitere Einzelheiten:
 https://forum.snapcraft.io/t/9469.

OK, thank you thus far.

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  »neues chromium-browser-Skript des Paketes pre-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  This happens while installing chromium (snap) with synaptic, together
  with different other applications.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 17:17:36 2020
  ErrorMessage: »neues chromium-browser-Skript des Paketes 
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
»neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab 
den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1859043] Re: thunderbird completely broken after upgrade

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

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

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

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

Title:
  thunderbird completely broken after upgrade

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When trying to start thunderbird 1.68 with my 1.60 profile, the
  following error appears:

  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  TypeError: aAttrDef.objectNounDef is undefined
  -- Exception object --
  *
  -- Stack Trace --
  defineAttribute@resource:///modules/gloda/gloda.js:1922:5
  defineAttributes@resource:///modules/gloda/fundattr.js:71:35
  init@resource:///modules/gloda/fundattr.js:43:12
  @resource:///modules/gloda/everybody.js:13:15
  @resource:///modules/gloda/public.js:8:57
  
nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32
  createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19
  glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: 
TypeError: TagUtils is undefined
  JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: 
aAttrDef.objectNounDef is undefined
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/mailWindowOverlay.js, line 172: 
TypeError: gFolderDisplay is null
  JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 780: 
TypeError: accountManager is undefined

  The result is a completely unusable thunderbird: the main window
  opens, but there are no messages and it is not possible to open any
  secondary window.

  Downgrading to 1.60 (from disco) solves this issue.

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

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

[Desktop-packages] [Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10

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

** Summary changed:

- Can't run Chromium since upgrade to Ubuntu 19.10
+ cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: 
Permission denied

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

Title:
  cannot perform operation: mount --rbind /root
  /tmp/snap.rootfs_vWwNbw//root: Permission denied

Status in chromium-browser package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  New

Bug description:
  Hi,

  I try to run Chromium from the menu and nothing happens.
  If I run it from the CLI I get:
  cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: 
Permission denied

  I tried uninstalling and reinstalling. I tried uninstalling and
  reinstalling snapd. Tried anything related I could find on-line, but
  nothing works.

  Upgrade snap to the latest version on the pre-release channel.

  For some reason Chromium does not show up in the Software centre
  either.

  Thanks for any help.

  $ lsb_release  -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 77.0.3865.120-0ubuntu1.19.10.1
Candidate: 77.0.3865.120-0ubuntu1.19.10.1
Version table:
   *** 77.0.3865.120-0ubuntu1.19.10.1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   77.0.3865.120-0ubuntu1~snap1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan/universe amd64 
Packages

  
  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonicalâ
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: today at 23:00 ACST
  channels:
stable:78.0.3904.108 2019-11-25 (958) 160MB -
candidate: 78.0.3904.108 2019-11-22 (952) 160MB -
beta:  79.0.3945.74  2019-12-06 (966) 155MB -
edge:  80.0.3983.2   2019-12-05 (964) 156MB -
  installed:   78.0.3904.108(958) 160MB

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

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

[Desktop-packages] [Bug 1874856] [NEW] Unwanted mouse trail

2020-04-24 Thread Christians

Public bug reported:

Moving mouse leaves a trail of squares for a few seconds on a fresh
20.04 install. This happens with proprietary nvidia 440 drivers as well
as nouveau on my GeFOrce GTX 1050 mobile.

Could be related to my submission
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/1874819

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 17:59:48 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1a10]
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. X580VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X580VD.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X580VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X580VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri Apr 24 16:45:55 2020
xserver.configfile: default
xserver.errors:
 NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
 NVIDIA(G0): Failing initialization of X screen
 systemd-logind: failed to release device: Device not taken
 systemd-logind: failed to release device: Device not taken
 modeset(0): failed to set mode: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "mousetrail.jpg"
   
https://bugs.launchpad.net/bugs/1874856/+attachment/5359627/+files/mousetrail.jpg

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

Title:
  Unwanted mouse trail

Status in xorg package in Ubuntu:
  New

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers as
  well as nouveau on my GeFOrce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hib

[Desktop-packages] [Bug 1865870] Re: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"

2020-04-24 Thread Dan Kegel

I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install' 
to
get drivers for my gtx 1080.  Reinstalling ubuntu 20.04 final made the problem 
vanish 
(whew).

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

Title:
  [nvidia] xorg via gdm-x-session fails to start with "Cannot run in
  framebuffer mode. Please specify busIDs for all framebuffer devices"

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After performing apt dist-upgrade and rebooting, plymouth doesn't run
  in full resolution and the graphical session won't start. The system
  is stuck on a blinking cursor. A full log file is attached. Here is
  the error:

  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"modesetting"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"fbdev"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: 
"fbdevhw"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted 
because of no matching config section.
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: 
"vesa"
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE)
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error:
  Mär 03 13:04:13  /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in 
framebuffer mode. Please specify busIDsfor all framebuffer devices

  Interestingly, pressing Ctrl+Alt+F1 when the system is stuck
  successfully starts the XServer and brings up the login screen. While
  I experience some font rendering issues, most things seem to work fine
  after that.

  lsb_release -rd 
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  uname -a
  Linux  5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx
  graphics:

  lshw -c video
*-display 
 Beschreibung: VGA compatible controller
 Produkt: TU106M [GeForce RTX 2060 Mobile]
 Hersteller: NVIDIA Corporation
 Physische ID: 0
 Bus-Informationen: pci@:01:00.0
 Version: a1
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom
 Konfiguration: driver=nvidia latency=0
 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff 
memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07
*-display
 Beschreibung: VGA compatible controller
 Produkt: UHD Graphics 630 (Mobile)
 Hersteller: Intel Corporation
 Physische ID: 2
 Bus-Informationen: pci@:00:02.0
 Version: 00
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom
 Konfiguration: driver=i915 latency=0
 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff 
ioport:5000(Größe=64) memory:c-d

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

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

[Desktop-packages] [Bug 1870640] Re: Does not register as x-www-browser alternative

Running:

sudo update-alternatives --install /usr/bin/x-www-browser \
x-www-browser /usr/bin/chromium-browser 40

as was done in the original postinst script for chromium-browser is
enough to fix the problem.

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Does not register as x-www-browser alternative

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This concern chromium 80.0.3987.162 (snap package) in Ubuntu focal.

  After installing the package, update-alternatives(1) cannot set x-www-
  browser to point to /usr/bin/chromium-browser:

  # update-alternatives --set x-www-browser /usr/bin/chromium-browser
  update-alternatives: error: alternative /usr/bin/chromium-browser for 
x-www-browser not registered; not setting

  This worked correctly with the previous non-snap chromium-browser
  package.

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

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

[Desktop-packages] [Bug 1870515] Re: site-specific browser (SSB) does not work in Firefox

This works for me here with firefox 75.0+build3-0ubuntu0.19.10.1. Can
you test again and let us know whether you're still seeing the problem?

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

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

Title:
  site-specific browser (SSB) does not work in Firefox

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The site-specific browser (SSB) feature does not work, e.g. running:

  firefox --ssb chat.google.com

  will just open a new empty Firefox window. "browser.ssb" is set to
  "true" in about:config.

  Affected version: Firefox 74.0+build3-0ubuntu0.19.10.1 on Ubuntu 19.10
  (eoan)

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

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

[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch

This sounds like a connectivity/network driver issue, rather than a
problem with thunderbird.

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

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

Title:
  Thunderbird freezes graphical session except mouse cursor on second
  launch or clicking the icon after email setup on the first launch

Status in network-manager package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Launching thunderbird (pinned on Favourites) from the dock/dash
  it shows 2 orange dots on default theme that is one for email setup
  and the other for the main window. After setting up an email and
  closing the email config window, the two dots are still shown on the
  dash/dock before the icon. Thunderbird causes the graphical session
  except for the mouse cursor to freeze until I switch to a TTY and
  reboot. Also when closing thunderbird, one dot is shown and when
  launching the application the graphical session except for mouse
  cursor freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BuildID: 20200110143530
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 13:26:59 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/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2020-03-31 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.4.1/20200110143530
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874786] Re: [snap] chromium stops working properly if snapd updates chromium in background

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

The notification is a stop-gap measure, it's not a perfect solution but
it strongly suggests to the user that they should restart chromium
themselves. See bug #1616650 for more details about this problem (I'm
marking this bug a duplicate of that one).

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

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

Title:
  [snap] chromium stops working properly if snapd updates chromium in
  background

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ubuntu 20.04

  mike@workstation:~$ apt info chromium-browser
  Package: chromium-browser
  Version: 80.0.3987.163-0ubuntu1
  Priority: optional
  Section: universe/web
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 164 kB
  Provides: www-browser
  Pre-Depends: debconf, snapd
  Depends: debconf (>= 0.5) | debconf-2.0
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: 48,3 kB
  APT-Manual-Installed: yes
  APT-Sources: http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  Description: Transitional package - chromium-browser -> chromium snap
   Dies ist ein Übergangspaket. Es kann gefahrlos entfernt werden.
   .
   chromium-browser is now replaced by the chromium snap.

  Problem:

  1) You start chromium (for me the browser is running for weeks/months).
  2) Suddenly snap updates chromium (without asking before) - you get a message 
in gnome-shell (but you can't reset browser by click)
  3) So no restart
  4) Problems begin:
  4)a) Close-Button, etc. disappears
  4)b) red poins (app icon in dock) disappear
  4)c) clicking app icon in dock does not show your chromium-windows. only 
"open new windows" is possible. but there are instances running...

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

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

[Desktop-packages] [Bug 1874727] Re: [snap] fullscreen uses only 1/4 of screen on 2. monitor

Could you please run the following command in a terminal to attach
additional debug information to this bug?

apport-collect 1874727

Also, would you mind taking a screenshot/picture that demonstrates the
problem? Thanks!

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

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

Title:
  [snap] fullscreen uses only 1/4 of screen on 2. monitor

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  ->
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy chromium
  ->
  chromium:
Installiert:   (keine)
Installationskandidat: (keine)
Versionstabelle:

  hardware:
  2x monitors: 4K
  scaling: 200%

  Is:
  In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd 
monitor.

  Should be:
  In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor.

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

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

[Desktop-packages] [Bug 1874808] Re: Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1

I can confirm the issue using the steps in the description.

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

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

Title:
  Unmuting Twitch video pauses playback, when media.autoplay.enabled
  .user-gestures-needed=false, media.autoplay.default=1

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  With `media.autoplay.enabled.user-gestures-needed` set to false and
  `media.autoplay.default` set to 1 (block audio), which is the default
  (and other autoplay-related settings in their defaults as well), a
  Twitch video can only be either paused or playing muted; unmuting the
  video pauses it and vice versa.

  == Steps to reproduce ==
  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.enabled.user-gestures-needed to false
  4. Set media.autoplay.default to 1
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video

  == What happens ==
  The video is unmuted, but also paused

  == What I expect to happen ==
  For the video to continue playing, unmuted

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running