date:20200610

Rather than being a graphics driver problem it looks like it could be
caused by one of the extensions:

  'system_moni...@bghome.gmail.com',
  'clipboard-indica...@tudmotu.com',
  'topic...@phocean.net'

Please disable/uninstall those and retest.

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1882415] Re: artifact in top-right corner

apport information

** Tags added: apport-collected

** Description changed:

  Ubuntu 20.04, Gnome 3.36.2, Nvidia
  
  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2014-11-12 (2037 days ago)
+ InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
+ RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
+ Tags:  focal
+ Uname: Linux 5.4.0-37-lowlatency x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1882415/+attachment/5382750/+files/GsettingsChanges.txt

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1882415] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1882415/+attachment/5382754/+files/monitors.xml.txt

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1883005] Re: Gnome Shell freeze

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

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


** Summary changed:

- Xorg freeze
+ Gnome Shell freeze

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: adsson andre da silva gomes (adsson) => (unassigned)

** This bug has been marked a duplicate of bug 1872268
   Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app 
icon folders (when ubuntu-dock is loaded)

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

Title:
  Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This bug have been happing on my PC, in the applications when i open
  some application folder and after click out of it, to close it. The
  screen just freeze and i have to reboot my notebook (Lenovo-
  ideapad-310).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  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: Wed Jun 10 15:08:37 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2020-06-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 80UH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UH:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UH
  dmi.product.sku: LENOVO_MT_80UH_BU_idea_FM_Lenovo ideapad 310-15ISK
  dmi.product.version: Lenovo ideapad 310-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/gnome-shell/+bug/1883005/+subscriptions

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

[Desktop-packages] [Bug 1883013] Re: gnome-shell-extensions-prefs does not show any updates

** Tags added: 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/1883013

Title:
  gnome-shell-extensions-prefs does not show any updates

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  One of the touted features of the GNOME 3.36 release was being able to
  update extensions directly from the Extensions app.  This doesn't seem
  to be working at all on Ubuntu 20.04, however.  I regularly receive
  update notifications from the Firefox extension, but the only way I
  have found to actually update them is using the old Gnome Extensions
  website.  I can still configure, disable, and remove extensions from
  the app, it just doesn't show any updates.  Is this functionality
  somehow disabled in Ubuntu?

  gnome-shell-extension-prefs 3.36.2-1ubuntu1~20.04.1

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

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

[Desktop-packages] [Bug 1856838] Re: gnome-shell using a lot of RAM after repeatedly opening the overview

** Summary changed:

- gnome-shell using a lot of RAM after repeatedly pressing Super+A
+ gnome-shell using a lot of RAM after repeatedly opening the overview

** Tags added: 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/1856838

Title:
  gnome-shell using a lot of RAM after repeatedly opening the overview

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

Bug description:
  Just noticed my gnome-shell was using 3GB RSS. Which seems excessive.
  Spoke to duflu on irc and he suggested I file a bug, and to make sure
  I'm not using any extra extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 10:49:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (681 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago)

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

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

[Desktop-packages] [Bug 1882781] Re: Gnome 3.36.2 leaking in 20.04

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

The attachment 'GsettingsChanges.txt' is showing two extensions were
enabled, so please make sure they are both removed.

If the problem still happens then it sounds like it's already covered by
bug 1856838.

** This bug has been marked a duplicate of bug 1856838
gnome-shell using a lot of RAM after repeatedly opening the overview

** Information type changed from Private to Public

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

Title:
Gnome 3.36.2 leaking in 20.04

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
I've noticed lately that the performance of the UI in Gnome 3.36.2
seems to decay with uptime.

The most obvious manifestation is that over time, window animations
have a delay and feel "sticky". Applications themselves seem
unaffected. When I tell gnome to switch workspaces, there's about a
half second to full second delay before the animation happens. This
also applies to things like pressing the meta key to show all my
windows or pressing alt-tab. Each one appears to share the same delay.

I'm running a fairly unremarkable desktop setup using vanilla gnome on
Ubuntu 20.04.

My research on this issue seems to indicate that there were memory
leak issues in 18.xx versions of the OS, but that those were
supposedly fixed. The only thing I can conclude at this point is that
a new issue has emerged, there was a regression, or the original fix
didn't work.

The animation delay is sapping productivity to the point that I
eventually have to reboot my system. The gnome-shell process
definitely leaks over time as it starts around ~300mb and if left for
a day will sit at ~600mb or more.

---

Regarding my overall hardware and nominal state of my system, I'm
experiencing this issue even as I'm creating this question. I'm
running the stock/vanilla gnome desktop, not the ubuntu customized
one.

My system has 32gb of RAM, only 6gb of which are in use currently. My
CPU usage fluctuates across 12 vcores up to 20% max. I have an RTX
2060 for my GPU.

At least as best as I can tell, I see no issue with the amount of
resources gnome-shell is getting right now. 

---

There also appear to be other accounts of this same issue building up
since the release of 20.04. It's clear that this is a widespread
issue:

https://www.reddit.com/r/gnome/comments/fxffcd/gnome_shell_336_in_ubuntu_2004_still_leaks/

I would treat this with some urgency as for regular users this bug
renders the OS completely unusable.

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Jun 9 08:19:21 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-20 (50 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
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/1882781/+subscriptions

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

[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

There's a discrepancy between the screenshot in comment #1 and that in
comment #3. The screenshot in comment #1 shows extensions clearly
running, and the screenshot in comment #3 suggests there are none.

After you have disabled all extensions, please:

1. Log out and in again.

2. Tell us if the bug still happens.

3. Provide a new screenshot of the whole desktop.

4. Run this command:

   gsettings list-recursively org.gnome.shell > settings.txt

   and attach the resulting text file here.

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

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a very serious security issue:

  When I lock my desktop with SUPER (windows) + L my screen gets locked
  and goes to black. Sometimes when I return to my PC and move my mouse
  to turn my screen back on I notice that the Ubuntu Dock + the Top Bar
  are accessible from the lockscreen.

  I unfortunately can't remember if they were accessible from the moment
  I locked the screen or became accessible after returning from fade to
  black. (This is not the first time this issue happened.)

  I was able to open the settings menu from the top bar and use all
  indicators. You can actually start the programs in the Ubuntu Dock and
  give keyboard inputs to them. For example I was able to start the
  terminal emulator from the lock screen and run firefox and other
  applications. So an attacker could run arbitrary commands with user
  privileges from the lockscreen!

  The indicators drop down menus were fully visible on the lock screen
  while the Dock applications remained hidden "behind" the lockscreen
  (however still accessible via keyboard as described above).

  I have attached a screenshot of the bug. I unfortunately had no camera
  at hand to film me running terminal commands.

  Please contact me if you need additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 13:35:28 2020
  InstallationDate: Installed on 2015-12-22 (1627 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719

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

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

[Desktop-packages] [Bug 1882464] Re: menu icons in top bars exceed their boundary

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

This sounds like bug 1877288. Please also try disabling the 'ubuntu-
dock' extension.

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

** This bug has been marked a duplicate of bug 1877288
   Text and icons in top bar is offset and hanging down

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

Title:
  menu icons in top bars exceed their boundary

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes the top bar icons (battery icon, wifi, sound etc...) are going out 
of their boundary at the top bar. when doing so they take over any maximized 
window top bar (e.g. browser, file explorer or any other app). By doing so it 
prevents the user from reaching the X, resize, and minimize buttons at the top 
right bar of the app. 
  Sometimes the app menu on that same top bar is exceeding as well causing the 
same problem on the left side of the screen.
  It happened several times, but i cant seem to notice what cause it...
  The problem also disappear quite easily, but the only time i noticed 
something that stopped it is when i toggled off the "application menu" option 
in "Extensions" - i.e. made any structure change in the top bar.

  I'm using ubuntu 20.04 LTS "focal fossa".
  I use a workspace indicator, and a horizontal workspace structure which i 
both toggled on from "Extensions".

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

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

[Desktop-packages] [Bug 1881415] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image() from st_theme_node_paint_equal() from st_widget_recompute_style()

Daniel, please use these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image()
  from st_theme_node_paint_equal() from st_widget_recompute_style()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/40c10d17842e966b2b77712dd58f500272d16dd8

  ---

  This crash occurs around 50% of the time on automatic screen lock or
  possible on screen blank.

  ProblemType: Crash
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat May 30 18:29:24 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-05-21 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SegvAnalysis:
   Segfault happened at: 0x7f7ce568a7ff :   
mov(%rax),%rsi
   PC (0x7f7ce568a7ff) ok
   source "(%rax)" (0x0260) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_get_border_image () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-29T18:09:27.628392
  separator:

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

Yes that's what the upstream bug for this bug says:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709

But I expect Ubuntu 20.04 will get the fix soon.

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1866703] Re: gnome-shell crashes on lock screen

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

More recent crashes during locking are generally 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/1866703

Title:
  gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After latest focal updates, gnome-shell crashes and I lose my entire
  session when I lock the screen.

  c@slate:~$ dpkg -l | grep gnome-shell
  ii  gnome-shell3.35.91-1ubuntu2   
 amd64graphical shell for the GNOME desktop

  c@slate:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  syslog at the time of crash shows:

  Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
  Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
  Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-power[14200]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[14199]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate evolution-alarm[14258]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate update-notifier[15178]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-color[14190]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with 
result 'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management 
handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling.
  Mar  9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main 
process exited, code=dumped, status=5/TRAP
  Mar  9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken 
(explicit kill or server shutdown).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 15:49:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-08-26 (561 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago)

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

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

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

1. That is bug 1832407 you are describing. Although you don't actually
need to be able to remove the extension package in order to replace it.
Installing any extension locally for your own account will override the
system version.

2. Canonical does contribute to desktop-icons when we have time.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

This bug is closed. If you experience any ongoing problems then please
open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

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

[Desktop-packages] [Bug 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

2020-06-10 Thread Ken VanDine

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

** Changed in: vte2.91 (Ubuntu Groovy)
   Status: New => Fix Released

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

** Changed in: vte2.91 (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: vte2.91 (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: gnome-terminal (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: gnome-terminal (Ubuntu Focal)
   Status: New => Triaged

** Changed in: vte2.91 (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Triaged
Status in vte2.91 source package in Focal:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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

[Desktop-packages] [Bug 1881415] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image() from st_theme_node_paint_equal() from st_widget_recompute_style()

2020-06-10 Thread Daniel Rodriguez

I think I have this issue, but I'm not 100% sure. I tried to find the
crash log in /var/crash, but it looks slightly different. There's no
segvanalysis or stacktrace, though I can find a signal 11 crash in
/var/log/apport.log. How can I go about confirming this is the bug I'm
experiencing?

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image()
  from st_theme_node_paint_equal() from st_widget_recompute_style()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/40c10d17842e966b2b77712dd58f500272d16dd8

  ---

  This crash occurs around 50% of the time on automatic screen lock or
  possible on screen blank.

  ProblemType: Crash
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat May 30 18:29:24 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-05-21 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SegvAnalysis:
   Segfault happened at: 0x7f7ce568a7ff :   
mov(%rax),%rsi
   PC (0x7f7ce568a7ff) ok
   source "(%rax)" (0x0260) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_get_border_image () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-29T18:09:27.628392
  separator:

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

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

[Desktop-packages] [Bug 1866703] Re: gnome-shell crashes on lock screen

2020-06-10 Thread David Rasch

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

Ok, maybe Original Poster was seeing same bug, perhaps Ishould file
another based upon the problem I'm seeing.

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

Title:
  gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After latest focal updates, gnome-shell crashes and I lose my entire
  session when I lock the screen.

  c@slate:~$ dpkg -l | grep gnome-shell
  ii  gnome-shell3.35.91-1ubuntu2   
 amd64graphical shell for the GNOME desktop

  c@slate:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  syslog at the time of crash shows:

  Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
  Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
  Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-power[14200]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[14199]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate evolution-alarm[14258]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate update-notifier[15178]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-color[14190]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with 
result 'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management 
handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling.
  Mar  9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main 
process exited, code=dumped, status=5/TRAP
  Mar  9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken 
(explicit kill or server shutdown).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 15:49:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-08-26 (561 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago)

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

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

[Desktop-packages] [Bug 1866703] Re: gnome-shell crashes on lock screen

2020-06-10 Thread David Rasch

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

Previous bug #1866044 reports being fixed in 3.36.0-2ubuntu1

I'm seeing crashes during lock screen with 3.36.1-5ubuntu2 often it's
returning from suspend, but not sure if this is the only trigger.

after unlock, I see some window manager crash artifacts (weird window
placement) and then Gnome-shell restarts and usually recovers.

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

Title:
  gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After latest focal updates, gnome-shell crashes and I lose my entire
  session when I lock the screen.

  c@slate:~$ dpkg -l | grep gnome-shell
  ii  gnome-shell3.35.91-1ubuntu2   
 amd64graphical shell for the GNOME desktop

  c@slate:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  syslog at the time of crash shows:

  Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
  Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
  Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-power[14200]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[14199]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate evolution-alarm[14258]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate update-notifier[15178]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-color[14190]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with 
result 'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management 
handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling.
  Mar  9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main 
process exited, code=dumped, status=5/TRAP
  Mar  9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken 
(explicit kill or server shutdown).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 15:49:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-08-26 (561 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago)

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

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

[Desktop-packages] [Bug 1436640] Re: gnome-keyring chews CPU and disk for 40 seconds on chrome startup

This issue has sat incomplete for more than two years now without any
response and didn't expire due to a bug watch. This bug report only
refers to Ubuntu releases that are now "End of life" so I'm going to
close this as "Invalid".

Please feel free to re-open this bug report if this is still an issue
using a currently supported release of Ubuntu.


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

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

Title:
  gnome-keyring chews CPU and disk for 40 seconds on chrome startup

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  0) start top
  1) start chrome
  2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice 
gnome-keyring in D state; notice chrome and whole machine responding poorly 
  3) 40 seconds later, system returns to normal, and chrome beings responding 
quickly as expected.

  This is ironic and annoying, since I never use gnome's keyring.  Ever.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 19:52:44 2015
  InstallationDate: Installed on 2014-07-18 (251 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883028] [NEW] Bluetooth devices don't reconnect after sleep.

2020-06-10 Thread Adam Cz

Public bug reported:

Bluetooth devices don't reconnect after sleep. Includes BT audio
receiver and BT Keyboard.  One way to repro is to switch BT pairing on
multi-pairing keyboard, then switch back to Ubuntu.  The BT connection
state will be very confused, keyboard will not work.

Another way to repro is to get a bluetooth receiver, pair it. Let the BT
device (or PC?) sleep... now wake up the system.  The audio will not
play.  BT UI slider says disconnected.  If you click the slider it will
go back to off.  If you click it quickly >25 times, no joke, it will
reconnect and work.


FYI: Raspbian handles the keyboard fine, have not tested the audio.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
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: ubuntu:GNOME
Date: Wed Jun 10 17:09:06 2020
InstallationDate: Installed on 2019-06-10 (366 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20HRCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET61W (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 88:B1:11:77:AE:CE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:6243797 acl:69580 sco:0 events:629809 errors:0
TX bytes:488355907 acl:570780 sco:0 commands:32574 errors:0

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

Title:
  Bluetooth devices don't reconnect after sleep.

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth devices don't reconnect after sleep. Includes BT audio
  receiver and BT Keyboard.  One way to repro is to switch BT pairing on
  multi-pairing keyboard, then switch back to Ubuntu.  The BT connection
  state will be very confused, keyboard will not work.

  Another way to repro is to get a bluetooth receiver, pair it. Let the
  BT device (or PC?) sleep... now wake up the system.  The audio will
  not play.  BT UI slider says disconnected.  If you click the slider it
  will go back to off.  If you click it quickly >25 times, no joke, it
  will reconnect and work.


  FYI: Raspbian handles the keyboard fine, have not tested the audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  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: ubuntu:GNOME
  Date: Wed Jun 10 17:09:06 2020
  InstallationDate: Installed on 2019-06-10 (366 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20HRCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET61W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address:

[Desktop-packages] [Bug 1882309]

2020-06-10 Thread Jfkthame

It looks like the site there is styled with `font-size:12px` and `line-
height:11px` (and `overflow:hidden`); the exact results will depend on
the font that's used, its baseline alignment within the available line
height, etc., but having `line-height` *smaller* than `font-size` seems
like it's asking for trouble.

Having said that, I'm not seeing this on my Ubuntu 18.04 system, with
any of several possible sans-serif fonts. What font is Ubuntu 20.04
using here?

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

Title:
  Cutted off font  on Facebook in Firefox

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  The domain of site is cutted off on Facebook site as it is seen on this 
screenshot. 
  https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png
  I've seen this problem in Ubuntu 20.04 and I haven't seen in Ubuntu 19.10. 
This issue is merely in Firefox. Facebook site in Google Chrome looks ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 77.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  konrad 1159 F pulseaudio
   /dev/snd/pcmC1D0p:   konrad 1159 F...m pulseaudio
   /dev/snd/controlC0:  konrad 1159 F pulseaudio
  BuildID: 2020060727
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sat Jun  6 00:05:28 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:731
  DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-06-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.8 metric 600
  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:731
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=77.0.1/2020060727 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0V8RX3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd11/25/2019:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7250
  dmi.product.sku: 062D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

2020-06-10 Thread Vitaly

Same crap in Ubuntu 20. GNOME's OSK is useless crap, it doesn't appear
automatically when I need to type something. It only appears when you
search for applications in application's menu. Here is no button to call
OSK or run it manually, wtf?

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

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

[Desktop-packages] [Bug 1882897] Re: Suddent log off/abort in middle of session

2020-06-10 Thread Seth Arnold

** Information type changed from Public Security to Public

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

Title:
  Suddent log off/abort in middle of session

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem starts recently while I was watching some video files on
  videos. After that whenever I click on any video file it just forces
  me to log off the system and crash the work environment.

  Then after uninstalling the Videos software it was working fine. But
  now recently I installed qgis software. Again this log off problem
  starts. Whenever I try to add some plugins to qgis my system crashes
  and forces me to log off from the current session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 12:53:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
  InstallationDate: Installed on 2019-08-31 (283 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:301a Dell Computer Corp.
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp.
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 3630 Tower
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-53-generic 
root=UUID=46512e15-013e-4c05-8e5a-6b0ccc6f6d7a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0NNNCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3630 Tower
  dmi.product.sku: 0871
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

2020-06-10 Thread SchnippenSchnappen

The picture in the other issue does indeed look identical to the screen
I had however it is a very different issue.

1. I update my system daily by hand. So my system was up to date and the
fix of the other issue was installed days ago when my issue occurred.

2. The referenced bug happened after entering a password under certain
circumstances. My issue however happened without entering any password
whatsoever. I simply moved my mouse to remove fade to black and was
presented with the situation as shown in the redacted_apps.png
screenshot.

Further differences:
3. I don't have automatic lockscreen set like in the referenced issue.

4. My Keyring is unlocked automatically after boot so there was no way
that I had a dialogue active "behind" my lockscreen.

5. My lockscreen did unlock after the first time I entered my password.

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

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a very serious security issue:

  When I lock my desktop with SUPER (windows) + L my screen gets locked
  and goes to black. Sometimes when I return to my PC and move my mouse
  to turn my screen back on I notice that the Ubuntu Dock + the Top Bar
  are accessible from the lockscreen.

  I unfortunately can't remember if they were accessible from the moment
  I locked the screen or became accessible after returning from fade to
  black. (This is not the first time this issue happened.)

  I was able to open the settings menu from the top bar and use all
  indicators. You can actually start the programs in the Ubuntu Dock and
  give keyboard inputs to them. For example I was able to start the
  terminal emulator from the lock screen and run firefox and other
  applications. So an attacker could run arbitrary commands with user
  privileges from the lockscreen!

  The indicators drop down menus were fully visible on the lock screen
  while the Dock applications remained hidden "behind" the lockscreen
  (however still accessible via keyboard as described above).

  I have attached a screenshot of the bug. I unfortunately had no camera
  at hand to film me running terminal commands.

  Please contact me if you need additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 13:35:28 2020
  InstallationDate: Installed on 2015-12-22 (1627 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719

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

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

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2020-06-10 Thread ttbek

Are you guys sure it isn't Avahi?  It was still happening to me after
stopping the network manager service. Is it not the incompatibility
mentioned in the Arch docs?  https://wiki.archlinux.org/index.php/Avahi
My ip and dns finally stopped changing when I disabled Avahi.  Also
happened to this guy: https://jrs-s.net/2015/01/09/avahi-killed-my-
server/  I have a similar bridge setup to his.  Maybe my case (and that
guy's) is a different bug/issue though.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Desktop-packages] [Bug 1883015] [NEW] [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

2020-06-10 Thread Ken VanDine

Public bug reported:

[ Description ]

Update as part of the GNOME 3.36 stable release series

[ QA ]

Check you can launch the terminal and use it. Maybe check that different
themes, launching a custom command, custom terminal launchers, etc work.

There is a standing SRU exception for GNOME:

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

[ Regresison potential ]

If the update causes issues they should be pretty apparent when running
gnome-terminal.

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

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: vte2.91 (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** Affects: vte2.91 (Ubuntu Groovy)
 Importance: Undecided
 Status: New

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

** Also affects: gnome-terminal (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: vte2.91 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: gnome-terminal (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: vte2.91 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New
Status in gnome-terminal source package in Focal:
  New
Status in vte2.91 source package in Focal:
  New
Status in gnome-terminal source package in Groovy:
  New
Status in vte2.91 source package in Groovy:
  New

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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

[Desktop-packages] [Bug 1881966] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382643/+files/nmcli-dev.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

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

apport information

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

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382642/+files/nmcli-con.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

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

apport information

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

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382638/+files/PciNetwork.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382641/+files/WifiSyslog.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382633/+files/NetDevice.lo.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382631/+files/IwConfig.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382637/+files/NetworkManager.conf.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetDevice.virbr0-nic.txt

apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382635/+files/NetDevice.virbr0-nic.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04

apport information

** Tags added: apport-collected focal

** Description changed:

  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.
  
  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for
  WiFi.  Here is some information about the network.
  
  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --
  
  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--
  
  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.
  
- I am happy to provide any information necessary to resolve this issue.
- Thanks
+ I am happy to provide any information necessary to resolve this issue. Thanks
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2020-02-01 (130 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: network-manager 1.22.10-1ubuntu2.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.4.0-33-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
+  [connection]
+  wifi.powersave = 2
+ mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
+ 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

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1881966/+attachment/5382627/+files/CRDA.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04

[Desktop-packages] [Bug 1881966] IpRoute.txt

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382630/+files/IpRoute.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1881966/+attachment/5382629/+files/IpAddr.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetDevice.virbr0.txt

apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382634/+files/NetDevice.virbr0.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

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

apport information

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

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetDevice.enp3s0.txt

apport information

** Attachment added: "NetDevice.enp3s0.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382632/+files/NetDevice.enp3s0.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881966] NetDevice.wlx74ee2af4348b.txt

apport information

** Attachment added: "NetDevice.wlx74ee2af4348b.txt"
   
https://bugs.launchpad.net/bugs/1881966/+attachment/5382636/+files/NetDevice.wlx74ee2af4348b.txt

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/1881966/+subscriptions

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

[Desktop-packages] [Bug 1883013] [NEW] gnome-shell-extensions-prefs does not show any updates

2020-06-10 Thread hackel

Public bug reported:

One of the touted features of the GNOME 3.36 release was being able to
update extensions directly from the Extensions app.  This doesn't seem
to be working at all on Ubuntu 20.04, however.  I regularly receive
update notifications from the Firefox extension, but the only way I have
found to actually update them is using the old Gnome Extensions website.
I can still configure, disable, and remove extensions from the app, it
just doesn't show any updates.  Is this functionality somehow disabled
in Ubuntu?

gnome-shell-extension-prefs 3.36.2-1ubuntu1~20.04.1

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

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

Title:
  gnome-shell-extensions-prefs does not show any updates

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  One of the touted features of the GNOME 3.36 release was being able to
  update extensions directly from the Extensions app.  This doesn't seem
  to be working at all on Ubuntu 20.04, however.  I regularly receive
  update notifications from the Firefox extension, but the only way I
  have found to actually update them is using the old Gnome Extensions
  website.  I can still configure, disable, and remove extensions from
  the app, it just doesn't show any updates.  Is this functionality
  somehow disabled in Ubuntu?

  gnome-shell-extension-prefs 3.36.2-1ubuntu1~20.04.1

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

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

[Desktop-packages] [Bug 1882464] Re: menu icons in top bars exceed their boundary

** Tags added: focal

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

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

Title:
  menu icons in top bars exceed their boundary

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes the top bar icons (battery icon, wifi, sound etc...) are going out 
of their boundary at the top bar. when doing so they take over any maximized 
window top bar (e.g. browser, file explorer or any other app). By doing so it 
prevents the user from reaching the X, resize, and minimize buttons at the top 
right bar of the app. 
  Sometimes the app menu on that same top bar is exceeding as well causing the 
same problem on the left side of the screen.
  It happened several times, but i cant seem to notice what cause it...
  The problem also disappear quite easily, but the only time i noticed 
something that stopped it is when i toggled off the "application menu" option 
in "Extensions" - i.e. made any structure change in the top bar.

  I'm using ubuntu 20.04 LTS "focal fossa".
  I use a workspace indicator, and a horizontal workspace structure which i 
both toggled on from "Extensions".

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

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

[Desktop-packages] [Bug 1882464] [NEW] menu icons in top bars exceed their boundary

You have been subscribed to a public bug:

Sometimes the top bar icons (battery icon, wifi, sound etc...) are going out of 
their boundary at the top bar. when doing so they take over any maximized 
window top bar (e.g. browser, file explorer or any other app). By doing so it 
prevents the user from reaching the X, resize, and minimize buttons at the top 
right bar of the app. 
Sometimes the app menu on that same top bar is exceeding as well causing the 
same problem on the left side of the screen.
It happened several times, but i cant seem to notice what cause it...
The problem also disappear quite easily, but the only time i noticed something 
that stopped it is when i toggled off the "application menu" option in 
"Extensions" - i.e. made any structure change in the top bar.

I'm using ubuntu 20.04 LTS "focal fossa".
I use a workspace indicator, and a horizontal workspace structure which i both 
toggled on from "Extensions".

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


** Tags: focal
-- 
menu icons in top bars exceed their boundary
https://bugs.launchpad.net/bugs/1882464
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 779328] Re: kernel module ppp_generic is missing

2020-06-10 Thread Agustin Martin

For the records, I hit the same problem in Debian when trying to use
network-manager-fortisslvpn. I opened https://bugs.debian.org/962468 bug
report against Debian ppp package and proposed a patch.

** Bug watch added: Debian Bug tracker #962468
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962468

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

Title:
  kernel module ppp_generic is missing

Status in ppp package in Ubuntu:
  New

Bug description:
  Binary package hint: ppp

  When I attempt to initiate a VPN connection, I get the following
  syslog:

  May  7 23:17:11 x NetworkManager[580]:  Starting VPN service 
'pptp'...
  May  7 23:17:11 x NetworkManager[580]:  VPN service 'pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 3241
  May  7 23:17:11 x NetworkManager[580]:  VPN service 'pptp' 
appeared; activating connections
  May  7 23:17:11 x NetworkManager[580]:  VPN plugin state changed: 1
  May  7 23:17:12 x NetworkManager[580]:  VPN plugin state changed: 3
  May  7 23:17:12 x NetworkManager[580]:  VPN connection 'RCN' 
(Connect) reply received.
  May  7 23:17:12 x pppd[3243]: Plugin 
/usr/lib/pppd/2.4.5//nm-pptp-pppd-plugin.so loaded.
  May  7 23:17:12 x pppd[3243]: Couldn't open the /dev/ppp device: No such 
device or address
  May  7 23:17:17 x pppd[3243]: Please load the ppp_generic kernel module.
  May  7 23:17:17 x NetworkManager[580]:  VPN plugin state changed: 6
  May  7 23:17:17 x NetworkManager[580]:  VPN plugin state change 
reason: 0
  May  7 23:17:17 x NetworkManager[580]:  error disconnecting VPN: 
Could not process the request because no VPN connection was active.
  May  7 23:17:17 x NetworkManager[580]:  Policy set 'z' (wlan0) 
as default for IPv4 routing and DNS.
  May  7 23:17:22 x NetworkManager[580]:  VPN service 'pptp' 
disappeared

  
  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu:
  Description:Ubuntu 11.04
  Release:11.04
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ppp:
Installed: 2.4.5-5ubuntu1
Candidate: 2.4.5-5ubuntu1
Version table:
   *** 2.4.5-5ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status
  3) What you expected to happen
  I expected a VPN connection to be established
  4) What happened instead
  ppp crashed because a kernel module is missing.

  I have been Googeling for days looking for any method of acquiring
  ppp_generic or anything of the sort.  I have attempted to apt-get
  purge pptp, pppd, etc. and re-installing in hopes that a re-install
  would return the required items to no avail.  Please let me know if
  you need further information or if there is a way that I can resolve
  this as I really need to be able to VPN into my work's network;
  thanks!

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

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

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

2020-06-10 Thread adsson andre da silva gomes

Public bug reported:

This bug have been happing on my PC, in the applications when i open
some application folder and after click out of it, to close it. The
screen just freeze and i have to reboot my notebook (Lenovo-
ideapad-310).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
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: Wed Jun 10 15:08:37 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2020-06-09 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 80UH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 5A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UH:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UH
dmi.product.sku: LENOVO_MT_80UH_BU_idea_FM_Lenovo ideapad 310-15ISK
dmi.product.version: Lenovo ideapad 310-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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
 Assignee: adsson andre da silva gomes (adsson)
 Status: New


** Tags: amd64 apport-bug focal freeze ubuntu

** Attachment added: "Screenshot from 2020-06-10 15-29-03.png"
   
https://bugs.launchpad.net/bugs/1883005/+attachment/5382591/+files/Screenshot%20from%202020-06-10%2015-29-03.png

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => adsson andre da silva gomes (adsson)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug have been happing on my PC, in the applications when i open
  some application folder and after click out of it, to close it. The
  screen just freeze and i have to reboot my notebook (Lenovo-
  ideapad-310).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  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: Wed Jun 10 15:08:37 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2020-06-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 80UH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW

[Desktop-packages] [Bug 1526082] Re: Area of screenshot remains highlighted until application closed

2020-06-10 Thread teo1978

How long can it possibly take to fix this crap???

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

Title:
  Area of screenshot remains highlighted until application closed

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  - hit shift+PrintScreen
  - Drag and drop to select a rectangular area of the screen to take a 
screenshot of
  - don't close the Gnome Screenshot dialog. Minimize it if you want

  Observed issue: the rectangular area that has been captured remains
  slightly highlighted (i.e. brighter) as long as the Gnome Screenshot
  application's dialog is open. No matter what window is on the
  foreground (or even fullscreen for that matter), you'll keep noticing
  the slightly brighter rectangle.

  See attachment screenshot: you can see the rectangle approximately at
  the center of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-screenshot 3.14.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 14 23:20:01 2015
  InstallationDate: Installed on 2013-10-11 (794 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (121 days ago)

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

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

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

2020-06-10 Thread Liz Fong-Jones

I'm unable to find the channel/branch on arm64. Can you also publish an
arm64 snap in that branch?

```
$ sudo snap switch --channel=latest/candidate/vaapi chromium
"chromium" switched to the "latest/candidate/vaapi" channel
$ sudo snap refresh chromium
error: requested a non-existing branch on latest/candidate for snap "chromium":
   vaapi
$ sudo snap refresh --revision=1191 chromium
error: cannot refresh "chromium": Access by specifying a revision is not
   allowed for this Snap.
```

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

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

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

  My amdgpu can use libva

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

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

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

[Desktop-packages] [Bug 1882897] Re: Suddent log off/abort in middle of session

2020-06-10 Thread Jyotima Kanaujia

Solved already. Problem was related to Nvidia driver

Similar bug Solution at the link
https://askubuntu.com/questions/1128350/ubuntu-18-10-settings-bug

** Description changed:

  This problem starts recently while I was watching some video files on
  videos. After that whenever I click on any video file it just forces me
  to log off the system and crash the work environment.
  
  Then after uninstalling the Videos software it was working fine. But now
  recently I installed qgis software. Again this log off problem starts.
  Whenever I try to add some plugins to qgis my system crashes and forces
  me to log off from the current session.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 12:53:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
+  NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
  InstallationDate: Installed on 2019-08-31 (283 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 413c:301a Dell Computer Corp. 
-  Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. 
-  Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 413c:301a Dell Computer Corp.
+  Bus 001 Device 002: ID 413c:2107 Dell Computer Corp.
+  Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 3630 Tower
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-53-generic 
root=UUID=46512e15-013e-4c05-8e5a-6b0ccc6f6d7a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0NNNCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3630 Tower
  dmi.product.sku: 0871
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  Suddent log off/abort in middle of session

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem starts recently while I was watching some video files on
  videos. After that whenever I click on any video file it just forces
  me to log off the system and crash the work environment.

  Then after uninstalling the Videos software it was working fine. But
  now recently I installed qgis software. Again this log off problem
  starts. Whenever I try to add some plugins to qgis my system crashes
  and forces me to log off from the current session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 12:53:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GP107GL [Quadro P400]

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

2020-06-10 Thread Natalia Bidart

** Attachment added: "Attaching gpu.html"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1880710/+attachment/5382511/+files/gpu.html

-- 
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 1882988] [NEW] Links in Software updater with dark theme are difficult to read

2020-06-10 Thread Rulon Oboev

Public bug reported:

Blue color is too dark (see screenshot)

Description:Ubuntu 20.04 LTS
Release:20.04


yaru-theme-icon:
  Installed: 20.04.7
  Candidate: 20.04.7
yaru-theme-gtk:
  Installed: 20.04.7
  Candidate: 20.04.7
yaru-theme-gnome-shell:
  Installed: 20.04.7
  Candidate: 20.04.7
yaru-theme-unity:
  Installed: (none)
  Candidate: 20.04.7

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "softwareupdater.png"
   
https://bugs.launchpad.net/bugs/1882988/+attachment/5382510/+files/softwareupdater.png

** Description changed:

  Blue color is too dark (see screenshot)
+ 
+ Description:  Ubuntu 20.04 LTS
+ Release:  20.04
+ 
+ 
+ yaru-theme-icon:
+   Installed: 20.04.7
+   Candidate: 20.04.7
+ yaru-theme-gtk:
+   Installed: 20.04.7
+   Candidate: 20.04.7
+ yaru-theme-gnome-shell:
+   Installed: 20.04.7
+   Candidate: 20.04.7
+ yaru-theme-unity:
+   Installed: (none)
+   Candidate: 20.04.7

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

Title:
  Links in Software updater with dark theme are difficult to read

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Blue color is too dark (see screenshot)

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  yaru-theme-icon:
Installed: 20.04.7
Candidate: 20.04.7
  yaru-theme-gtk:
Installed: 20.04.7
Candidate: 20.04.7
  yaru-theme-gnome-shell:
Installed: 20.04.7
Candidate: 20.04.7
  yaru-theme-unity:
Installed: (none)
Candidate: 20.04.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1882988/+subscriptions

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-06-10 Thread Alex Tasin

for me the two workaround doesn't work

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1880806] Re: Gedit unable to save preferences on 20.04

2020-06-10 Thread Balazs Gyurak

Ah! I see why we have a discrepancy. I'm sorry, I was not explicit
enough with my repro steps. Following your steps, it works for me as
well.

What I am doing is the following:
- ctrl+alt+T
- $ gedit
- first line is highlighted by default
- *** open the "Ln1, Col 1" menu in the bottom right corner ***
- uncheck "Highlight current line"
- first line is NOT highlighted now
- close gedit
- in the terminal: $ gedit 
- first line is highlighted again

So, it seems that the quick menu in the bottom right corner is the one
that's not working. I do not go into the "Preferences" dialog at all.

If this doesn't help, I can do a video of the problem.

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

Title:
  Gedit unable to save preferences on 20.04

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By 
default, it came with the following:
  Display line numbers: on
  Display right margin: off
  Highlight current line: on
  Text wrapping: on

  I wanted to disable the first and third option, so I did. It works as
  long as gedit is open, but if I close and reopen it, the settings were
  reverted.

  Repro steps:
  1. Open gedit
  2. Toggle the "Highlight current line" preference
  3. Close gedit
  4. Open gedit again
  5. Observe that the "Highlight current line" preference is reverted to the 
original value

  Expected behavior
  Gedit persists preferences after closing & reopening

  Actual behavior:
  Gedit does not persist preferences after closing & reopening

  Workaround:
  Using gsettings seemed to do the trick. I've run:
  gsettings set org.gnome.gedit.preferences.editor highlight-current-line false
  gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

  This persists the settings correctly, so I believe the bug is related
  to the UI.

  Additional information:
  OS: Ubuntu 20.04
  Package: /usr/bin/gedit
  Version: 3.36.2-0ubuntu1

  Thanks,
  Balazs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 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: ubuntu:GNOME
  Date: Wed May 27 06:37:36 2020
  InstallationDate: Installed on 2018-11-05 (568 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

This bug was fixed in the package desktop-file-utils - 0.24-1ubuntu3

---
desktop-file-utils (0.24-1ubuntu3) focal; urgency=medium

  * debian/defaults.list
- Updated for the transition to snap-store (LP: #1873658)

 -- Ken VanDine   Tue, 21 Apr 2020 09:38:59
-0400

** Changed in: desktop-file-utils (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Released
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

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

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

[Desktop-packages] [Bug 1873658] Update Released

2020-06-10 Thread Brian Murray

The verification of the Stable Release Update for desktop-file-utils has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Released
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

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

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

[Desktop-packages] [Bug 1880806] Re: Gedit unable to save preferences on 20.04

Could you do a screencast/video of the issue?

Yes I just tried with a fresh ISO
- downloaded a focal desktop amd64 iso
- started it in VM on the live session
- ctrl-alt-T

$ gedit

- opened the popdown menu
- selected preferences
- unselected the checkbox for the 'highlight selected line'

verified that the first emtpy line is selected

- closed gedit
- type gedit on the command line again

gedit opens with the first line not selected

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

Title:
  Gedit unable to save preferences on 20.04

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By 
default, it came with the following:
  Display line numbers: on
  Display right margin: off
  Highlight current line: on
  Text wrapping: on

  I wanted to disable the first and third option, so I did. It works as
  long as gedit is open, but if I close and reopen it, the settings were
  reverted.

  Repro steps:
  1. Open gedit
  2. Toggle the "Highlight current line" preference
  3. Close gedit
  4. Open gedit again
  5. Observe that the "Highlight current line" preference is reverted to the 
original value

  Expected behavior
  Gedit persists preferences after closing & reopening

  Actual behavior:
  Gedit does not persist preferences after closing & reopening

  Workaround:
  Using gsettings seemed to do the trick. I've run:
  gsettings set org.gnome.gedit.preferences.editor highlight-current-line false
  gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

  This persists the settings correctly, so I believe the bug is related
  to the UI.

  Additional information:
  OS: Ubuntu 20.04
  Package: /usr/bin/gedit
  Version: 3.36.2-0ubuntu1

  Thanks,
  Balazs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 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: ubuntu:GNOME
  Date: Wed May 27 06:37:36 2020
  InstallationDate: Installed on 2018-11-05 (568 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

2020-06-10 Thread Richard Elkins

It happened to me too.  Then, I discovered that my login to my google
acct had "expired" (how does that happen?).  I logged in again and then
created a test event which got synced within one minute.

If you are looking at an Android phone/tablet that is not receiving the
event that you created on Gnome, I suggest checking calendar.google.com.
I've also had issues with my phone syncing with on-line for unknown
causes, usually just delayed.

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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

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

[Desktop-packages] [Bug 1881756] Re: SRU the current 3.36.3 stable update

Using 1:3.36.3-0ubuntu1 nautilus works correctly and verified to fix the
search focal regression reported in bug #1874972

** Tags removed: verification-needed verification-needed-focal
** Tags added: focal verification-done verification-done-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/1881756

Title:
  SRU the current 3.36.3 stable update

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-3-36/NEWS

  
  * Test case

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

  Check that browsing directories and opening, copying, etc files still
  work correctly

  
  * Regression potential

  The update has some fixes to the file search, check that it works
  correctly in the file manager as well as the desktop overview screen

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

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

[Desktop-packages] [Bug 1882966] [NEW] Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04

2020-06-10 Thread Maksym Bilak

Public bug reported:

The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
libatk-adapter packages makes it impossible to build Orca Master in
Ubuntu-MATE 20.04. Reproduction steps:

1. You need to have Ubuntu-MATE 20.04 with the latest updates;

2. Install the following packages:

git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
libatspi2.0-dev libatk-bridge2.0-dev

3. Clone the Orca repository:

git clone https://gitlab.gnome.org/GNOME/orca.git

4. Navigate to the cloned repository:

cd orca

5. Run the command:

./autogen.sh

The command output ends with the following lines:

checking for ATKBRIDGE... no
configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
Package 'atk', required by 'atk-bridge-2.0', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
forcibly downgraded to version 2.34.1-3, this error disappears.

Many thanks for fixing this issues.

** Affects: at-spi2-atk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

** Description changed:

  The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
  libatk-adapter packages makes it impossible to build Orca Master in
- Ubuntu 20.04. Reproduction steps:
+ Ubuntu-MATE 20.04. Reproduction steps:
  
  1. You need to have Ubuntu-MATE 20.04 with the latest updates;
  
  2. Install the following packages:
  
  git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
  libatspi2.0-dev libatk-bridge2.0-dev
  
  3. Clone the Orca repository:
  
  git clone https://gitlab.gnome.org/GNOME/orca.git
  
  4. Navigate to the cloned repository:
  
  cd orca
  
  5. Run the command:
  
  ./autogen.sh
  
  The command output ends with the following lines:
  
  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
  Package 'atk', required by 'atk-bridge-2.0', not found
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
  and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.
  
  If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
  forcibly downgraded to version 2.34.1-3, this error disappears.
  
  Many thanks for fixing this issues.

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

Title:
  Recent updates to some packages make it impossible to build an Orca
  Master in Ubuntu-MATE 20.04

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
  libatk-adapter packages makes it impossible to build Orca Master in
  Ubuntu-MATE 20.04. Reproduction steps:

  1. You need to have Ubuntu-MATE 20.04 with the latest updates;

  2. Install the following packages:

  git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
  libatspi2.0-dev libatk-bridge2.0-dev

  3. Clone the Orca repository:

  git clone https://gitlab.gnome.org/GNOME/orca.git

  4. Navigate to the cloned repository:

  cd orca

  5. Run the command:

  ./autogen.sh

  The command output ends with the following lines:

  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
  Package 'atk', required by 'atk-bridge-2.0', not found
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
  and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.

  If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
  forcibly downgraded to version 2.34.1-3, this error disappears.

  Many thanks for fixing this issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions

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

[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

I've tested on xubuntu now

- start a new focal xubuntu image
- download the eog focal deb from focal
- clicked on it from the file manager

-> gnome-software is opened

then after installing desktop-file-utils 0.24-1ubuntu3 trying the same steps 
gave the same result
after restarting the session is was still working as expected
the gio mime command also showed the default was still correct and 
gnome-software there

setting back to verification-done now

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

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Committed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

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

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

[Desktop-packages] [Bug 1879333] Re: [nvidia] Black screen on loading latest system update

2020-06-10 Thread mtbdrew

Issue happened again after today's system update.

The problem is causing the Nvidia device to not even been detected:

frontend@frontend:~$ lsmod | grep nvidia
frontend@frontend:~$ sudo lshw -c video | grep 'configuration'
   configuration: driver=i915 latency=0
   configuration: latency=0

After running steps listed here: https://askubuntu.com/questions/1129516
/black-screen-at-boot-after-nvidia-driver-installation-on-
ubuntu-18-04-2-lts

The card is correctly detected again:

frontend@frontend:~$ lsmod | grep nvidia
nvidia_uvm937984  0
nvidia_drm 45056  3
nvidia_modeset   1110016  6 nvidia_drm
nvidia  20422656  249 nvidia_uvm,nvidia_modeset
drm_kms_helper172032  2 nvidia_drm,i915
drm   401408  8 drm_kms_helper,nvidia_drm,i915
ipmi_msghandler53248  2 ipmi_devintf,nvidia
frontend@frontend:~$ sudo lshw -c video | grep 'configuration'
[sudo] password for frontend: 
   configuration: driver=i915 latency=0
   configuration: driver=nvidia latency=0

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

Title:
  [nvidia] Black screen on loading latest system update

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

Bug description:
  This bug has been around since 16.04 and still occurs with 18.04 when
  using nvidia drivers. When update required for the OS the black screen
  situation happens after the required reboot. Only way to regain
  desktop is to login via ssh terminal and run the commands listed here:

  https://askubuntu.com/questions/1129516/black-screen-at-boot-after-
  nvidia-driver-installation-on-ubuntu-18-04-2-lts

  sudo apt-get update

  sudo apt-get upgrade

  sudo apt-get purge nvidia*

  sudo apt autoremove

  sudo apt-get install dkms build-essential linux-headers-$(uname -r)

  echo "# Disable the default Nouveau kernel driver" | sudo tee -a
  /etc/modprobe.d/blacklist-nouveau.conf

  echo "# -" | sudo tee -a
  /etc/modprobe.d/blacklist-nouveau.conf

  echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d
  /blacklist-nouveau.conf

  echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  cat /etc/modprobe.d/blacklist-nouveau.conf

  echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d
  /nouveau-kms.conf

  cat /etc/modprobe.d/nouveau-kms.conf

  sudo update-initramfs -u

  sudo service lightdm stop

  sudo apt-get install nvidia-driver-440

  lsmod | grep nvidia

  sudo lshw -c video | grep 'configuration'

  sudo reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  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.14
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon May 18 08:44:05 2020
  DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1]
   NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a]
  InstallationDate: Installed on 2019-09-26 (234 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Desktop-packages] [Bug 1874972] Re: Nautilus search in file names shows results from full text search

The issue is fixed in this update

https://bugs.launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1

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

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

Title:
  Nautilus search in file names shows results from full text search

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Nautilus full text search works fine. However, a search in file names brings 
the same results as in full text search. The only difference is that, in the 
file name mode, no text is shown beside the file name.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: nautilus 1:3.36.1.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

This bug was fixed in the package linux-riscv - 5.4.0-27.31

---
linux-riscv (5.4.0-27.31) focal; urgency=medium

  * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798)

  * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667)
- [config] riscv: disable am-1805 RTC driver

  * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after
upgrade to 20.04 (LP: #1875665)
- [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: serial: qcserial: Add DW5816e support
- nvme: refactor nvme_identify_ns_descs error handling
- nvme: fix possible hang when ns scanning fails during error recovery
- tracing/kprobes: Fix a double initialization typo
- net: macb: Fix runtime PM refcounting
- drm/amdgpu: move kfd suspend after ip_suspend_phase1
- drm/amdgpu: drop redundant cg/pg ungate on runpm enter
- vt: fix unicode console freeing with a common interface
- tty: xilinx_uartps: Fix missing id assignment to the console
- devlink: fix return value after hitting end in region read
- dp83640: reverse arguments to list_add_tail
- fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks
- ipv6: Use global sernum for dst validation with nexthop objects
- mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly
- neigh: send protocol value in neighbor create notification
- net: dsa: Do not leave DSA master with NULL netdev_ops
- net: macb: fix an issue about leak related system resources
- net: macsec: preserve ingress frame ordering
- net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc()
- net_sched: sch_skbprio: add message validation to skbprio_change()
- net: stricter validation of untrusted gso packets
- net: tc35815: Fix phydev supported/advertising mask
- net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict()
- net/tls: Fix sk_psock refcnt leak when in tls_data_ready()
- net: usb: qmi_wwan: add support for DW5816e
- nfp: abm: fix a memory leak bug
- sch_choke: avoid potential panic in choke_reset()
- sch_sfq: validate silly quantum values
- tipc: fix partial topology connection closure
- tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040
- bnxt_en: Fix VF anti-spoof filter setup.
- bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF.
- bnxt_en: Improve AER slot reset.
- bnxt_en: Return error when allocating zero size context memory.
- bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features().
- net/mlx5: DR, On creation set CQ's arm_db member to right value
- net/mlx5: Fix forced completion access non initialized command entry
- net/mlx5: Fix command entry leak in Internal Error State
- net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx()
- net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del()
- HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices
- sctp: Fix bundling of SHUTDOWN with COOKIE-ACK
- Revert "HID: wacom: generic: read the number of expected touches on a per
  collection basis"
- HID: usbhid: Fix race between usbhid_close() and usbhid_stop()
- HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT
- USB: uas: add quirk for LaCie 2Big Quadra
- usb: chipidea: msm: Ensure proper controller reset using role switch API
- USB: serial: garmin_gps: add sanity checking for data length
- tracing: Add a vmalloc_sync_mappings() for safe measure
- crypto: arch/nhpoly1305 - process in explicit 4k chunks
- KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
- KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path
- KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER
- KVM: arm64: Fix 32bit PC wrap-around
- arm64: hugetlb: avoid potential NULL dereference
- drm: ingenic-drm: add MODULE_DEVICE_TABLE
- ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
- epoll: atomically remove wait entry on wake up
- eventpoll: fix missing wakeup for ovflist in ep_poll_callback
- mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous()
- mm: limit boost_watermark on small zones
- ceph: demote quotarealm lookup warning to a debug message
- staging: gasket: Check the return value of gasket_get_bar_index()
- coredump: fix crash when umh is disabled
- iocost: protect iocg->abs_vdebt with iocg->waitq.lock
- batman-adv: fix batadv_nc_random_weight_tq
- batman-adv: Fix refcnt leak in

[Desktop-packages] [Bug 1882849] Re: Doesn't send dhcpv6 request

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

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

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

Title:
  Doesn't send dhcpv6 request

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using network-manager 1.22.10-1ubuntu2.1 in Ubuntu Focal 20.04.
  After a connection the internal dhcp doesn't send request to dhcpv6
  server. All options in NM are default. IPv4 is ok.

  Using tcpdump I can see the packages:

  17:47:38.428145 IP6 fe80::426e:5cc5:ab6b:e126.546 > ff02::1:2.547: dhcp6 
solicit
  17:47:38.428902 IP6 fe80::20e:1eff:fe7a:9ed0.547 > 
fe80::426e:5cc5:ab6b:e126.546: dhcp6 advertise

  After dhcp6 advertise the NM doesn't send any request. After some
  seconds I can see a timeout on logs.

  NetworkManager[3803]:   [1591735670.9313] dhcp6 (eno1): request timed 
out
  NetworkManager[3803]:   [1591735670.9314] dhcp6 (eno1): state changed 
unknown -> timeout

  As man says, we can change the dhcp client. If I change
  /etc/NetworkManager/NetworkManager.conf adding

  [main]
  dhcp=dhclient 

  so everything works nice.

  I think there is some problem with the internal dhcp client of
  NetworkManager.

  Tks

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

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

[Desktop-packages] [Bug 1882958] [NEW] [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all

2020-06-10 Thread Vinicius Costa

Public bug reported:

No sound at all

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vinikir2517 F pulseaudio
 /dev/snd/pcmC0D1p:   vinikir2517 F...m pulseaudio
 /dev/snd/controlC1:  vinikir2517 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Wed Jun 10 11:20:26 2020
InstallationDate: Installed on 2020-02-06 (125 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vinikir2517 F pulseaudio
 /dev/snd/pcmC0D1p:   vinikir2517 F...m pulseaudio
 /dev/snd/controlC1:  vinikir2517 F pulseaudio
Symptom_Jack: SPDIF Out, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0810
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B250M-PLUS/BR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0810:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-PLUS/BR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

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

Title:
  [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound
  at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinikir2517 F pulseaudio
   /dev/snd/pcmC0D1p:   vinikir2517 F...m pulseaudio
   /dev/snd/controlC1:  vinikir2517 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Wed Jun 10 11:20:26 2020
  InstallationDate: Installed on 2020-02-06 (125 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinikir2517 F pulseaudio
   /dev/snd/pcmC0D1p:   vinikir2517 F...m pulseaudio
   /dev/snd/controlC1:  vinikir2517 F pulseaudio
  Symptom_Jack: SPDIF Out, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0810
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-PLUS/BR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0810:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-PLUS/BR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage

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

2020-06-10 Thread David Jeffrey

I have the same with the headset that was initially reported - the
Sennheiser HD 4.50 BTNC. A2DP works perfectly.

-- 
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 and microphone is not working (no input)
  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 1772683] Re: [snap] Cannot sign a document, gpg keys are not listed

2020-06-10 Thread Andrew Thornton

I've discovered that this bug affects the non-snap version of
libreoffice on focal too.

https://listarchives.libreoffice.org/global/users/msg54820.html suggests
that the problem is likely within the apparmor profile - and that
apparmor is preventing libreoffice from accessing .gnupg but I have not
attempted to change the profile to see if this fixes things.

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

Title:
  [snap] Cannot sign a document, gpg keys are not listed

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

Bug description:
  (initially reported on the forum: https://forum.snapcraft.io/t
  /libreoffice-snap-missing-features-and-known-bugs/3920/10)

  Libreoffice 6.0.4.2 (64, candidate channel).

  Steps to reproduce:
   1) snap run libreoffice.writer
   2) write something, then save the document (anywhere) on disk
   3) Open the File menu, then Digital Signatures > Digital Signatures…
   4) in the dialog, click "Sign Document…"

  Expected result: your GPG keys are listed

  Current result: no keys are listed

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

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

[Desktop-packages] [Bug 1882952] Re: SRU the current 0.30.10 stable version

https://bugs.launchpad.net/ubuntu/+source/shotwell/0.30.10-0ubuntu1

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

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

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

Title:
  SRU the current 0.30.10 stable version

Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The update is an upstream bugfix one, including translations updates
  and fixes to youtube's publishing

  * Test case

  Import photos, make sure than browsing and tagging works as expected

  * Regression potential

  Check that publishing content to a youtube account works correctly
  since there were fixes in the corresponding sources

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

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

[Desktop-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

** Description changed:

  * Impact
  extra roaming events are been generated
  
  * Test case
- check the output of `journalctl -lu wpa_supplicant`, it should have warnings
+ check the output of `journalctl -lu wpa_supplicant`, it shouldn't have 
warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  the roaming events should not be too frequent
  
  * Regression potential
  check that wifi connection keep working correctly
  
  --
  
  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:
  
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  Having done a little research, at least the dbus errors seem to be fixed
  by this commit upstream:
  
  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756
  
  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  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
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  * Impact
  extra roaming events are been generated
  
  * Test case
- check the output of `journalctl -lu wpa_supplicant`, it shouldn't have 
warnings
+ check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those 
warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  the roaming events should not be too frequent
  
  * Regression potential
  check that wifi connection keep working correctly
  
  --
  
  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:
  
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  Having done a little research, at least the dbus errors seem to be fixed
  by this commit upstream:
  
  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756
  
  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  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
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Incomplete

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu

[Desktop-packages] [Bug 1882799] Re: SRU the current 0.30.10 stable version

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

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

Title:
  SRU the current 0.30.10 stable version

Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The update is an upstream bugfix one, including translations updates
  and fixes to youtube's publishing

  * Test case

  Import photos, make sure than browing and tagging works as expected

  * Regression potential

  Check that publishing content to a youtube account works correctly

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

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

[Desktop-packages] [Bug 1882880] Re: FP Auth enroll screen issue: Max limit not defined

Thank you for your bug report, the fact that it's possible to enroll the
same finger is bug #1882878. If that bug is fixed then it wouldn't be
possible to enroll more than 10 fingers then it would solve that issue
as well right? In which case it's a duplicate of the other report?

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

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

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

Title:
  FP Auth enroll screen issue: Max limit not defined

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

Bug description:
  We are able to enroll FP's even after Max limit is reached (10). (No
  error like 'Max limit is reached' is observed). So we are able to
  enroll the same fingers again and again with any number of times.

  The release of Ubuntu : Ubuntu 20.04 LTS

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

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

[Desktop-packages] [Bug 1882952] [NEW] SRU the current 0.30.10 stable version

Public bug reported:

* Impact

The update is an upstream bugfix one, including translations updates and
fixes to youtube's publishing

* Test case

Import photos, make sure than browsing and tagging works as expected

* Regression potential

Check that publishing content to a youtube account works correctly since
there were fixes in the corresponding sources

** Affects: shotwell (Ubuntu)
 Importance: Low
 Status: Fix Released

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

Title:
  SRU the current 0.30.10 stable version

Status in shotwell package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The update is an upstream bugfix one, including translations updates
  and fixes to youtube's publishing

  * Test case

  Import photos, make sure than browsing and tagging works as expected

  * Regression potential

  Check that publishing content to a youtube account works correctly
  since there were fixes in the corresponding sources

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

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

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2020-06-10 Thread Salim B

> We are somewhat trapped. It's a choice between using the old version
of nautilus forever with bugs and incompatibilities, or the new version
of nautilus without desktop support. Those are not good choices but they
are all we have now. This is not a problem created by, or unique to
Ubuntu.

That seems not quite accurate. Of course, using the whole GNOME 3
desktop incl. latest Nautilus is the way to go for Ubuntu. The absence
of proper "desktop support" is unfortunate. Also sad: The current state
of the official replacement for Nautilus' desktop support, the GNOME
Shell extension "Desktop Icons", is pretty premature (still limited
keyboard support etc.).

BUT!

1. Why does Ubuntu force its users to stick with an outdated version of
the GNOME Shell extension "Desktop Icons"? Ubuntu ships the extension
via the DEB package `gnome-shell-extension-desktop-icons` which *cannot*
be removed without also removing the packages `ubuntu-desktop` and
`ubuntu-desktop-minimal`. This completely sucks. Because of the pre-
installed extension DEB package, one cannot install/update the latest
upstream version of the extension from
https://extensions.gnome.org/extension/1465/desktop-icons/

2. Why doesn't Canonical assign some of its developer ressources to
improving the "Desktop Icons" extension? This would not only benefit The
Ubuntu ecosystem but every Linux distro shipping the GNOME 3 desktop.
The sources are found here:
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons

---

For the time being, Ubuntu users can use the following workaround to get
the latest version of the "Desktop Icons" extension which already brings
limited drag-and-drop support and keyboard support:

Ensure you have 7-Zip, Git and Meson installed (e.g. via the Debian
packages `p7zip`, `git` and `meson`), then run the following in a
terminal to update the extension:

cd /usr/share/gnome-shell/extensions

# backup the DEB-packaged extension if not already done before and delete it
if [ ! -s desktop-icons_bckp.7z ] ; then sudo 7z a desktop-icons_bckp.7z
desktop-icons@csoriano/* ; fi
rm -R desktop-icons@csoriano

# build and copy the extension from git master branch
git clone g...@gitlab.gnome.org:World/ShellExtensions/desktop-icons.git
~/desktop-icons
cd ~/desktop-icons
./export-zip.sh
unzip desktop-ic...@csoriano.zip -d desktop-icons@csoriano
sudo mv desktop-icons@csoriano /usr/share/gnome-shell/extensions/

# clean up
rm -R ~/desktop-icons

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

Title:
Can no longer drag and drop files between desktop and applications

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

Bug description:
In releases before 19.04, you could drag and drop files from the
desktop into applications.

This no longer works.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-desktop-icons 19.01-1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 26 21:47:14 2019
InstallationDate: Installed on 2019-01-02 (24 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

[Desktop-packages] [Bug 1881756] Re: SRU the current 3.36.3 stable update

2020-06-10 Thread Robie Basak

Hello Sebastien, or anyone else affected,

Accepted nautilus into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nautilus (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1881756

Title:
  SRU the current 3.36.3 stable update

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-3-36/NEWS

  
  * Test case

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

  Check that browsing directories and opening, copying, etc files still
  work correctly

  
  * Regression potential

  The update has some fixes to the file search, check that it works
  correctly in the file manager as well as the desktop overview screen

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

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

[Desktop-packages] [Bug 1882878] Re: The user panel let you enroll the same finger several times

Thank you for your bug report, does it create any issue in practice or any 
buggy situation? It would probably be nicer if the UI was warning you about 
that but it seems pretty minor. I've forwarded it upstream anyway
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1023

** Summary changed:

- FP Auth enroll screen issue
+ The user panel let you enroll the same finger several times

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1023
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1023

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

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

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1023
   Importance: Unknown
   Status: Unknown

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

Title:
  The user panel let you enroll the same finger several times

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

Bug description:
  We are able to enroll the same finger for all 10 available options.
  (No error like 'Fingerprint is already enrolled' is observed). In
  windows it doesn’t allow to enroll the same finger, it has a duplicate
  check API. Here we have all 10 finger options are shown in GUI itself,
  so whichever finger is enrolled atleast the same finger can be grayed
  out so that user cannot enroll the same finger again.

  The release of Ubuntu: Ubuntu 20.04

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

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

[Desktop-packages] [Bug 1882881] Re: FP Auth login Screen issue: failed attempts

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

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

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

** This bug has been marked a duplicate of bug 1865838
no error displayed on failed fingerprint authentication

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

Title:
FP Auth login Screen issue: failed attempts

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

Bug description:
FP authentication doesn't work after 3 failed attempts.
The behavior is the same in Windows OS as well.
But in windows the GUI shows an alert like Max attempts are reached and try
to login with PIN or password.
So there is no failure report of the failed authentication for each attempt.

Ubuntu version : 20.04 LTS

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

[Desktop-packages] [Bug 1882884] Re: FP Auth : Multi user Scenario

Thank you for your bug report, the description is not really clear,

Do you mean that if you have user A and B then
- log into user A
- close the session
- auth user A with a fingepritn works

but

- log into user A
- close the session
- auth user B with a fingerprint doesn't work
?

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

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

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

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

Title:
  FP Auth : Multi user Scenario

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  FP authentication doesn't work from the login screen when there is another 
user.
  You have to login into any user with a password for first time, then we can 
use FP authentication for our next login attempts.

  Ubuntu version : 20.04 LTS

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

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

[Desktop-packages] [Bug 1880564] Proposed package upload rejected

2020-06-10 Thread Robie Basak

An upload of ubuntu-drivers-common to focal-proposed has been rejected
from the upload queue for the following reason: "Cannot review: missing
SRU information. Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Not all changes
appear to have bug references either.".

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Triaged

Bug description:
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in
  all of build-essential on upgrades (or just binutils and make and
  patch if you pass --no-install-recommends).

  This needs to be reverted and fixed differently.

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

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

[Desktop-packages] [Bug 1881586] Proposed package upload rejected

2020-06-10 Thread Robie Basak

An upload of ubuntu-drivers-common to focal-proposed has been rejected
from the upload queue for the following reason: "Cannot review: missing
SRU information. Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Not all changes
appear to have bug references either.".

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In Progress

Bug description:
  Add support for the new NVIDIA -server series to the ubuntu-drivers
  tool.

  Also add support for specifying a driver series (as already possible
  with the --gpgpu argument, for computing use cases).

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

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

[Desktop-packages] [Bug 573640] Re: mixed rtsp and http playlist does not play in totem

This issue has sat incomplete for over 5 years without any response to
comment #4. The report was raised against a very old release of Ubuntu
and did not expire due to the bug watch so I'm closing it as "Invalid".

Please feel free to re-open this bug report if this still an issue for
you.

** Changed in: totem (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  mixed rtsp and http playlist does not play in totem

Status in totem package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: totem

  Totem can not open the online radio in this link:
  http://cluster.quantumart.ru/broadcast/default.aspx?media=rusradio

  The playlist at this location contains both rtsp and http streams. The rtsp 
streams fail to play directly in any player I have tried (totem, mplayer and 
vlc).
  The rtsp stream appears first in the playlist. vlc seems to skip the streams 
it can't play, but totem just throws an error on the first stream and gives up:

  ** Message: Error: Could not read from resource.
  gstrtspsrc.c(3847): gst_rtspsrc_try_send (): 
/GstPlayBin2:play/GstURIDecodeBin:uridecodebin1/GstRTSPSrc:source:
  Could not receive message. (Timeout while waiting for server response)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Uname: Linux 2.6.31-14-generic i686
  Architecture: i386
  Date: Sun May  2 14:30:36 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  ProcEnviron:
   LANG=nl_BE.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

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

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

[Desktop-packages] [Bug 1882938] Re: Procedure for printing booklet does not state application program

2020-06-10 Thread Gunnar Hjalmarsson

Thanks for your report.

Which application do you have in mind?

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

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

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

Title:
  Procedure for printing booklet does not state application program

Status in gnome-user-docs package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.4

  
  On the Help page 
,
 the procedure for printing booklets with a single-sided printer does not tell 
the reader what program the instructions refer to. It is not possible to carry 
out the procedure without this information.

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

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

[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-10 Thread Yacine Benabderrahmane

Hi,

Since recent updates :
 - External mic (in headphones) : Working
 - Internal mic : Not Working / Not recognized

>arecord -l
 Liste des Périphériques Matériels CAPTURE 
carte 0: PCH [HDA Intel PCH], périphérique 0: ALC215 Analog [ALC215 Analog]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

>uname -a
Linux  5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

Laptop : HP EliteBook 840 G6

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

2020-06-10 Thread Slavo Roikhel

So with your tip, I disabled all my extensions until I found Dash To panel 
extension:
https://extensions.gnome.org/extension/1160/dash-to-panel/

When disabling it doesn't crash.

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

2020-06-10 Thread Slavo Roikhel

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1882938] [NEW] Procedure for printing booklet does not state application program

You have been subscribed to a public bug:

Ubuntu 18.04.4


On the Help page 
,
 the procedure for printing booklets with a single-sided printer does not tell 
the reader what program the instructions refer to. It is not possible to carry 
out the procedure without this information.

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


** Tags: documentation help
-- 
Procedure for printing booklet does not state application program 
https://bugs.launchpad.net/bugs/1882938
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1309902] Re: video image is always on top at VirtualBox with 3D

This issue has sat incomplete for more than a year without any response.
The report was raised against a release of Ubuntu that is now EOL and
did not expire due to the bug watch so I'm closing it as "Invalid".

Please feel free to re-open this bug report if this still an issue.

** Changed in: totem (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  video image is always on top at VirtualBox with 3D

Status in totem package in Ubuntu:
  Invalid

Bug description:
  
  If the "3D acceleration" from VirtualBox is activated.
  - Then is the Video image always on top. 
  - At Minimize Window is Video image still visible.
  - Menu bar is behind the video image.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Apr 19 11:35:52 2014
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

We are somewhat trapped. It's a choice between using the old version of
nautilus forever with bugs and incompatibilities, or the new version of
nautilus without desktop support. Those are not good choices but they
are all we have now. This is not a problem created by, or unique to
Ubuntu.

Indeed comment #14 links to the *official* recommended workaround.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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

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

apport information

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

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

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1882402] Re: Ubuntu-drivers allows installation of (nvidia-340) drivers, which are broken/break things (Kubuntu 20.04)

apport information

** Tags added: apport-collected focal

** Description changed:

  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.
  
  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.
  
  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34
  
  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0
  
  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)
  
  
  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "
  
  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.
  
  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?
  
  "
  root@XXX# ubuntu-drivers 
  
  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "
  
  Reproduction:
  ===
  1) ubuntu-drivers list
  
  2) which shows:
  
  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  
  "
  3) ubuntu-drivers install nvidia-340
  
  4) Reboot ==> black screen, no login screen
  
  
  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ Package: ubuntu-drivers-common 1:0.8.1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
+ Tags:  focal
+ Uname: Linux 5.4.0-37-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

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

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

2020-06-10 Thread Luca

Marcello, your workaround does indeed work because Xu and Lu flavours
use a window manager other than Mutter in Gnome. I myself had to revert
back to Unity.

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

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

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

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

apport information

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

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

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1882402] UbuntuDriversDebug.txt