date:20200529

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [nouveau] changing screen position, dash is gone, background is
  black.. and flashing white on any attempt to operate anything

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

Bug description:
  Ubuntu 20.04 LTS daily QA-test (live) on hp dc7700 (c2d-e6320, 5gb,
  nvidia quadro nvs 290)

  Background:

  Another exploration of http://launchpad.net/bugs/1869571, primarily as
  I want screen dump to file bug upstream as requested; this box shares
  screens of hp 8200 that had it before, so I'd expect can easily re-
  create it..  I hadn't re-create that issue on this box though..  This
  box has menu on display I prefer, so maybe has cables reversed to hp
  8200 used earlier in 1869571, mentioned in case related - but
  different issue

  What I did:

  Opened `displays` to adjust to match setup (vertical alignment of screens); 
and on hitting "apply" the system has gone strange
   - black background (both displays)
   - lots of (white) flashing on mouse movements if near panel/dash
   - dash is gone, like it has background color but icons gone, now only ~half 
height of monitor (it was screen height before apply with icons)

  Menu items could no longer be operated as not viewable (let alone
  white flashes being very annoying)

  I pressed printscreen to get screencapture once `ubuntu-bug` was
  started; and the dash was re-drawn!!? (it was not there after screen
  position was changed & until printscreen was hit)...

  Printscreen also stopped all white-flashes, and the system is now
  operational again?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 05:21:52 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869650] Re: [nouveau] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [nouveau] changing screen position, dash is gone, background is
  black.. and flashing white on any attempt to operate anything

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

Bug description:
  Ubuntu 20.04 LTS daily QA-test (live) on hp dc7700 (c2d-e6320, 5gb,
  nvidia quadro nvs 290)

  Background:

  Another exploration of http://launchpad.net/bugs/1869571, primarily as
  I want screen dump to file bug upstream as requested; this box shares
  screens of hp 8200 that had it before, so I'd expect can easily re-
  create it..  I hadn't re-create that issue on this box though..  This
  box has menu on display I prefer, so maybe has cables reversed to hp
  8200 used earlier in 1869571, mentioned in case related - but
  different issue

  What I did:

  Opened `displays` to adjust to match setup (vertical alignment of screens); 
and on hitting "apply" the system has gone strange
   - black background (both displays)
   - lots of (white) flashing on mouse movements if near panel/dash
   - dash is gone, like it has background color but icons gone, now only ~half 
height of monitor (it was screen height before apply with icons)

  Menu items could no longer be operated as not viewable (let alone
  white flashes being very annoying)

  I pressed printscreen to get screencapture once `ubuntu-bug` was
  started; and the dash was re-drawn!!? (it was not there after screen
  position was changed & until printscreen was hit)...

  Printscreen also stopped all white-flashes, and the system is now
  operational again?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 05:21:52 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1881380] [NEW] fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader

2020-05-29 Thread Jesús Diéguez Fernández

Public bug reported:

The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was
working fine with ubuntu 16.04 and 18.04.

lsusb shows:

0483:2016 STMicroelectronics Fingerprint Reader

user@xubuntu:~$ fprintd-enroll 
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: transfer timed out

user@xubuntu:~$ fprintd-list user
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User user has no fingers enrolled for UPEK TouchStrip.


This bug is probably the same as:

https://bugzilla.redhat.com/show_bug.cgi?id=1832229

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

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

Title:
  fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB
  UPEK reader

Status in fprintd package in Ubuntu:
  New

Bug description:
  The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It
  was working fine with ubuntu 16.04 and 18.04.

  lsusb shows:

  0483:2016 STMicroelectronics Fingerprint Reader

  user@xubuntu:~$ fprintd-enroll 
  Using device /net/reactivated/Fprint/Device/0
  failed to claim device: Open failed with error: transfer timed out

  user@xubuntu:~$ fprintd-list user
  found 1 devices
  Device at /net/reactivated/Fprint/Device/0
  Using device /net/reactivated/Fprint/Device/0
  User user has no fingers enrolled for UPEK TouchStrip.

  
  This bug is probably the same as:

  https://bugzilla.redhat.com/show_bug.cgi?id=1832229

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

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

[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2020-05-29 Thread Kai Kasurinen

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1880258

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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

[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)

2020-05-29 Thread Joe Coutcher

I just spent a few hours trying to figure out why my Alcatel modem
wasn't establishing a connection...and ran across this bug.  Thank you
Hanno for the workaround!

I uninstalled the usb_modeswitch package and installed the one from
Debian Bullseye, and my modem shows up now!  After adding entries to my
netplan configuration to enable DHCP, I can access the interfaces.

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

Title:
  usb_modeswitch does not switch modems (remain visible as mass storage)

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

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

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

[Desktop-packages] [Bug 1881371] Re: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.

2020-05-29 Thread Kai Kasurinen

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

** This bug has been marked a duplicate of bug 1881370
   Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files 
from archive manager and attempted to drag to nautilus.

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

Title:
   Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed
  files from archive manager and attempted to drag to nautilus.

Status in nautilus package in Ubuntu:
  New

Bug description:
  When I attempted to drag the contents of the gcc subfolder in the
  gcc-10.1.0 source from a .xz file in archive manager and drop the
  results in the gcc subfolder of the extracted archive in nautilus, the
  cursor became stuck in the "drag and drop" mode without initiating the
  drag and drop. In this state, I was unable to click anything, and the
  enter button would be ignored, preventing me from entering any
  commands, forcing me to do a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 21:59:38 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-05-07 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881372] Re: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.

2020-05-29 Thread Kai Kasurinen

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

** This bug has been marked a duplicate of bug 1881370
   Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files 
from archive manager and attempted to drag to nautilus.

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

Title:
  Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed
  files from archive manager and attempted to drag to nautilus.

Status in file-roller package in Ubuntu:
  New

Bug description:
  When I attempted to drag the contents of the gcc subfolder in the
  gcc-10.1.0 source from a .xz file in archive manager and drop the
  results in the gcc subfolder of the extracted archive in nautilus, the
  cursor became stuck in the "drag and drop" mode without initiating the
  drag and drop. In this state, I was unable to click anything, and the
  enter button would be ignored, preventing me from entering any
  commands, forcing me to do a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 22:01:26 2020
  InstallationDate: Installed on 2020-05-07 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1881372/+subscriptions

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

[Desktop-packages] [Bug 1881372] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.

2020-05-29 Thread Seija Kijin

Public bug reported:

When I attempted to drag the contents of the gcc subfolder in the
gcc-10.1.0 source from a .xz file in archive manager and drop the
results in the gcc subfolder of the extracted archive in nautilus, the
cursor became stuck in the "drag and drop" mode without initiating the
drag and drop. In this state, I was unable to click anything, and the
enter button would be ignored, preventing me from entering any commands,
forcing me to do a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: file-roller 3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 29 22:01:26 2020
InstallationDate: Installed on 2020-05-07 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed
  files from archive manager and attempted to drag to nautilus.

Status in file-roller package in Ubuntu:
  New

Bug description:
  When I attempted to drag the contents of the gcc subfolder in the
  gcc-10.1.0 source from a .xz file in archive manager and drop the
  results in the gcc subfolder of the extracted archive in nautilus, the
  cursor became stuck in the "drag and drop" mode without initiating the
  drag and drop. In this state, I was unable to click anything, and the
  enter button would be ignored, preventing me from entering any
  commands, forcing me to do a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 22:01:26 2020
  InstallationDate: Installed on 2020-05-07 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1881372/+subscriptions

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

[Desktop-packages] [Bug 1881371] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.

2020-05-29 Thread Seija Kijin

Public bug reported:

When I attempted to drag the contents of the gcc subfolder in the
gcc-10.1.0 source from a .xz file in archive manager and drop the
results in the gcc subfolder of the extracted archive in nautilus, the
cursor became stuck in the "drag and drop" mode without initiating the
drag and drop. In this state, I was unable to click anything, and the
enter button would be ignored, preventing me from entering any commands,
forcing me to do a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 29 21:59:38 2020
GsettingsChanges:
 
InstallationDate: Installed on 2020-05-07 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

Title:
   Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed
  files from archive manager and attempted to drag to nautilus.

Status in nautilus package in Ubuntu:
  New

Bug description:
  When I attempted to drag the contents of the gcc subfolder in the
  gcc-10.1.0 source from a .xz file in archive manager and drop the
  results in the gcc subfolder of the extracted archive in nautilus, the
  cursor became stuck in the "drag and drop" mode without initiating the
  drag and drop. In this state, I was unable to click anything, and the
  enter button would be ignored, preventing me from entering any
  commands, forcing me to do a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 21:59:38 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-05-07 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881370] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.

2020-05-29 Thread Seija Kijin

Public bug reported:

When I attempted to drag the contents of the gcc subfolder in the
gcc-10.1.0 source from a .xz file in archive manager and drop the
results in the gcc subfolder of the extracted archive in nautilus, the
cursor became stuck in the "drag and drop" mode without initiating the
drag and drop. In this state, I was unable to click anything, and the
enter button would be ignored, preventing me from entering any commands,
forcing me to do a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 29 21:53:18 2020
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2020-05-07 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-05-25 19-01-22.png"
   
https://bugs.launchpad.net/bugs/1881370/+attachment/5378620/+files/Screenshot%20from%202020-05-25%2019-01-22.png

** Attachment removed: "Screenshot from 2020-05-25 19-01-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881370/+attachment/5378620/+files/Screenshot%20from%202020-05-25%2019-01-22.png

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

Title:
  Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed
  files from archive manager and attempted to drag to nautilus.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I attempted to drag the contents of the gcc subfolder in the
  gcc-10.1.0 source from a .xz file in archive manager and drop the
  results in the gcc subfolder of the extracted archive in nautilus, the
  cursor became stuck in the "drag and drop" mode without initiating the
  drag and drop. In this state, I was unable to click anything, and the
  enter button would be ignored, preventing me from entering any
  commands, forcing me to do a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 21:53:18 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-05-07 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode

2020-05-29 Thread mirek koc

For me removing iio sensor not helping ... 
My mouse cursor is still flipped like or your video.

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

Title:
  [HP Spectre x360 Convertible 13] click position is flipped to cursor
  position when in tent mode

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

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug

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

2020-05-29 Thread Juan C.

Same issue with GeForce 920M with nvidia drivers (ASUS TP-300LJ).

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1881364] Re: broken kerning

2020-05-29 Thread Hadmut Danisch

Example file:

Slide 1: Vertical negative distance
Slide 2: Horizontal negativ kerning


** Attachment added: "test4.odp"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881364/+attachment/5378597/+files/test4.odp

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

Title:
  broken kerning

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I am just trying to debug a problem with impress I have after
  upgrading from 18.04 to 20.04:

  On some, not on all slides, text becomes

  - unreadable due to negative kerning, i.e. characters are shifted so
  close together that they are overlapping

  - one slide even invisible.


  Strangely, the effect occurs 
  - with libreoffice as a debian package
  - with libreoffice as an AppImage downloaded from libreoffice.org
  - *but not* with libreoffice as a snap (which doesn't solve the problem 
because of other problems of accessing local fonts)


  Unfortunately, I can't give the slides as an example, they're strictly
  confidential. But I'm trying to build an example.

  
  Just to bring people together who experience the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sat May 30 01:43:40 2020
  InstallationDate: Installed on 2020-05-27 (2 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1881364] [NEW] broken kerning

2020-05-29 Thread Hadmut Danisch

Public bug reported:

Hi,

I am just trying to debug a problem with impress I have after upgrading
from 18.04 to 20.04:

On some, not on all slides, text becomes

- unreadable due to negative kerning, i.e. characters are shifted so
close together that they are overlapping

- one slide even invisible.


Strangely, the effect occurs 
- with libreoffice as a debian package
- with libreoffice as an AppImage downloaded from libreoffice.org
- *but not* with libreoffice as a snap (which doesn't solve the problem because 
of other problems of accessing local fonts)


Unfortunately, I can't give the slides as an example, they're strictly
confidential. But I'm trying to build an example.


Just to bring people together who experience the same problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Sat May 30 01:43:40 2020
InstallationDate: Installed on 2020-05-27 (2 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  broken kerning

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I am just trying to debug a problem with impress I have after
  upgrading from 18.04 to 20.04:

  On some, not on all slides, text becomes

  - unreadable due to negative kerning, i.e. characters are shifted so
  close together that they are overlapping

  - one slide even invisible.


  Strangely, the effect occurs 
  - with libreoffice as a debian package
  - with libreoffice as an AppImage downloaded from libreoffice.org
  - *but not* with libreoffice as a snap (which doesn't solve the problem 
because of other problems of accessing local fonts)


  Unfortunately, I can't give the slides as an example, they're strictly
  confidential. But I'm trying to build an example.

  
  Just to bring people together who experience the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sat May 30 01:43:40 2020
  InstallationDate: Installed on 2020-05-27 (2 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2020-05-29 Thread Samuel Alves Gonçalves

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

New Install from netboot method ubuntu 20.04 focal same error, I did
everything, but nothing worked

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Desktop-packages] [Bug 1880710] Re: [snap] Tab goes blank even after reloads (and no refresh is happening)

2020-05-29 Thread Natalia Bidart

Hey Oliver, thanks for your attention to this bug.

The issue happened again, I tried to open a google doc, new url and new
tab, and it does not render. Again, I checked for refreshes and all I
have is:

nessita@dali:~$ date
Fri 29 May 2020 06:42:07 PM -03

nessita@dali:~$ snap changes
ID   Status  Spawn   Ready   Summary
128  Donetoday at 01:30 -03  today at 01:31 -03  Auto-refresh snap "lxd"

nessita@dali:~$

I have only 2 extensions installed: pagerduty and thegreatsuspender. The
latter was updated this morning without showing any issue after update.
I opened many new tabs since the update (that was about 5 hours ago).

I tried another new tab, and as before I do get the browser title set
and there are a few google redirects that happens, but the final
doc/page is never shown, I only get a blank page.

Can I provide any extra information to keep debugging this issue?

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => 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/1880710

Title:
  [snap] Tab goes blank even after reloads (and no refresh is happening)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Using chromium from stable:

  installed:  83.0.4103.61(1165) 163MB

  after a few hours of having it opened, some tabs started showing a
  blank page (google spreadsheets, google calendar). Even after hitting
  F5 or hard reloads, the browser will show the content is being re-
  fetched, but nothing is rendered.

  This is happening while chromium is NOT being refreshed:

  nessita@dali:~$ snap changes
  ID   Status  Spawn   Ready   Summary
  125  Doneyesterday at 12:09 -03  yesterday at 12:09 -03  Auto-refresh 
snap "lxd"

  nessita@dali:~$

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

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

[Desktop-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04

2020-05-29 Thread Brian Murray

** Package changed: ubuntu => xorg (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/1881342

Title:
  Display settings are completely broken in 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  This is after doing a fresh Ubuntu 20.04 installation, on my machine
  equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors
  are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait
  mode. This used to work properly in Ubuntu 19.10, but is utterly
  broken in 20.04. Portrait mode doesn't work anymore, and scaling
  doesn't work anymore.

  It'd be much easier to show what's going on with a video, so here
  goes: https://youtu.be/OHxKWfSxhsE

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

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

[Desktop-packages] [Bug 1881342] [NEW] Display settings are completely broken in 20.04

You have been subscribed to a public bug:

This is after doing a fresh Ubuntu 20.04 installation, on my machine
equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors
are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait
mode. This used to work properly in Ubuntu 19.10, but is utterly broken
in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work
anymore.

It'd be much easier to show what's going on with a video, so here goes:
https://youtu.be/OHxKWfSxhsE

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


** Tags: bot-comment
-- 
Display settings are completely broken in 20.04
https://bugs.launchpad.net/bugs/1881342
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1881294] Re: Apparmor blocks evince GUI-Input-Dialogs

2020-05-29 Thread Seth Arnold

Hello Reinhard, please see the
/etc/apparmor.d/tunables/home.d/site.local file, it describes how to add
additional paths to the @{HOMEDIRS} variable, which should allow evince,
and all other profiles that use @{HOME}, to function in your
environment.

Thanks

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

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

Title:
  Apparmor blocks evince GUI-Input-Dialogs

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Network Users (LDAP + NFS4 home) cannot interact with evince GUI-
  input-elements.

  * page navigation per number not possible
  * select pages to print not possible
  * save open PDF with different name not possible

  Local user on the same machine behaves as expected.

  
  apparmor messages  in /var/log/syslog 

  May 29 14:37:07 r002pc51 kernel: [15848.736916] audit: type=1400
  audit(1590755827.768:827): apparmor="DENIED" operation="file_lock"
  profile="/usr/bin/evince" name="/home/teachers/ttfinr/.cache/event-
  sound-cache.tdb.2176809057334199ab75052753e0683a.x86_64-pc-linux-gnu"
  pid=34988 comm="evince" requested_mask="k" denied_mask="k" fsuid=4515
  ouid=4515

  May 29 14:37:07 r002pc51 kernel: [15848.739259] audit: type=1400
  audit(1590755827.772:828): apparmor="DENIED" operation="link"
  profile="/usr/bin/evince" name="/home/teachers/ttfinr/.local/share
  /gvfs-metadata/.open04eaJ8" pid=34988 comm="pool-evince"
  requested_mask="l" denied_mask="l" fsuid=4515 ouid=4515
  target="/home/teachers/ttfinr/.local/share/gvfs-metadata/home"

  May 29 14:37:07 r002pc51 kernel: [15848.739974] audit: type=1400
  audit(1590755827.772:829): apparmor="DENIED" operation="open"
  profile="/usr/bin/evince" name="/run/user/4515/gvfs-
  metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="r"
  denied_mask="r" fsuid=4515 ouid=4515

  May 29 14:37:07 r002pc51 kernel: [15848.740088] audit: type=1400
  audit(1590755827.772:830): apparmor="DENIED" operation="unlink"
  profile="/usr/bin/evince" name="/run/user/4515/gvfs-
  metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="d"
  denied_mask="d" fsuid=4515 ouid=4515

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

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

[Desktop-packages] [Bug 1874247] Re: Don't work wired connection regression focal

2020-05-29 Thread Igor Zubarev

Currently works ok. It seems it was Beta bug.

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  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.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/1874247/+subscriptions

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

[Desktop-packages] [Bug 1881199] Re: [SoundCore mini, playback] No sound at all from Rhythmbox

2020-05-29 Thread Albert Cardona

Thank you very much, your suggestion solved the issue: rhythmbox can now
play via bluetooth.

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

Title:
  [SoundCore mini, playback] No sound at all from Rhythmbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After connecting via bluetooth the Soundcore Mini, I can get sound to
  play through it just fine from e.g. the Chromium browser, but not from
  Rhythmbox, which instead always plays from the laptop's internal
  speakrs.

  In the bluetooth settings, Soundcore Mini is connected. In the sound
  settings, Soundcore Mini is selected, and the "Test" button opens an
  UI that lets me play test sounds, and it works. And indeed it works
  for e.g. Google Chrome for a youtube video. But Rhythmbox plays
  through the internal speakers no matter what. I've tried restarting
  Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings
  and then running "pulseaudio -k", and then restarting Rhythmbox, to no
  avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 22:00:38 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-24 (1434 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SoundCore mini
  Symptom_DevicesInUse:
   Cannot stat file /proc/43906/fd/6: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [SoundCore mini, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1870450] Re: Firefox takes a moment before being reactive after launch

2020-05-29 Thread Coeur Noir

On Ubuntu Budgie 19.10, the problem disappears when I do not use global-
menu-applet.

On Ubuntu Budgie 20.04, no problem at all, even while using global-menu-
applet.

So probably something changed in Firefox Ubuntu package regarding menu (
? ).

-- 
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,

  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
  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
  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)
  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

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

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

[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

2020-05-29 Thread Vinícius Borriello

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

Same problem here. A2DP works fine, but HSP/HFP is marked as
unavailable.

$ uname -r
4.19.66-gentoo

$ pulseaudio --version
pulseaudio 13.0

Device 5C:FB:7C:E2:7A:5B (public)
Name: JBL TUNE500BT
Alias: JBL TUNE500BT
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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

[Desktop-packages] [Bug 1881344] [NEW] JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2

2020-05-29 Thread Jerry Quinn

Public bug reported:

May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: 
Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 786]: 
Too many arguments to method Clutter.Actor.add_child: expected 1, got 2

It seems the pomodoro extension package is either out of date or too new
for the version of gnome-shell in Ubuntu 18.04.

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

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

Title:
  JS WARNING: [/usr/share/gnome-
  shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many
  arguments to method Clutter.Actor.add_child: expected 1, got 2

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

Bug description:
  May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: 
Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
  May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 786]: 
Too many arguments to method Clutter.Actor.add_child: expected 1, got 2

  It seems the pomodoro extension package is either out of date or too
  new for the version of gnome-shell in Ubuntu 18.04.

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

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

[Desktop-packages] [Bug 1855968] Re: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1090]: unreachable code after return statement

2020-05-29 Thread Jerry Quinn

For Ubuntu 18.04, it's at line 1028, but is the same issue.

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

Title:
  JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-
  d...@ubuntu.com/appIcons.js 1090]: unreachable code after return
  statement

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

Bug description:
  JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-
  d...@ubuntu.com/appIcons.js 1090]: unreachable code after return
  statement

  which is true:

  popupMenu() {
  return false;

  this._removeMenuTimeout();
  this.actor.fake_release();
  ...

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

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

[Desktop-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again

2020-05-29 Thread FelipeAF

bluetoothctl connect is the same that connecting in ubuntu settings?

I tried to connect via terminal, and I had same problem:

*TURN PHONE ON*
bluetoothctl connect 1C:52:16:B6:64:01
Attempting to connect to 1C:52:16:B6:64:01
Failed to connect: org.bluez.Error.Failed

Trying a lot of times, after more than 10 times, it works:

 bluetoothctl connect 1C:52:16:B6:64:01
Attempting to connect to 1C:52:16:B6:64:01
^[[A
[CHG] Device 7C:A6:B4:62:CF:86 RSSI: -90
[CHG] Device 64:32:A8:7D:D7:45 RSSI: -70
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -72
[CHG] Device 1C:52:16:B6:64:01 RSSI: -51
[CHG] Device 7C:A6:B4:62:CF:86 RSSI: -90
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -57
[CHG] Device 1C:52:16:B6:64:01 Connected: yes
[CHG] Device E4:7D:BD:56:A8:FD RSSI: -93
[NEW] Device 29:87:FF:B9:CE:42 29-87-FF-B9-CE-42
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -68
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -56
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -71
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -64
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -72
[CHG] Device D0:03:DF:52:8A:44 RSSI: -85
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Key: 0x0075
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Value:
  42 04 01 01 7e d0 03 df 52 8a 44 d2 03 df 52 8a  B...~...R.D...R.
  43 01 16 ad 09 00 00 00  C...
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Key: 0x001d
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Value:
  00 01 4c ..L

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

Title:
  [Redmi AirDots Bluetooth] I need to remove device in settings every
  time i want to connect again

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can connect to my bluetooth phone only the first time after pair the 
device. It works until disconnecting, (whether by turning off the phone, or 
putting into the case, or disconnecting in ubuntu settings), and then i turn on 
the phone again (or remove from the case), i cannot connect until I manually 
remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. 
  If the Ubuntu/Gnome Settings is opened, i can see the status "connected" 
blinks, and fastly change to "disconnected".

  My bluetooth phone works fine with another devices.
  Ubuntu 20.04 LTS
  Laptop Acer Aspire Nitro 5 (AN515-52-5771).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  felipe 2149 F pulseaudio
   /dev/snd/controlC0:  felipe 2149 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 19:10:35 2020
  InstallationDate: Installed on 2020-04-29 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Redmi AirDots_R
  Symptom_Type: None of the above
  Title: [Redmi AirDots_R, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1852172] Re: Battery history and statistics graphs markings are unreadable on a dark theme

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

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

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

Title:
  Battery history and statistics graphs markings are unreadable on a
  dark theme

Status in gnome-power-manager package in Ubuntu:
  Confirmed

Bug description:
  1 - Use a dark theme using Gnome Tweaks.
  2 - Open Power Statistics
  3 - Click on Laptop battery -> History or Statistics tab.

  The markings on the X and Y axes are not readable since the text
  colour does not adapt to the dark theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-power-manager 3.32.0-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 12:25:29 2019
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2019-10-19 (23 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1881330] [NEW] gnome-terminal fails to start

2020-05-29 Thread Jerry Quinn

Public bug reported:

My system has something strange going on.  I'm unable to start gnome-
terminal.  In journalctl, I see the following cryptic message:

May 29 13:08:38 cerberus org.gnome.Shell.desktop[3960]: # Error
constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:
Could not connect: Connection refused

If I then try to start it from an existing terminal, I get:

jlquinn@cerberus:~/work/lt-language-pairs$ gnome-terminal
# Error constructing proxy for :1.89:/org/gnome/Terminal/Factory0: Could not 
connect: Connection refused
# Failed to use specified server: Could not connect: Connection refused
# Falling back to default server.
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Could not connect: Connection refused

This is a somewhat important issue because it will force me to reboot my
machine (or at least GUI) due to the inability to create new terminals.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18
Uname: Linux 4.15.0-102-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 13:03:43 2020
InstallationDate: Installed on 2016-05-30 (1459 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to bionic on 2018-09-17 (620 days ago)

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


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

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

Title:
  gnome-terminal fails to start

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  My system has something strange going on.  I'm unable to start gnome-
  terminal.  In journalctl, I see the following cryptic message:

  May 29 13:08:38 cerberus org.gnome.Shell.desktop[3960]: # Error
  constructing proxy for
  org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect:
  Connection refused

  If I then try to start it from an existing terminal, I get:

  jlquinn@cerberus:~/work/lt-language-pairs$ gnome-terminal
  # Error constructing proxy for :1.89:/org/gnome/Terminal/Factory0: Could not 
connect: Connection refused
  # Failed to use specified server: Could not connect: Connection refused
  # Falling back to default server.
  # Error constructing proxy for 
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect: Connection 
refused

  This is a somewhat important issue because it will force me to reboot
  my machine (or at least GUI) due to the inability to create new
  terminals.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18
  Uname: Linux 4.15.0-102-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 13:03:43 2020
  InstallationDate: Installed on 2016-05-30 (1459 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to bionic on 2018-09-17 (620 days ago)

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

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

[Desktop-packages] [Bug 1881154] Re: xorg crashes with segmentation fault on login; resolved by uninstalling libnvidia-common-440

2020-05-29 Thread Brian Murray

** Package changed: ubuntu => xorg (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/1881154

Title:
  xorg crashes with segmentation fault on login; resolved by
  uninstalling libnvidia-common-440

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg.log.0 output:

  
  [   410.800] (--) Log file renamed from "/var/log/Xorg.pid-3446.log" to 
"/var/log/Xorg.0.log"
  [   410.801] 
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [   410.801] X Protocol Version 11, Revision 0
  [   410.801] Build Operating System: Linux 4.4.0-168-generic x86_64 Ubuntu
  [   410.801] Current Operating System: Linux tarmstrong-Precision-7540 
4.15.0-1081-oem #91-Ubuntu SMP Fri May 1 02:03:58 UTC 2020 x86_64
  [   410.801] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=3a3585a1-8378-42d5-a146-bce23c579d8b ro mem_sleep_default=deep 
amdgpu.runpm=0 quiet splash vt.handoff=1
  [   410.801] Build Date: 14 November 2019  06:20:00PM
  [   410.801] xorg-server 2:1.19.6-1ubuntu4.4 (For technical support please 
see http://www.ubuntu.com/support) 
  [   410.801] Current version of pixman: 0.34.0
  [   410.801]  Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  [   410.801] Markers: (--) probed, (**) from config file, (==) default 
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [   410.801] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 28 09:12:58 
2020
  [   410.801] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [   410.801] (==) No Layout section.  Using the first Screen section.
  [   410.801] (==) No screen section available. Using defaults.
  [   410.801] (**) |-->Screen "Default Screen Section" (0)
  [   410.801] (**) |   |-->Monitor ""
  [   410.801] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
  [   410.801] (==) Automatically adding devices
  [   410.801] (==) Automatically enabling devices
  [   410.801] (==) Automatically adding GPU devices
  [   410.801] (==) Automatically binding GPU devices
  [   410.801] (==) Max clients allowed: 256, resource mask: 0x1f
  [   410.801] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
  [   410.801] (==) ModulePath set to "/usr/lib/xorg/modules"
  [   410.801] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
  [   410.801] (II) Loader magic: 0x555c85989020
  [   410.801] (II) Module ABI versions:
  [   410.801]  X.Org ANSI C Emulation: 0.4
  [   410.801]  X.Org Video Driver: 23.0
  [   410.801]  X.Org XInput driver : 24.1
  [   410.801]  X.Org Server Extension : 10.0
  [   410.802] (++) using VT number 2

  [   410.803] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_312
  [   410.804] (II) xfree86: Adding drm device (/dev/dri/card0)
  [   410.804] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 
paused 0
  [   410.804] (II) xfree86: Adding drm device (/dev/dri/card1)
  [   410.805] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 
paused 0
  [   410.806] (**) OutputClass "nvidia" ModulePath extended to 
"/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
  [   410.806] (**) OutputClass "Nvidia Prime" ModulePath extended to 
"/x86_64-linux-gnu/nvidia/xorg,/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
  [   410.806] (**) OutputClass "Nvidia Prime" setting /dev/dri/card0 as 
PrimaryGPU
  [   410.807] (--) PCI: (0:0:2:0) 8086:3e9b:1028:0926 rev 0, Mem @ 
0xb300/16777216, 0x6000/268435456, I/O @ 0x4000/64, BIOS @ 
0x/131072
  [   410.807] (--) PCI:*(0:1:0:0) 10de:1fb9:1028:0926 rev 161, Mem @ 
0xb400/16777216, 0x7000/268435456, 0x8000/33554432, I/O @ 
0x3000/128, BIOS @ 0x/524288
  [   410.807] (II) LoadModule: "glx"
  [   410.807] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [   410.808] (II) Module glx: vendor="X.Org Foundation"
  [   410.808]  compiled for 1.19.6,

[Desktop-packages] [Bug 1881154] [NEW] xorg crashes with segmentation fault on login; resolved by uninstalling libnvidia-common-440

You have been subscribed to a public bug:

Xorg.log.0 output:


[   410.800] (--) Log file renamed from "/var/log/Xorg.pid-3446.log" to 
"/var/log/Xorg.0.log"
[   410.801] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   410.801] X Protocol Version 11, Revision 0
[   410.801] Build Operating System: Linux 4.4.0-168-generic x86_64 Ubuntu
[   410.801] Current Operating System: Linux tarmstrong-Precision-7540 
4.15.0-1081-oem #91-Ubuntu SMP Fri May 1 02:03:58 UTC 2020 x86_64
[   410.801] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=3a3585a1-8378-42d5-a146-bce23c579d8b ro mem_sleep_default=deep 
amdgpu.runpm=0 quiet splash vt.handoff=1
[   410.801] Build Date: 14 November 2019  06:20:00PM
[   410.801] xorg-server 2:1.19.6-1ubuntu4.4 (For technical support please see 
http://www.ubuntu.com/support) 
[   410.801] Current version of pixman: 0.34.0
[   410.801]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   410.801] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   410.801] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 28 09:12:58 
2020
[   410.801] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   410.801] (==) No Layout section.  Using the first Screen section.
[   410.801] (==) No screen section available. Using defaults.
[   410.801] (**) |-->Screen "Default Screen Section" (0)
[   410.801] (**) |   |-->Monitor ""
[   410.801] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   410.801] (==) Automatically adding devices
[   410.801] (==) Automatically enabling devices
[   410.801] (==) Automatically adding GPU devices
[   410.801] (==) Automatically binding GPU devices
[   410.801] (==) Max clients allowed: 256, resource mask: 0x1f
[   410.801] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[   410.801] (==) ModulePath set to "/usr/lib/xorg/modules"
[   410.801] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   410.801] (II) Loader magic: 0x555c85989020
[   410.801] (II) Module ABI versions:
[   410.801]X.Org ANSI C Emulation: 0.4
[   410.801]X.Org Video Driver: 23.0
[   410.801]X.Org XInput driver : 24.1
[   410.801]X.Org Server Extension : 10.0
[   410.802] (++) using VT number 2

[   410.803] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_312
[   410.804] (II) xfree86: Adding drm device (/dev/dri/card0)
[   410.804] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[   410.804] (II) xfree86: Adding drm device (/dev/dri/card1)
[   410.805] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[   410.806] (**) OutputClass "nvidia" ModulePath extended to 
"/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
[   410.806] (**) OutputClass "Nvidia Prime" ModulePath extended to 
"/x86_64-linux-gnu/nvidia/xorg,/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
[   410.806] (**) OutputClass "Nvidia Prime" setting /dev/dri/card0 as 
PrimaryGPU
[   410.807] (--) PCI: (0:0:2:0) 8086:3e9b:1028:0926 rev 0, Mem @ 
0xb300/16777216, 0x6000/268435456, I/O @ 0x4000/64, BIOS @ 
0x/131072
[   410.807] (--) PCI:*(0:1:0:0) 10de:1fb9:1028:0926 rev 161, Mem @ 
0xb400/16777216, 0x7000/268435456, 0x8000/33554432, I/O @ 
0x3000/128, BIOS @ 0x/524288
[   410.807] (II) LoadModule: "glx"
[   410.807] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   410.808] (II) Module glx: vendor="X.Org Foundation"
[   410.808]compiled for 1.19.6, module version = 1.0.0
[   410.808]ABI class: X.Org Server Extension, version 10.0
[   410.808] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[   410.808]loading driver: nvidia
[   410.808] (II) Applying OutputClass "Nvidia Prime" to /dev/dri/card0
[   410.808]loading driver: nvidia
[   410.808] (==) Matched nvidia as autoconfigured driver 0
[   410.808] (==) Matched nvidia as autoconfigured driver 1
[

[Desktop-packages] [Bug 1881320] Re: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2020-05-29 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 libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1881320

Title:
  package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb
  --control subprocess returned error exit status 2

Status in libglvnd package in Ubuntu:
  New

Bug description:
  got the issue while updating

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 29 21:46:42 2020
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DuplicateSignature:
   package:libglvnd0:1.0.0-2ubuntu2
   Unpacking libegl1:amd64 (1.0.0-2ubuntu2.3) over (1.0.0-2ubuntu2) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb' is not a 
Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: libglvnd
  Title: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb 
--control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1881320] [NEW] package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2020-05-29 Thread Sneha Mestry

Public bug reported:

got the issue while updating

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglvnd0 1.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 29 21:46:42 2020
Dependencies:
 gcc-8-base 8.4.0-1ubuntu1~18.04
 libc6 2.27-3ubuntu1
 libgcc1 1:8.4.0-1ubuntu1~18.04
DuplicateSignature:
 package:libglvnd0:1.0.0-2ubuntu2
 Unpacking libegl1:amd64 (1.0.0-2ubuntu2.3) over (1.0.0-2ubuntu2) ...
 dpkg-deb: error: 
'/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb' is not a 
Debian format archive
 dpkg: error processing archive 
/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb (--unpack):
  dpkg-deb --control subprocess returned error exit status 2
ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
InstallationDate: Installed on 2020-05-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.1
SourcePackage: libglvnd
Title: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb 
--control subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb
  --control subprocess returned error exit status 2

Status in libglvnd package in Ubuntu:
  New

Bug description:
  got the issue while updating

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 29 21:46:42 2020
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DuplicateSignature:
   package:libglvnd0:1.0.0-2ubuntu2
   Unpacking libegl1:amd64 (1.0.0-2ubuntu2.3) over (1.0.0-2ubuntu2) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb' is not a 
Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: libglvnd
  Title: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb 
--control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

2020-05-29 Thread Yuri Weinstein

https://github.com/home-sweet-gnome/dash-to-panel/issues/1026

** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1026
   https://github.com/home-sweet-gnome/dash-to-panel/issues/1026

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

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

2020-05-29 Thread Mario Vukelic

Will be fixed in 3.36.3:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242#note_823253

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

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

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

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

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

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

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

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

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

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

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

  In bug #1866556;
  Lenovo ThinkPad L390 Yoga
  Asus ZenBook UX370UAF
  Acer Switch 11 V sw5-173 (said to have worked with 18.04)
  (Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the 
tablet mode seems unsupported on these devices and so the issue might be 
different)

  In upstream bug:
  Dell Inspiron 15 700 2-in-1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 19:59:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (619 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)

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

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

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

2020-05-29 Thread Luka Maljic

RTX 2060 also. Any status updates?

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1874630] Re: not start without sudo

2020-05-29 Thread AdlerHorst

I checked this. Ubuntu-software is installed and in use. So I added this
ticket to the wrong package. The problem seems caused by the fact, that
launchpad tells me that ubuntu-software do not exist.

> ubuntu-software/eoan-updates,eoan-updates,now 3.30.6-2ubuntu10.19.10.1 all  
> [installiert]
>  Utility for browsing, installing, and removing software

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

Title:
  not start without sudo

Status in gnome-software package in Ubuntu:
  New

Bug description:
  To be able installing anything I have to run Ubuntu-software with sudo
  from terminal.

  sudo chown -Rh $USER:$USER ~/

  not worked.

  Also interesting: If I do not start with sudo. I'm able to login to
  Ubutu-one but not to snap.

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

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

[Desktop-packages] [Bug 1881298] Re: Incorrect disk information is displayed after creating a new partition

2020-05-29 Thread Lin Manfu

** Description changed:

  After creating a new partition, GNOME Disks did not indicate whether or
  not the partition creation had succeeded. Instead, it indicated that
  several partitions had been destroyed, when this was not correct.
  
  I will describe the steps that lead to the issue:
  
- 1. A disk was divided into several ext4 and NTFS partitions.
+ 1. A disk had been divided into several ext4 and NTFS partitions.
  2. I shrank the last partition (NTFS) using Windows.
  3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space 
at the end of the disk.
  4. I instructed GNOME Disks to create a new ext4 logical partition using the 
dialog opened by the + symbol.
  5. The dialog disappeared without any indication of whether the operation had 
succeeded or not. At the same time, the disk graphic was updated (see 
screenshot in attachment). It said that the disk had only one partition (/) and 
the rest of the disk was free space. This implied that the operation had failed 
and all the other partitions had been destroyed.
  6. I tried closing and opening Disks, but it continued to indicate that most 
of the disk had been wiped.
  7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME 
System Monitor. The information there suggested that the existing partitions 
were intact and the new partition had been successfully created.
  8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new 
disk layout (see screenshot in attachment in comment below).
  
  I have not attempted to reproduce the issue as I cannot afford to risk
  damaging a hard disk in daily use.
  
  This behaviour is highly undesirable. Users who are informed that their
  hard disk has been wiped suffer greatly increased stress and in their
  panic may take irreversible actions in an attempt to remedy the
  situation.
  
  I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
  utility itself does not seem to have a version number.
  
  I originally reported the issue upstream at GNOME
  (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and
  they asked me to report the issue at Ubuntu instead.

** Description changed:

  After creating a new partition, GNOME Disks did not indicate whether or
  not the partition creation had succeeded. Instead, it indicated that
  several partitions had been destroyed, when this was not correct.
  
  I will describe the steps that lead to the issue:
  
- 1. A disk had been divided into several ext4 and NTFS partitions.
+ 1. A disk divided into several ext4 and NTFS partitions existed.
  2. I shrank the last partition (NTFS) using Windows.
  3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space 
at the end of the disk.
  4. I instructed GNOME Disks to create a new ext4 logical partition using the 
dialog opened by the + symbol.
  5. The dialog disappeared without any indication of whether the operation had 
succeeded or not. At the same time, the disk graphic was updated (see 
screenshot in attachment). It said that the disk had only one partition (/) and 
the rest of the disk was free space. This implied that the operation had failed 
and all the other partitions had been destroyed.
  6. I tried closing and opening Disks, but it continued to indicate that most 
of the disk had been wiped.
  7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME 
System Monitor. The information there suggested that the existing partitions 
were intact and the new partition had been successfully created.
  8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new 
disk layout (see screenshot in attachment in comment below).
  
  I have not attempted to reproduce the issue as I cannot afford to risk
  damaging a hard disk in daily use.
  
  This behaviour is highly undesirable. Users who are informed that their
  hard disk has been wiped suffer greatly increased stress and in their
  panic may take irreversible actions in an attempt to remedy the
  situation.
  
  I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
  utility itself does not seem to have a version number.
  
  I originally reported the issue upstream at GNOME
  (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and
  they asked me to report the issue at Ubuntu instead.

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

Title:
  Incorrect disk information is displayed after creating a new partition

Status in GNOME Disks:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  After creating a new partition, GNOME Disks did not indicate whether
  or not the partition creation had succeeded. Instead, it indicated
  that several partitions had been destroyed, when this was not correct.

  I will describe the steps that lead to

[Desktop-packages] [Bug 1881298] Re: Incorrect disk information is displayed after creating a new partition

2020-05-29 Thread Lin Manfu

The attachment shows the disk layout after the partition was created and
I rebooted. This is what GNOME Disks should have displayed when the
partition-creation operation succeeded.

** Attachment added: "Correctly Displayed Disk Layout"

https://bugs.launchpad.net/gnome-disk-utility/+bug/1881298/+attachment/5378411/+files/Correctly%20Displayed%20Disk.png

** Description changed:

After creating a new partition, GNOME Disks did not indicate whether or
not the partition creation had succeeded. Instead, it indicated that
several partitions had been destroyed, when this was not correct.

I will describe the steps that lead to the issue:

- A disk was divided into several ext4 and NTFS partitions.
- I shrank the last partition (NTFS) using Windows.
- I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at
the end of the disk.
- I instructed GNOME Disks to create a new ext4 logical partition using the
dialog opened by the + symbol.
- The dialog disappeared without any indication of whether the operation had
succeeded or not. At the same time, the disk graphic was updated (see
screenshot in attachment). It said that the disk had only one partition (/) and
the rest of the disk was free space. This implied that the operation had failed
and all the other partitions had been destroyed.
- I tried closing and opening Disks, but it continued to indicate that most of
the disk had been wiped.
- I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME
System Monitor. The information there suggested that the existing partitions
were intact and the new partition had been successfully created.
- I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk
layout (see screenshot in attachment in comment below).
+ 1. A disk was divided into several ext4 and NTFS partitions.
+ 2. I shrank the last partition (NTFS) using Windows.
+ 3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space
at the end of the disk.
+ 4. I instructed GNOME Disks to create a new ext4 logical partition using the
dialog opened by the + symbol.
+ 5. The dialog disappeared without any indication of whether the operation had
succeeded or not. At the same time, the disk graphic was updated (see
screenshot in attachment). It said that the disk had only one partition (/) and
the rest of the disk was free space. This implied that the operation had failed
and all the other partitions had been destroyed.
+ 6. I tried closing and opening Disks, but it continued to indicate that most
of the disk had been wiped.
+ 7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME
System Monitor. The information there suggested that the existing partitions
were intact and the new partition had been successfully created.
+ 8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new
disk layout (see screenshot in attachment in comment below).

- I have not attempted to reproduce the issue as I cannot afford to risk
damaging a hard disk in daily use.
- This behaviour is highly undesirable. Users who are informed that their hard
disk has been wiped suffer greatly increased stress and in their panic may take
irreversible actions in an attempt to remedy the situation.
+ I have not attempted to reproduce the issue as I cannot afford to risk
+ damaging a hard disk in daily use.
+
+ This behaviour is highly undesirable. Users who are informed that their
+ hard disk has been wiped suffer greatly increased stress and in their
+ panic may take irreversible actions in an attempt to remedy the
+ situation.

I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
utility itself does not seem to have a version number.

I originally reported the issue upstream at GNOME
(https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and
they asked me to report the issue at Ubuntu instead.

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

Title:
Incorrect disk information is displayed after creating a new partition

Status in GNOME Disks:
Unknown
Status in gnome-disk-utility package in Ubuntu:
New

Bug description:
After creating a new partition, GNOME Disks did not indicate whether
or not the partition creation had succeeded. Instead, it indicated
that several partitions had been destroyed, when this was not correct.

I will describe the steps that lead to the issue:

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

2020-05-29 Thread staycalm

Same here with a RTX 2070 Super.

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1881301] [NEW] q

2020-05-29 Thread Matias Rubio

Public bug reported:

q

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_67 wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 29 09:16:10 2020
DistUpgraded: 2019-01-04 17:00:34,973 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-88-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
InstallationDate: Installed on 2017-02-06 (1207 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20156
ProcEnviron:
 LANGUAGE=es_PE:es
 PATH=(custom, no user)
 LANG=es_PE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=cef7f1ec-6114-4595-a4fc-e46a6813a2ca ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-01-04 (510 days ago)
dmi.bios.date: 08/16/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 62CN89WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G480
dmi.board.vendor: LENOVO
dmi.board.version: 3194WIN8 STD SGL
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G480
dmi.modalias: 
dmi:bvnLENOVO:bvr62CN89WW:bd08/16/2012:svnLENOVO:pn20156:pvrLenovoG480:rvnLENOVO:rnLenovoG480:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG480:
dmi.product.family: ChiefRiver System
dmi.product.name: 20156
dmi.product.version: Lenovo G480
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Jan  4 13:11:34 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17740 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1881301

Title:
  q

Status in xorg package in Ubuntu:
  New

Bug description:
  q

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_67 wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 29 09:16:10 2020
  DistUpgraded: 2019-01-04 17:00:34,973 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-88-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2017-02-06 (1207 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20156
  ProcEnviron:
   LANGUAGE=es_PE:es
   PATH=(custom, no user)
   LANG=es_PE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=cef7f1ec-6114-4595-a4fc-e46a6813a2ca ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-04 (510 days ago)
  dmi.bios.date: 08/16/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN89WW
  dmi.board.asset.tag: No

[Desktop-packages] [Bug 1881298] [NEW] Incorrect disk information is displayed after creating a new partition

2020-05-29 Thread Lin Manfu

Public bug reported:

I will describe the steps that lead to the issue:

1. A disk divided into several ext4 and NTFS partitions existed.
2. I shrank the last partition (NTFS) using Windows.
3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space
at the end of the disk.
4. I instructed GNOME Disks to create a new ext4 logical partition using the
dialog opened by the + symbol.
5. The dialog disappeared without any indication of whether the operation had
succeeded or not. At the same time, the disk graphic was updated (see
screenshot in attachment). It said that the disk had only one partition (/) and
the rest of the disk was free space. This implied that the operation had failed
and all the other partitions had been destroyed.
6. I tried closing and opening Disks, but it continued to indicate that most of
the disk had been wiped.
7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME
System Monitor. The information there suggested that the existing partitions
were intact and the new partition had been successfully created.
8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new
disk layout (see screenshot in attachment in comment below).

I have not attempted to reproduce the issue as I cannot afford to risk
damaging a hard disk in daily use.

This behaviour is highly undesirable. Users who are informed that their
hard disk has been wiped suffer greatly increased stress and in their
panic may take irreversible actions in an attempt to remedy the
situation.

I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
utility itself does not seem to have a version number.

I originally reported the issue upstream at GNOME
(https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and
they asked me to report the issue at Ubuntu instead.

** Affects: gnome-disk-utility
Importance: Unknown
Status: Unknown

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

** Attachment added: "What GNOME Disks Showed After Partition Creation"

https://bugs.launchpad.net/bugs/1881298/+attachment/5378410/+files/What%20Disks%20Showed%20After%20Partition%20Creation.png

** Description changed:

I will describe the steps that lead to the issue:

A disk was divided into several ext4 and NTFS partitions.
I shrank the last partition (NTFS) using Windows.
I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at
the end of the disk.
I instructed GNOME Disks to create a new ext4 logical partition using the
dialog opened by the + symbol.
- The dialog disappeared without any indication of whether the operation had
succeeded or not. At the same time, the disk graphic was updated (see
screenshot above). It said that the disk had only one partition (/) and the
rest of the disk was free space. This implied that the operation had failed and
all the other partitions had been destroyed.
+ The dialog disappeared without any indication of whether the operation had
succeeded or not. At the same time, the disk graphic was updated (see
screenshot in attachment). It said that the disk had only one partition (/) and
the rest of the disk was free space. This implied that the operation had failed
and all the other partitions had been destroyed.
I tried closing and opening Disks, but it continued to indicate that most of
the disk had been wiped.
I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME
System Monitor. The information there suggested that the existing partitions
were intact and the new partition had been successfully created.
- I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk
layout:
+ I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk
layout (see screenshot in attachment in comment below).

I have not attempted to reproduce the issue as I cannot afford to risk
damaging a hard disk in daily use.
This behaviour is highly undesirable. Users who are informed that their hard
disk has been wiped suffer greatly increased stress and in their panic may take
irreversible actions in an attempt to remedy the situation.
- I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
utility itself does not seem to have a version number.
+
+ I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
+ utility itself does not seem to have a version number.
+
+ I originally reported the issue upstream at GNOME
+

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

2020-05-29 Thread Diegstroyer

I find other extensions with same bug:
Panel-OSD
Unite

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

[Desktop-packages] [Bug 1881294] [NEW] Apparmor blocks evince GUI-Input-Dialogs

2020-05-29 Thread Reinhard

Public bug reported:

Network Users (LDAP + NFS4 home) cannot interact with evince GUI-input-
elements.

* page navigation per number not possible
* select pages to print not possible
* save open PDF with different name not possible

Local user on the same machine behaves as expected.


apparmor messages  in /var/log/syslog 

May 29 14:37:07 r002pc51 kernel: [15848.736916] audit: type=1400
audit(1590755827.768:827): apparmor="DENIED" operation="file_lock"
profile="/usr/bin/evince" name="/home/teachers/ttfinr/.cache/event-
sound-cache.tdb.2176809057334199ab75052753e0683a.x86_64-pc-linux-gnu"
pid=34988 comm="evince" requested_mask="k" denied_mask="k" fsuid=4515
ouid=4515

May 29 14:37:07 r002pc51 kernel: [15848.739259] audit: type=1400
audit(1590755827.772:828): apparmor="DENIED" operation="link"
profile="/usr/bin/evince" name="/home/teachers/ttfinr/.local/share/gvfs-
metadata/.open04eaJ8" pid=34988 comm="pool-evince" requested_mask="l"
denied_mask="l" fsuid=4515 ouid=4515
target="/home/teachers/ttfinr/.local/share/gvfs-metadata/home"

May 29 14:37:07 r002pc51 kernel: [15848.739974] audit: type=1400
audit(1590755827.772:829): apparmor="DENIED" operation="open"
profile="/usr/bin/evince" name="/run/user/4515/gvfs-
metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="r"
denied_mask="r" fsuid=4515 ouid=4515

May 29 14:37:07 r002pc51 kernel: [15848.740088] audit: type=1400
audit(1590755827.772:830): apparmor="DENIED" operation="unlink"
profile="/usr/bin/evince" name="/run/user/4515/gvfs-
metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="d"
denied_mask="d" fsuid=4515 ouid=4515

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


** Tags: apparmor envince

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

Title:
  Apparmor blocks evince GUI-Input-Dialogs

Status in evince package in Ubuntu:
  New

Bug description:
  Network Users (LDAP + NFS4 home) cannot interact with evince GUI-
  input-elements.

  * page navigation per number not possible
  * select pages to print not possible
  * save open PDF with different name not possible

  Local user on the same machine behaves as expected.

  
  apparmor messages  in /var/log/syslog 

  May 29 14:37:07 r002pc51 kernel: [15848.736916] audit: type=1400
  audit(1590755827.768:827): apparmor="DENIED" operation="file_lock"
  profile="/usr/bin/evince" name="/home/teachers/ttfinr/.cache/event-
  sound-cache.tdb.2176809057334199ab75052753e0683a.x86_64-pc-linux-gnu"
  pid=34988 comm="evince" requested_mask="k" denied_mask="k" fsuid=4515
  ouid=4515

  May 29 14:37:07 r002pc51 kernel: [15848.739259] audit: type=1400
  audit(1590755827.772:828): apparmor="DENIED" operation="link"
  profile="/usr/bin/evince" name="/home/teachers/ttfinr/.local/share
  /gvfs-metadata/.open04eaJ8" pid=34988 comm="pool-evince"
  requested_mask="l" denied_mask="l" fsuid=4515 ouid=4515
  target="/home/teachers/ttfinr/.local/share/gvfs-metadata/home"

  May 29 14:37:07 r002pc51 kernel: [15848.739974] audit: type=1400
  audit(1590755827.772:829): apparmor="DENIED" operation="open"
  profile="/usr/bin/evince" name="/run/user/4515/gvfs-
  metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="r"
  denied_mask="r" fsuid=4515 ouid=4515

  May 29 14:37:07 r002pc51 kernel: [15848.740088] audit: type=1400
  audit(1590755827.772:830): apparmor="DENIED" operation="unlink"
  profile="/usr/bin/evince" name="/run/user/4515/gvfs-
  metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="d"
  denied_mask="d" fsuid=4515 ouid=4515

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

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

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

2020-05-29 Thread Brett D

In my case I was able to narrow down the problem to the gTile extension.
(I've never had Dash-to-panel installed.)

Now all I have to do is find a way to live without gTile :)  Thanks for
the tip!

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

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

2020-05-29 Thread Cornelius

When switching from A2DP to HSP/HFP I get this log message 5 times:

Bluetooth: hci0: SCO packet for unknown connection handle 0

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

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

2020-05-29 Thread Cornelius

Also in 18.04 after regular update some days ago.

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-29 Thread Krister

I installed 1.22.10-1ubuntu2.1 and turned the hotspot on...
   my clients can use the hotspot normally.

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

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

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  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/1870359/+subscriptions

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

[Desktop-packages] [Bug 1874630] Re: not start without sudo

2020-05-29 Thread Paul White

Yes, software-center is what was used when Unity was the default desktop
environment. Moving to gnome-software (also known as ubuntu-software)
which is the default for Ubuntu 19.10.

** Tags added: eoan

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => 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/1874630

Title:
  not start without sudo

Status in gnome-software package in Ubuntu:
  New

Bug description:
  To be able installing anything I have to run Ubuntu-software with sudo
  from terminal.

  sudo chown -Rh $USER:$USER ~/

  not worked.

  Also interesting: If I do not start with sudo. I'm able to login to
  Ubutu-one but not to snap.

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

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

[Desktop-packages] [Bug 1874630] [NEW] not start without sudo

You have been subscribed to a public bug:

To be able installing anything I have to run Ubuntu-software with sudo
from terminal.

sudo chown -Rh $USER:$USER ~/

not worked.

Also interesting: If I do not start with sudo. I'm able to login to
Ubutu-one but not to snap.

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


** Tags: eoan
-- 
not start without sudo
https://bugs.launchpad.net/bugs/1874630
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software 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 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created

2020-05-29 Thread Patrick Wu

Rene Prillop,

I have submitted the SRU to backport the fix back to bionic and xenial.
It is usually expected to be completed in 2-3 weeks

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

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

Status in wslu package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

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

  [Test Case]
   * TODO

  [Regression Potential]
   * TODO
  [Other Info]

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

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

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

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

[Desktop-packages] [Bug 1881284] [NEW] Pause the music after suspend

2020-05-29 Thread Rajesh Chaudhary

Public bug reported:

Hi, I don't know how to describe it. What I basically need is pause the
media/music automatically after I come back from suspend.

Let's suppose we're suspending the laptop while playing the media
(Spotify, youtube)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 18:09:52 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-04 (24 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Pause the music after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi, I don't know how to describe it. What I basically need is pause
  the media/music automatically after I come back from suspend.

  Let's suppose we're suspending the laptop while playing the media
  (Spotify, youtube)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 18:09:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-04 (24 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"

2020-05-29 Thread Olivier Tilloy

Once chromium 84 becomes stable, in ~ 6 weeks time.

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

Title:
  [snap] Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

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

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

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

2020-05-29 Thread Rene Prillop

What is the expected latency for it to reach Bionic? 1.5 months has passed 
since...
I think there is no real benefit if it gets released in 2023 :)

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

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

Status in wslu package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

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

  [Test Case]
   * TODO

  [Regression Potential]
   * TODO
  [Other Info]

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

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

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

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

[Desktop-packages] [Bug 1881062] Re: Mouse pointer disappeared after upgrade

2020-05-29 Thread Kai-Heng Feng

Seems like the desktop is Unity. I wonder if same thing happens under
GNOME...

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

Title:
  Mouse pointer disappeared after upgrade

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Mouse vendor: Elecom
  Mouse name: Deft M-DT20R
  S/N 99011158
  S/N 9700261B
  I have two sets of this model and both are not working any more.
  Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th 
May 2020.
  I also upgraded BIOS of ThinkStation P500 from A4KT89US to A4KTA7US just an 
hour before the upgrade.
  However I plugged in an old wired Elecom USB mouse and this is working.
  And also I tried another wireless USB mouse Logicool M570, this model is 
working except the left-click or right-click (means unstable).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03: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:
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 28 13:14:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097]
  InstallationDate: Installed on 2020-05-25 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 30A6S45A16
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic 
root=UUID=822191be-6b70-4841-97dc-e4c008d418b2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A4KTA7AUS
  dmi.board.name: 102F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN 3425060692537
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrA4KTA7AUS:bd04/13/2020:svnLENOVO:pn30A6S45A16:pvrThinkStationP500:rvnLENOVO:rn102F:rvrSDK0J40705WIN3425060692537:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: ThinkStation P500
  dmi.product.name: 30A6S45A16
  dmi.product.sku: LENOVO_MT_30A6_BU_Think_FM_ThinkStation P500
  dmi.product.version: ThinkStation P500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.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.1
  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/linux/+bug/1881062/+subscriptions

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1881273/+attachment/5378368/+files/ProcEnviron.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/1881273

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 19.10
  NonfreeKernelModules: nvidia wl
  Package: nautilus 1:3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-55-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1881273/+attachment/5378367/+files/ProcCpuinfoMinimal.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/1881273

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 19.10
  NonfreeKernelModules: nvidia wl
  Package: nautilus 1:3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-55-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881273] Re: Redo folder copy: incorrect recursion

apport information

** Tags added: apport-collected eoan

** Description changed:

  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.
  
  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.9
+ Architecture: amd64
+ CurrentDesktop: Unity:Unity7:ubuntu
+ DistroRelease: Ubuntu 19.10
+ NonfreeKernelModules: nvidia wl
+ Package: nautilus 1:3.34.1-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
+ Tags:  eoan
+ Uname: Linux 5.3.0-55-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ usr_lib_nautilus:

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1881273/+attachment/5378365/+files/Dependencies.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/1881273

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 19.10
  NonfreeKernelModules: nvidia wl
  Package: nautilus 1:3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-55-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1881273] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1881273/+attachment/5378366/+files/GsettingsChanges.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/1881273

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 19.10
  NonfreeKernelModules: nvidia wl
  Package: nautilus 1:3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-55-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"

Will this be in the next stable channel snap update?

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

Title:
  [snap] Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

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

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

[Desktop-packages] [Bug 1881273] Re: Redo folder copy: incorrect recursion

2020-05-29 Thread lotuspsychje

Thank you for reporting this bug and make ubuntu better!

Please when filing bugs on ubuntu use ubuntu-bug packagename in the future
so relevant system info gets pulled into your bug and developers can debug
a better way.

You can still pull the info in your existing bug with: apport-collect 1881273
in this stage, thank you!

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

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)

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

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

[Desktop-packages] [Bug 1881273] [NEW] Redo folder copy: incorrect recursion

Public bug reported:

I did the following:
- I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
- I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
- I pressed shift+ctrl+Z to redo this action.

This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
`/somewhere/my-folder (copy)/has/a/child.txt` (correct)
`/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
`/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
`/somewhere/my-folder/has/a/child (copy).txt` (wrong)

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

** Description changed:

  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
- - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)`
+ - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.
  
  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times: I also got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)

** Description changed:

  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.
  
- This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times: I also got:
+ This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)

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

Title:
  Redo folder copy: incorrect recursion

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did the following:
  - I copied folder `/somewhere/my-folder` to the same parent folder 
`/somewhere`, yielding `/somewhere/my-folder (copy)`.
  - I pressed ctrl+Z to undo this action (and confirmed), correctly causing 
`/somewhere/my-folder (copy)` to disappear.
  - I pressed shift+ctrl+Z to redo this action.

  This resulted not only in the reappearance of `/somewhere/my-folder (copy)` 
with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` 
was copied several times. I got:
  `/somewhere/my-folder (copy)/has/a/child.txt` (correct)
  `/somewhere/my-folder/has (copy)/a/child.txt` (wrong)
  `/somewhere/my-folder/has/a (copy)/child.txt` (wrong)
  `/somewhere/my-folder/has/a/child (copy).txt` (wrong)

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

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

[Desktop-packages] [Bug 1881266] [NEW] Xorg crash

2020-05-29 Thread amirhosein mohammadi

Public bug reported:

hi 
there is something wrong with my display
when i using laptop for a while display crashed and getting black
my monitor is 4k and i guess it's cause of this problem

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
Uname: Linux 5.4.0-34-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.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 14:24:38 2020
DistUpgraded: 2020-05-11 18:00:30,770 DEBUG refresh of snap core18 succeeded
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d8d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d8d]
InstallationDate: Installed on 2020-05-11 (17 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: ASUSTeK COMPUTER INC. N552VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic 
root=UUID=a76ee8a9-d0e8-4e74-8578-67f8f39c8f00 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-05-11 (17 days ago)
dmi.bios.date: 08/31/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN552VW.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N552VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.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.1
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 crash 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/1881266

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  hi 
  there is something wrong with my display
  when i using laptop for a while display crashed and getting black
  my monitor is 4k and i guess it's cause of this problem

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 14:24:38 2020
  DistUpgraded: 2020-05-11 18:00:30,770 DEBUG refresh of snap core18 succeeded
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)

I can confirm that setting org.gnome.desktop.privacy remember-app-usage
to false, and thus removing the Frequent / All buttons, also works
around this problem.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders (when ubuntu-dock is loaded)

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

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)

I think part of the culprit may be that the Frequent / All buttons on
the bottom are pushed downwards when opening an app folder on a 1366x768
display, causing the grid to re-align. This doesn't happen on 1280x800
or 1680x1050, where the bugs related to the many dots on the right or
the shell locking up are also not present.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders (when ubuntu-dock is loaded)

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

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-29 Thread Ludovic Rousseau

The fact that the LED is green then goes to red after a few seconds is 
completely normal.
See https://ludovicrousseau.blogspot.com/2010/10/card-auto-power-on-and-off.html

The fact that you get "PowerUp failed" errors is NOT normal.
It is a hardware issue with the card and/or the reader.

That is why I asked you to try with another smart card.

On my side I tried with current version of pcsc-lite and libccid and I
have no problem with my ActivIdentity Activkey_Sim device.

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)

This is definitely resolution related. I am unable to reproduce this on
my X200's and T400's (1280x800) or T500's (1680x1050), but it hits me
every time on my X220's (1366x768).

I also tried gnome-shell-extension-ubuntu-dock 68 from focal-proposed,
but that does not help at all. Setting org.gnome.shell.extensions.dash-
to-dock extend-height to false indeed avoids the problem, but it doesn't
look very nice.

There seem to be more problems with GNOME Shell on this resolution. The
text in the app folder icon doesn't line out nicely, and when opening
the drawer, the application icons beneath it seem to re-align. When
disabling the Ubuntu Dock extension, the normal GNOME dock also seems to
grow and move when an app folder is opened. This does not happen on the
other resolutions.

Therefore, I am unsure if this is only caused by the extension. I think
it's not, but the dock just makes it worse.

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

Title:
Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
of app icon folders (when ubuntu-dock is loaded)

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

Bug description:
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

Bug: Gnome shell while opening app drawer, clicking on an app folder
and clicking on the blank area freezes gnome shell and it makes the
session completely unusable and non recoverable.

How to reproduce: 1- Click 9 dots on bottom corner of dash (the app
launcher button), wait for the app grid to show up.

2- Click on an app folder to open it.
3- Click on the blank area outside of the opened folder dialog.
4- Gnome shell gets freezes and never come back from this state, on both
wayland session and x11 session.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:00:13 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/828
   Importance: Unknown
   Status: Unknown

** No longer affects: mutter (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1880784] Re: Gamemode sets incorrect default governor

2020-05-29 Thread Stephan Lachnit

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

This is fixed in Ubuntu 20.10 devel with gamemode-1.5.1-0ubuntu4, same
bug as https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1875740.

** This bug has been marked a duplicate of bug 1875740
   gamemode throttles (AMD?) CPUs on exit (powersave governor)

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

Title:
  Gamemode sets incorrect default governor

Status in gamemode package in Ubuntu:
  Fix Committed

Bug description:
  gamemode 1.5.1-0ubuntu3 in Ubuntu 20.04 LTS

  Gamemode sets the incorrect default cpu governor which causes huge
  performance decreases in some scenarios.

  What I expect to happen:
  Gamemode on exit should set the cpu governor back to system default (ondemand 
in Ubuntu's case I believe)

  What happens instead:
  Gamemode currently will set the cpu governor to powersave when exiting

  Fix:
  /etc/gamemode.ini - Commenting out line `defaultgov=powersave` will correctly 
set the cpu governor back to the system default 

  
https://github.com/FeralInteractive/gamemode/commit/1c9cd2de5bd47c04a124445eb5b567f37ec3e85f

  A fix is currently in gamemode master, but I hope this can be
  addressed in Ubuntu 20.04

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

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

[Desktop-packages] [Bug 1881115] Re: desktop - no shift-delete, non localized menu

2020-05-29 Thread frank

templates submenu is also missing on desktop...available in nautilus-
window (i have created some templates to get the menu in nautilus-
window)

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

Title:
  desktop - no shift-delete, non localized menu

Status in nautilus package in Ubuntu:
  New

Bug description:
  Hi,

  i've noticed 2 problems on desktop (gnome-flashback), which is imho
  handled by nautilus...

  - contextmenu (rightclick) is not localized (german environment, menu is 
english)
  - shift-delete does nothing, in menu there is only "move to trash" (+open 
+properties), no way to delete files without trash

  regards Frank

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu May 28 14:12:30 2020
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-04-27 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

2020-05-29 Thread Aleksander Miera

Fix in Xorg:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/447#note_515426

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

That is bug 184.

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

2020-05-29 Thread Diegstroyer

Hi again, in my case, Dash-to-panel is the guilty, installed by
synaptic... removing it and installing from Gnome.org solve the problem.

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5

2020-05-29 Thread Olivier Tilloy

Confirmed to be fixed with https://bazaar.launchpad.net/~chromium-team
/chromium-browser/bionic-dev/revision/1552.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  DevTools does not open at 84.0.4115.5

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1072187

  Steps to reproduce the problem:
  1. Ctrl+Shift+I or right-click, click Inspect
  2. Navigate to chrome://inspect/#pages, click inspect
  3.

  What is the expected behavior?
  DevTools to open

  What went wrong?
  DevTools does not open.

  Did this work before? Yes Chromium 83

  Chrome version: 84.0.4115.5  Channel: dev

  $ chromium-browser --temp-profile

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
  error: gtk.css:597:14: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
  error: gtk.css:597:14: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
  error: gtk.css:600:17: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
  error: gtk.css:784:14: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
  error: gtk.css:784:14: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
  error: gtk.css:787:17: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
  error: gtk.css:1096:14: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
  error: gtk.css:1096:14: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
  error: gtk.css:1099:17: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
  error: gtk.css:2286:8: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
  error: gtk.css:2286:18: Using Pango syntax for the font: style
  property is deprecated; please use CSS syntax

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
  error: gtk.css:2291:8: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
  error: gtk.css:2291:18: Using Pango syntax for the font: style
  property is deprecated; please use CSS syntax

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
  error: gtk.css:4357:14: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
  error: gtk.css:4357:14: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
  error: gtk.css:4419:12: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
  error: gtk.css:4419:12: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
  error: gtk.css:4428:16: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4428:16: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4443:22: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4443:22: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4499:12: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4501:16: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4501:16: Expected a string.

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
  error: gtk.css:4549:12: not a number

  (chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error: 
gtk.css:4549:12: Expected a string.
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to open i915 (search paths 
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  failed to load driver: i915
  MESA-LOADER: failed to open kms_swrast (search paths 
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  failed to load driver: kms_swrast
  MESA-LOADER: failed to open swrast (search paths 
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  failed to load swrast driver
  [21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot 
read property 'Runtime' of undefined", source: 
devtools://devtools/bundled/root/root-legacy.js (1)
  [21919:21919:0421/034207.195989:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot 
read property 'Runtime' of undefined", source: 
devtools://devtools/bundled/root/root-legacy.js (1)
  [21919:21919:0421/034207.197368:ERROR:CONSOLE(70)] "Uncaught TypeError: 
Cannot read

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work

That's a good point. A few people are finding buggy extensions
(especially dash-to-panel) are causing a crash on screen lock, which
causes a blink and the lock to fail. That's mostly covered by bug
184.

So yes, please do make sure you remove all your extensions as part of
the testing process.

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

Title:
  Screen lock won't work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Screen lock won't work i focal.

  Used to work fine on Super-L and now what happens it freezes for awhile 
(suspect time out defined) and then blinks and comes back into windows session.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694

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

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

[Desktop-packages] [Bug 1880337] Re: Screen lock won't work