from:"Roger"

If you are experiencing this bug. Try the following.

if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).

Please report the results of this test back here.

I am trying to correlate information on the part this extension is
playing in various desktop rendering glitches.

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

Title:
CPU spikes caused by saving PDF to Desktop

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

Bug description:
### Affected version

- Ubuntu 19.10
- GNOME 3.34.1
- X11

### Bug summary
Downloading a large (60MB) PDF to the desktop causes CPU spikes at regular
intervals. Was not able to reproduce when saving it elsewhere (such as
`~/Documents`)

### Steps to reproduce

[PDF](https://openstax.org/details/books/psychology?Book%20details)

This is the PDF I downloaded that presented the issue (it's a free
textbook published by OpenStax).

1. Click "Download PDF"
2. Save to the Desktop
3. Verify degraded system performance (see notes below)
4. Delete PDF
5. Verify system performance is no longer degraded

### Relevant logs, screenshots, screencasts etc.

The culprit appears to be `createThumbnail.js`. It appears to be stuck
in an infinite loop of starting and stopping a new process. This makes
it a bit difficult to monitor. The method that worked for me was to
run `top -o %CPU`, press `d`, and set the delay to something short
like `0.1`. You should see `createThumbnail` continuously flash on and
off the top of the list.

I tested saving and deleting the PDF repeatedly and there were a
couple times when it wouldn't cause the issue.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell-extension-desktop-icons 19.10.2-1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 03:02:52 2020
InstallationDate: Installed on 2020-03-04 (11 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled

If you are experiencing this bug. Try the following.

if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).

Please report the results of this test back here.

I am trying to correlate information on the part this extension is
playing in various desktop rendering glitches.

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

Title:
  gnome-shell animations are noticeably stuttery when the Ubuntu
  extensions are enabled

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

Bug description:
  I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running 
Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this 
is not always the case.
  The applications animation (the icons coming from the bottom left) is 
specially stuttery most of the time. Sometimes it is buttery smooth, but most 
of the times it is not. It is difficult to pinpoint when.

  Some exploration that may help to find the issue:
  * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much 
smoother. This seems to indicate that the problem is somehow related to the 
Intel iGPU.
  * Animations seem smoother under Wayland. But, because of other limitations, 
I am staying on Xorg for now.
  * The application animation is super stuttery the first time it is opened in 
a session. It gets slowly better with subsequent uses, although never totally 
smooth.
  " The animation is noticeably more stuttery if it opens the “All” 
applications tab instead of “Frequent” apps. Maybe the number of apps (icons) 
is a factor?
  * Vanilla gnome-session seems to be smoother. Maybe the problem is related to 
Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default 
extensions are enabled).

  These datapoints are mainly subjective as I have no means of properly
  measure animations performance.

  Don't get my wrong, 20.04 is a clear improvement over 18.04. But it
  seems there is some room for improvement at least in this hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 15:23:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-23 (780 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

If you are experiencing this bug. Try the following.

if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).

Please report the results of this test back here.

I am trying to correlate information on the part this extension is
playing in various desktop rendering glitches.

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

Title:
  Locking and unlocking the screen is slow and stuttery

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 14 10:10:38 2019
  InstallationDate: Installed on 2019-06-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049

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

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

[Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

This bug is still present in Focal. It seems to have lost focus in
upstream. In Focal it is much harder to remove the extension as it is
even more tightly linked in as a mandatory dependency for a number of
major system components. The only way to remove it is by deleting or
renaming its files.

It seems to me that this extension is responsible for numerous
performance issues. A number of bugs have been raised on different
symptoms, but all have a common factor of impacting performance and
involving this extension.

May I suggest that an umbrella bug is created and named something like
"Unacceptable Gnome shell perfomance" and marked as critical. The first
priority is to make this extension optional and disabled by default. The
process of enabling should warn of potential performance issues.

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

Title:
Desktop view flashes every time ~/Desktop changes

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

Bug description:
All of the icons on my desktop visibly flash every time I change
anything in the folder ~/Desktop, even if the change is not something
that is visible on my desktop.

For example, "touch ~/Desktop/.#foo".

I mean, the icons that haven't changed should never flash at all, even
if a change is made that _does_ affect the visible display -- only the
things that are actually new or different should change their
appearance, and everything else should remain the same and not flash.
But at the very least, there should be no flash when there are no
visible changes.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.5-1ubuntu1
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: Tue Jan 22 11:38:30 2019
InstallationDate: Installed on 2019-01-02 (20 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

[Desktop-packages] [Bug 677139] Fwd:

2020-06-13 Thread roger mateo

�� �� �� �� https://bitly.com/3ffH1ws �� �� ��


From: natopeacekeeper 

Sent: Saturday, June 13, 2020 12:39:09 PM

To: 677...@bugs.launchpad.net

Subject: 
��





http://www.bing.com/search?q=&form=FUBMECYDTFWTZQW&cvid=QCBWHHWYPBMMYFZ

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

Title:
  [Realtek ID 275] Recording problem intenal micphone , internal laptop
  speacker no not work., however when you use speacker or micphone via
  jacks external audio works.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  internal laptop micophone, internal laptop speackers do not work.
  external speackers and external micophone via jacks will work.
  this is the i386 10.04 desktop version. on sony laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  1563 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 22'
 Mixer name : 'Intel G45 DEVIBX'
 Components : 'HDA:10ec0275,104d4100,0015 
HDA:80862804,104d4100,0010'
 Controls  : 8
 Simple ctrls  : 4
  Date: Thu Nov 18 13:43:31 2010
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ID 275] Recording problem
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0270Q3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0270Q3:bd12/16/2009:svnSonyCorporation:pnVPCS111FM:pvrC103WRC4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCS111FM
  dmi.product.version: C103WRC4
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1880347] Re: Permanent pointer arrow at center of screen

2020-05-24 Thread Roger Hsu

Unfortunately, after a recent restart, the problem has returned, and my
prior trick of changing the Refresh Rate no longer fixes the problem.

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

Title:
  Permanent pointer arrow at center of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  There is a permanent pointer arrow on my screen. I have included a
  screenshot. The pointer arrow in the center of the screen is *not* my
  mouse pointer. My mouse pointer functions normally but I can't get rid
  of the pointer arrow in the center of the screen. I have not tried
  restarting the system to see if it goes away as I wanted to file this
  bug first.

  OS Name: Ubuntu 20.04 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.2
  Windowing System: X11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 23 17:07:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580/590 
[1da2:e366]
  InstallationDate: Installed on 2020-05-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 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 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2fd43526-0b59-4c37-890d-023522b1288c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.10
  dmi.board.name: AB350M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd08/30/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound

2020-05-24 Thread Roger Hsu

I have the same experience as Comment #14 - on a fresh install of 20.04
LTS, this problem randomly (at least it seems random) occurs and is
fixed by killing speech-dispatcher.

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions

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

[Desktop-packages] [Bug 1876889] Re: Jiggling Frequent/All/page buttons at low resolutions

2020-05-06 Thread Roger Light

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2758

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

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

Title:
  Jiggling Frequent/All/page buttons at low resolutions

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

Bug description:
  I installed 20.04 stock to VirtualBox and clicking the "3x3 grid of
  dots" button bottom left of the desktop brings up applications to
  chose from, but the "Frequent All" UI elements are jiggling up and
  down. This only seems to happen at 800x600.

  https://www.youtube.com/watch?v=4NIz0UCA4So

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 10:38:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1876889] [NEW] Jiggling UI elements at low resolutions

2020-05-05 Thread Roger Light

Public bug reported:

I installed 20.04 stock to VirtualBox and clicking the "3x3 grid of
dots" button bottom left of the desktop brings up applications to chose
from, but the "Frequent All" UI elements are jiggling up and down.
This only seems to happen at 800x600.

https://www.youtube.com/watch?v=4NIz0UCA4So

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May  5 10:38:05 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-05 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Jiggling UI elements at low resolutions

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I installed 20.04 stock to VirtualBox and clicking the "3x3 grid of
  dots" button bottom left of the desktop brings up applications to
  chose from, but the "Frequent All" UI elements are jiggling up and
  down. This only seems to happen at 800x600.

  https://www.youtube.com/watch?v=4NIz0UCA4So

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 10:38:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1871805] Re: --wait option not working as expected (3.28)

2020-05-04 Thread Roger

Thank you, I have just updated the description. Should I try to make the
fix and upload a debdiff which includes all libraries upgrades?


** Description changed:

+ [Impact]
+ 
+ Users are unable to launch an asynchronous gnome-terminal. In some
+ cases, a user/program/script might want to run a gnome-terminal with a
+ provided command and wait till the launched gnome-terminal exits.
+ 
+ By default, gnome-terminal runs synchronously as it uses the gnome-
+ server to handle the requests. To solve that, gnome-terminal 3.27.1
+ introduced the --wait option which solves this issue. The problem, is
+ that --wait flag does not work properly till version >= 3.36 which also
+ uses a new vte version (libvte-2.91-dev_0.60.1). Thus users cannot wait
+ for a gnome-terminal session process to finish.
+ 
+ More information: https://gitlab.gnome.org/GNOME/gnome-
+ terminal/issues/16
+ 
+ [Test Case]
+ 
+ To reproduce the bug let's assume that we want to open a gnome-terminal
+ with a provided command, for example a simple bash:
+ 
+ 1- Open a terminal:
+ 
+ gnome-terminal -- /bin/sh -c "/bin/bash"
+ 
+ This will launch gnome-terminal with a bash but the parent process in
+ the first terminal finishes just after executing the command, even if
+ the gnome-terminal is opened.
+ 
+ 2- Include the --wait option to make the command call asynchronous:
+ 
+ gnome-terminal --wait -- /bin/sh -c "/bin/bash"
+ 
+ - Now you can see int the first terminal that the processes didn't
+ finish, instead it is waiting for the launched gnome-terminal.
+ 
+ To see the explained bug try to close the opened gnome-terminal using
+ the X icon windows or File-> Close Tab. => The parent process in
+ terminal 1 does not receive the child-exited signal, thus it keeps
+ waiting forever.
+ 
+ However if we try to exit from the launched gnome-terminal by typing
+ "exit" on it, the parent process does receive the corresponding signal.
+ 
+ [Regression Potential]
+ 
+ As mentioned before, this bug was solved in gnome-terminal >= 3.36
+ Many users use the GUI options in order to finish a process, so this bug 
prevents developers to take advantage of the --wait option in its programs. 
+ 
+ The version 3.36 is included in new Ubuntu versions but not in the
+ bionic one(Ubuntu 18.04). Many users and enterprises are still using
+ Ubuntu 18.04 as the new LTS has just been released a few days ago.
+ 
+ [Other Info]
+ 
+ Initial bug report:
+ 
  Dear Maintainers,
  
  We have developed a program that it launches a new gnome-terminal with a
  ssh tunnel connection. Basically, the program forwards a local port to
  the destination address and opens a new terminal with a ssh connection
  to the local port:
  
  gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"
  
  The problem comes when we need to know when this gnome-terminal session
  has finished, in order to end the tunnel process. As you might know, the
  gnome-terminal command fires up gnome-terminal-server which it might be
  already running. Who handles the "ssh" connection is the gnome-terminal-
  server and not the gnome-terminal command, thus our program receives and
  exit code just after executing the previous command.
  
  In previous version there was the --disable-factory option, but
  unfortunately now is deprecated. Because of this type of problem it was
  added the --wait flag which was introduced in 3.27.1:
  
  gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"
  
- Nevertheless, there's a bug in this version. More information:
- https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16
+ Nevertheless, there's a bug in this version.
  
  You can reproduced by launching a new gnome-terminal with the --wait
  flag from a gnome-terminal session and try to close it via a window
  operation. In that version --wait only works if with the exit command in
  the opened session.
  
  As mentioned in the linked URL this is solved in version >= 3.36 which
  also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
  there are multiple issues referring the --disable-factory deprecated
  option, those could be closed as the new --wait option has the same
  behavior.
  
  Shall we update the libvte version used by gnome? The last libvte
  version has the proper child exit SIGNAL handler which solves the
  described issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  Architecture: amd64

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

Title:
  --wait option not working as expected (3.28)

Status in gnome-terminal package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Users are unable to launch an asynchronous gnome-terminal. In some
  cases, a user/program/script might want to run a gnome-terminal with a
  provided command and wait till the launched gnome-terminal exits.

  By

[Desktop-packages] [Bug 1871805] Re: --wait option not working as expected (3.28)

2020-04-16 Thread Roger

** Summary changed:

- Update g-t 3.36 version to solve --wait issue(bionic)
+ --wait option not working as expected (3.28)

** Description changed:

  Dear Maintainers,
  
- 
- We have developed a program that it launches a new gnome-terminal with a ssh 
tunnel connection. Basically, the program forwards a local port to the 
destination address and opens a new terminal with a ssh connection to the local 
port:
- 
+ We have developed a program that it launches a new gnome-terminal with a
+ ssh tunnel connection. Basically, the program forwards a local port to
+ the destination address and opens a new terminal with a ssh connection
+ to the local port:
  
  gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"
  
  The problem comes when we need to know when this gnome-terminal session
  has finished, in order to end the tunnel process. As you might know, the
  gnome-terminal command fires up gnome-terminal-server which it might be
  already running. Who handles the "ssh" connection is the gnome-terminal-
  server and not the gnome-terminal command, thus our program receives and
  exit code just after executing the previous command.
  
  In previous version there was the --disable-factory option, but
  unfortunately now is deprecated. Because of this type of problem it was
  added the --wait flag which was introduced in 3.27.1:
  
  gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"
  
- 
- Nevertheless, there's a bug in this version. More information: 
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16
+ Nevertheless, there's a bug in this version. More information:
+ https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16
  
  You can reproduced by launching a new gnome-terminal with the --wait
  flag from a gnome-terminal session and try to close it via a window
  operation. In that version --wait only works if with the exit command in
  the opened session.
  
  As mentioned in the linked URL this is solved in version >= 3.36 which
  also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
  there are multiple issues referring the --disable-factory deprecated
  option, those could be closed as the new --wait option has the same
  behavior.
  
- Could we update the bionic gnom-terminal 3.28 to >= 3.36 version?
+ Shall we update the libvte version used by gnome? The last libvte
+ version has the proper child exit SIGNAL handler which solves the
+ described issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  Architecture: amd64

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

Title:
  --wait option not working as expected (3.28)

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Dear Maintainers,

  We have developed a program that it launches a new gnome-terminal with
  a ssh tunnel connection. Basically, the program forwards a local port
  to the destination address and opens a new terminal with a ssh
  connection to the local port:

  gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  The problem comes when we need to know when this gnome-terminal
  session has finished, in order to end the tunnel process. As you might
  know, the gnome-terminal command fires up gnome-terminal-server which
  it might be already running. Who handles the "ssh" connection is the
  gnome-terminal-server and not the gnome-terminal command, thus our
  program receives and exit code just after executing the previous
  command.

  In previous version there was the --disable-factory option, but
  unfortunately now is deprecated. Because of this type of problem it
  was added the --wait flag which was introduced in 3.27.1:

  gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  Nevertheless, there's a bug in this version. More information:
  https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16

  You can reproduced by launching a new gnome-terminal with the --wait
  flag from a gnome-terminal session and try to close it via a window
  operation. In that version --wait only works if with the exit command
  in the opened session.

  As mentioned in the linked URL this is solved in version >= 3.36 which
  also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
  there are multiple issues referring the --disable-factory deprecated
  option, those could be closed as the new --wait option has the same
  behavior.

  Shall we update the libvte version used by gnome? The last libvte
  version has the proper child exit SIGNAL handler which solves the
  described issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  Architecture: amd64

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

-- 
Mailing list: https://launch

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-13 Thread Roger Lipscombe

See https://github.com/home-sweet-gnome/dash-to-panel/issues/959,
wherein I discover that dash-to-panel seems to be the worst offender in
terms of leaking handlers, but there's a lower-grade steady leak anyway,
which might bear looking at.

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

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-12 Thread Roger Lipscombe

> see if something's leaking registered handlers.

It looks like clutter handlers are stored in two different hash tables:
g_handlers and g_handler_list_bsa_ht.

On the PC that's really slow, g_handlers.size = 8388608 (that's ~8M); on
the PC that's not, g_handlers.size = 65536 (~65K). So, yeah, something's
leaking, afaict.

Gonna see if the hash table entries (signal_id, instance, closure) point
to anything that gives me a clue. Given that the extensions are written
mostly in JS, this is gonna be all kinds of interesting...

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-12 Thread Roger Lipscombe

This is proving to be really difficult to reproduce -- it's getting
slower (but really slowly) on my spare PC. The memory use for gnome-
shell is, essentially, static.

So: I sampled some perf data from the PC where it consistently happens
and threw up a flame graph.

It spends a bunch of time in 'clutter_actor_destroy' ->
'destroy_closure_array' -> 'handler_lookup'.

This suggests to me that some extension or other is registering a
handler for something multiple times, and not cleaning it up, which
means it takes longer and longer to iterate through the list of
handlers.

I'm gonna have a rummage through the source code to see which function
adds handlers, and then I'll attach a debugger to it to see if
something's leaking registered handlers.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1871805] Re: Update g-t 3.36 version to solve --wait issue(bionic)

2020-04-09 Thread Roger

** Tags added: upgrade-software-version

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

Title:
  Update g-t 3.36 version to solve --wait issue(bionic)

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Dear Maintainers,

  
  We have developed a program that it launches a new gnome-terminal with a ssh 
tunnel connection. Basically, the program forwards a local port to the 
destination address and opens a new terminal with a ssh connection to the local 
port:

  
  gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  The problem comes when we need to know when this gnome-terminal
  session has finished, in order to end the tunnel process. As you might
  know, the gnome-terminal command fires up gnome-terminal-server which
  it might be already running. Who handles the "ssh" connection is the
  gnome-terminal-server and not the gnome-terminal command, thus our
  program receives and exit code just after executing the previous
  command.

  In previous version there was the --disable-factory option, but
  unfortunately now is deprecated. Because of this type of problem it
  was added the --wait flag which was introduced in 3.27.1:

  gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  
  Nevertheless, there's a bug in this version. More information: 
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16

  You can reproduced by launching a new gnome-terminal with the --wait
  flag from a gnome-terminal session and try to close it via a window
  operation. In that version --wait only works if with the exit command
  in the opened session.

  As mentioned in the linked URL this is solved in version >= 3.36 which
  also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
  there are multiple issues referring the --disable-factory deprecated
  option, those could be closed as the new --wait option has the same
  behavior.

  Could we update the bionic gnom-terminal 3.28 to >= 3.36 version?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  Architecture: amd64

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

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

[Desktop-packages] [Bug 1871805] [NEW] Update g-t 3.36 version to solve --wait issue(bionic)

2020-04-09 Thread Roger

Public bug reported:

Dear Maintainers,


We have developed a program that it launches a new gnome-terminal with a ssh 
tunnel connection. Basically, the program forwards a local port to the 
destination address and opens a new terminal with a ssh connection to the local 
port:


gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

The problem comes when we need to know when this gnome-terminal session
has finished, in order to end the tunnel process. As you might know, the
gnome-terminal command fires up gnome-terminal-server which it might be
already running. Who handles the "ssh" connection is the gnome-terminal-
server and not the gnome-terminal command, thus our program receives and
exit code just after executing the previous command.

In previous version there was the --disable-factory option, but
unfortunately now is deprecated. Because of this type of problem it was
added the --wait flag which was introduced in 3.27.1:

gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"


Nevertheless, there's a bug in this version. More information: 
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16

You can reproduced by launching a new gnome-terminal with the --wait
flag from a gnome-terminal session and try to close it via a window
operation. In that version --wait only works if with the exit command in
the opened session.

As mentioned in the linked URL this is solved in version >= 3.36 which
also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
there are multiple issues referring the --disable-factory deprecated
option, those could be closed as the new --wait option has the same
behavior.

Could we update the bionic gnom-terminal 3.28 to >= 3.36 version?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.1-1ubuntu1
Architecture: amd64

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

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

Title:
  Update g-t 3.36 version to solve --wait issue(bionic)

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Dear Maintainers,

  
  We have developed a program that it launches a new gnome-terminal with a ssh 
tunnel connection. Basically, the program forwards a local port to the 
destination address and opens a new terminal with a ssh connection to the local 
port:

  
  gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  The problem comes when we need to know when this gnome-terminal
  session has finished, in order to end the tunnel process. As you might
  know, the gnome-terminal command fires up gnome-terminal-server which
  it might be already running. Who handles the "ssh" connection is the
  gnome-terminal-server and not the gnome-terminal command, thus our
  program receives and exit code just after executing the previous
  command.

  In previous version there was the --disable-factory option, but
  unfortunately now is deprecated. Because of this type of problem it
  was added the --wait flag which was introduced in 3.27.1:

  gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2"

  
  Nevertheless, there's a bug in this version. More information: 
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16

  You can reproduced by launching a new gnome-terminal with the --wait
  flag from a gnome-terminal session and try to close it via a window
  operation. In that version --wait only works if with the exit command
  in the opened session.

  As mentioned in the linked URL this is solved in version >= 3.36 which
  also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that
  there are multiple issues referring the --disable-factory deprecated
  option, those could be closed as the new --wait option has the same
  behavior.

  Could we update the bionic gnom-terminal 3.28 to >= 3.36 version?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.1-1ubuntu1
  Architecture: amd64

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

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-06 Thread Roger Lipscombe

With ALL extensions, it doesn't get slower. When it was getting slower,
I had the standard 'gnome-shell-extensions' package installed.

I'm going to reinstall it and see if that reproduces the problem.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-06 Thread Roger Lipscombe

That should say "With ALL extensions uninstalled..."

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-04-02 Thread Roger Lipscombe

Update: my spare PC is definitely getting slower at unlocking, but
(possibly because I'm not using it as much) not as quickly.

Are there any logs/debug steps you want me to run on it? I know enough
gdb to be dangerous, if that helps.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-03-30 Thread Roger Lipscombe

Some investigation and notes (and apologies for the noise; I need
somewhere to take notes):

I have the following extensions in /usr/share/gnome-shell/extensions:

alternate-...@gnome-shell-extensions.gcampax.github.com/
apps-m...@gnome-shell-extensions.gcampax.github.com/
auto-move-wind...@gnome-shell-extensions.gcampax.github.com/
dash-to-d...@micxgx.gmail.com/
dash-to-pa...@jderose9.github.com/
drive-m...@gnome-shell-extensions.gcampax.github.com/
hidetop...@mathieu.bidon.ca/
launch-new-insta...@gnome-shell-extensions.gcampax.github.com/
mediapla...@patapon.info/
move_cl...@jonathan.bluemosh.com/
multi-monitors-add-on@spin83/
native-window-placem...@gnome-shell-extensions.gcampax.github.com/
pixel-sa...@deadalnix.me/
places-m...@gnome-shell-extensions.gcampax.github.com/
screenshot-window-si...@gnome-shell-extensions.gcampax.github.com/
TaskBar@zpydr/
ubuntu-appindicat...@ubuntu.com/
ubuntu-d...@ubuntu.com/
user-th...@gnome-shell-extensions.gcampax.github.com/
window-l...@gnome-shell-extensions.gcampax.github.com/
windowsnaviga...@gnome-shell-extensions.gcampax.github.com/
workspace-indica...@gnome-shell-extensions.gcampax.github.com/

I have the following extensions installed via apt (reason, where known):

gnome-shell-extension-appindicator (ubuntu-desktop)
gnome-shell-extension-autohidetopbar (explicit)
gnome-shell-extension-dashtodock (explicit)
gnome-shell-extension-dash-to-panel (explicit)
gnome-shell-extension-mediaplayer (explicit)
gnome-shell-extension-move-clock (explicit)
gnome-shell-extension-multi-monitors (explicit)
gnome-shell-extension-pixelsaver (explicit)
gnome-shell-extensions (explicit)
gnome-shell-extension-taskbar (explicit)
gnome-shell-extension-ubuntu-dock (ubuntu-desktop)
ubuntu-session (ubuntu-desktop)

I'm trying to figure out which directory maps to which .deb package, and
then I'll remove the extensions that I'm not using. If that solves the
problem: job done.

I also have the following extensions installed in ~/.local/share/gnome-
shell/extensions:

alternate-...@gnome-shell-extensions.gcampax.github.com/
dash-to-pa...@jderose9.github.com/
multi-monitors-add-on@spin83/
audio-output-switcher@anduchs/
hidetop...@mathieu.bidon.ca/

I'm not sure what it means that I have an extension listed in both
locations.

I've removed the dashtodock and pixelsaver extensions; I wasn't using
them. I'll remove some more unused extensions if that doesn't solve the
problem.

Concurrently, I'll leave my other PC nearly stock and I'll lock/unlock
it a bunch of times over the next week or so and see if it gets slower.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-03-30 Thread Roger Lipscombe

I've also removed gnome-shell-extension-move-clock, gnome-shell-
extension-autohidetopbar and gnome-shell-extension-taskbar.

> I'm not sure what it means that I have an extension listed in both
locations.

I suspect that either I've installed it explicitly, or
extensions.gnome.org installed an update.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] Re: Unlock takes a long time

2020-03-30 Thread Roger Lipscombe

I can't do that on my primary PC -- I'm *using* those extensions.

I'll set up my spare PC the same way (with the extensions) and see if I
can repro. Then I'll disable them and see if the problem goes away (or
not).

Gonna take me about a week, though, since this only happens after a
bunch of locking and unlocking.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

[Desktop-packages] [Bug 1869568] [NEW] Unlock takes a long time

2020-03-29 Thread Roger Lipscombe

Public bug reported:

I searched and found related bugs #1774188 and #1847566, but one of
those is against 19.04, which is end-of-support, and the other was
abandoned with no feedback from the OP. So, let's try again.

When unlocking my screen, it takes progressively longer to unlock. After
a fresh restart, it's pretty quick. After about a day, it takes about a
second. After a longer period, it takes up to 5 seconds.

When I press Enter at the lock screen to get to the password entry, the
"wipe" effect commonly stalls as it gets near the top of the screen; not
sure if this is related.

After correctly entering my password, it takes several seconds before my
desktop is visible. It's _there_, because moving the mouse around
changes the mouse pointer according to what's under it (e.g. it turns
into an I-bar on the Firefox search/address box and a finger icon on a
link). It just takes several seconds to actually draw the screen.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 29 11:10:07 2020
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-01-10 (78 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+subscriptions

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

Re: [Desktop-packages] [Bug 1848014] Re: media lists users already deleted

2019-10-15 Thread Roger

I deleted them with:

sudo nautilus

went to computer, then media, then I deleted the extra non-users

However it was difficult to remove them from trash, don't remember how  
I did it.

Roger

On 2019-10-15 4:25 a.m., Sebastien Bacher wrote:
> Ok, fair enough, unsure what process should clean those entries out
> though. What command/UI did you use to delete the users?
>
> ** Changed in: udisks2 (Ubuntu)
> Status: Incomplete => New
>

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

Title:
  media lists users already deleted

Status in udisks2 package in Ubuntu:
  New

Bug description:
  directory "/media" shows entries of previously removed users

  try to enter those entries gives "Could not enter folder
  /media/rogertmp" where rogertmp user was already removed including its
  files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.firefox.rules 
70-snap.vlc.rules 70-snap.core.rules 70-snap.vidcutter.rules 
70-snap.keepassxc.rules
  Date: Mon Oct 14 08:20:43 2019
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=23de13e5-46cb-482a-a90d-e623c6bfdd4d ro elevator=noop quiet splash 
vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5109:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

Re: [Desktop-packages] [Bug 1848014] Re: media lists users already deleted

2019-10-14 Thread Roger

I don't know what issue it relates to, but the web site forced me to 
select one of the options.  Sorry if this was misleading information.

(a) I don't think the bug has any real consequences

(2) I think it was a simple oversight (part of process of deleting the 
old users files)

Roger

On 2019-10-14 9:58 a.m., Sebastien Bacher wrote:
> Thank you for your bug report. Why do you think that's an udisk issue?
> How were those mountpoint created?
>
> ** Changed in: udisks2 (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: udisks2 (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  media lists users already deleted

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  directory "/media" shows entries of previously removed users

  try to enter those entries gives "Could not enter folder
  /media/rogertmp" where rogertmp user was already removed including its
  files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.firefox.rules 
70-snap.vlc.rules 70-snap.core.rules 70-snap.vidcutter.rules 
70-snap.keepassxc.rules
  Date: Mon Oct 14 08:20:43 2019
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=23de13e5-46cb-482a-a90d-e623c6bfdd4d ro elevator=noop quiet splash 
vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5109:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1848014] [NEW] media lists users already deleted

2019-10-14 Thread Roger

Public bug reported:

directory "/media" shows entries of previously removed users

try to enter those entries gives "Could not enter folder
/media/rogertmp" where rogertmp user was already removed including its
files

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-3ubuntu0.2
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.firefox.rules 
70-snap.vlc.rules 70-snap.core.rules 70-snap.vidcutter.rules 
70-snap.keepassxc.rules
Date: Mon Oct 14 08:20:43 2019
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=23de13e5-46cb-482a-a90d-e623c6bfdd4d ro elevator=noop quiet splash 
vt.handoff=1
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5109
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5109:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic

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

Title:
  media lists users already deleted

Status in udisks2 package in Ubuntu:
  New

Bug description:
  directory "/media" shows entries of previously removed users

  try to enter those entries gives "Could not enter folder
  /media/rogertmp" where rogertmp user was already removed including its
  files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.firefox.rules 
70-snap.vlc.rules 70-snap.core.rules 70-snap.vidcutter.rules 
70-snap.keepassxc.rules
  Date: Mon Oct 14 08:20:43 2019
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=23de13e5-46cb-482a-a90d-e623c6bfdd4d ro elevator=noop quiet splash 
vt.handoff=1
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5109
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5109:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1448351] Re: Preserve job files (allow reprinting) causes UI freeze

2019-09-05 Thread Roger James

I am seeing a version of this bug in 19.04.

However, this also causes a corruption of the of the cupsd.conf file and
subsequent failure of the cups service to start/restart.

The cupsd.conf filer is overwritten with the single line.

PreserveJobFiles Yes

I think this deserves more urgency than medium.

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

Title:
  Preserve job files (allow reprinting) causes UI freeze

Status in One Hundred Papercuts:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  I can set this via dconf and I have no issues, but when I use the GUI
  to change this setting and press OK, the application freezes up and I
  have to force it to close. Happens on Ubuntu 15.04 currently, and it
  happened on 14.10 as well after some updates.

  I'm assuming it's an issue in this application and not CUPS because I
  can change it via dconf without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2
  Uname: Linux 4.0.0-04-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   E [24/Apr/2015:12:24:19 -0400] [Client 18] Local authentication certificate 
not found.
   E [24/Apr/2015:19:32:49 -0400] [Client 14] Local authentication certificate 
not found.
   E [24/Apr/2015:19:45:05 -0400] [Client 29] Local authentication certificate 
not found.
  CurrentDesktop: Unity
  Date: Fri Apr 24 19:58:36 2015
  InstallationDate: Installed on 2015-04-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire X1430
  PackageArchitecture: all
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-04-generic 
root=UUID=68234429-c890-4e23-b852-c4a62ff3282d ro quiet splash vt.handoff=7
  SourcePackage: system-config-printer
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-C1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Aspire X1430
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svnAcer:pnAspireX1430:pvr:rvnAcer:rnAspireX1430:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire X1430
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-09-02 Thread Roger

I had a major crash on mu Ubuntu Budgie system and had to reinstall
using a Ubuntu Budgie 18.04.3 iso. I used the god old ppa from Rolf
Bensch: ppa:rolfbensch/sane-git which again solved the problem on my
Canon Lide 100 scanner. Version 1.0.28 of libsane seems to do the trick.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Committed
Status in sane-backends source package in Disco:
  Fix Committed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

2019-08-20 Thread Roger James

I have now reinstalled the extension and having been running for a day
without problems. This leads me to think that this a persistent data,
rather than code related problem. I can only assume that the purge
reinstall cycle removed whatever was causing the problem.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

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

Bug description:
  After startup or login, An error occurs that just states cancel or
  report... but does not open a detail dialog

  Error messages in the syslog:

  ...
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] 
Registering 
StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  ...

  It seems that the update notifier cannot register its icon in the top
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:49:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (354 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

The extension is only fully removed if you purge it and reboot your
system.

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

Title:
  Desktop view flashes every time ~/Desktop changes

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

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  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: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

Re: [Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

Hi Jonathon,

Sorry, I wasn't clear. I really only meant the uninstall as a temporary 
test, to provide more information on what issues this extension was 
causing. For me it also solved a number of seemingly unrelated issues 
mostly to do with excessive cpu usage.

Roger

On 19 August 2019 20:35:40 Jonathan Kamens 
wrote:

> I hardly think enough research into this has been done for it to be
> obvious that this is a duplicate.
>
>
> There are literally eight app indicator icons in my system tray right
> now that disappear when I uninstall gnome-shell-extension-appindicator
> (Synology Drive, Google Hangouts, Google Chrome, Dropbox, Yubico
> Authenticator, Slack, Zoom, Flameshot), and I use them all the time.
> Uninstalling that extension simply is not an option.
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1812883
>
>
> Title:
>  Desktop view flashes every time ~/Desktop changes
>
>
> Status in gnome-shell-extension-desktop-icons:
>  New
> Status in gnome-shell-extension-desktop-icons package in Ubuntu:
>  Triaged
>
>
> Bug description:
>  All of the icons on my desktop visibly flash every time I change
>  anything in the folder ~/Desktop, even if the change is not something
>  that is visible on my desktop.
>
>
>  For example, "touch ~/Desktop/.#foo".
>
>
>  I mean, the icons that haven't changed should never flash at all, even
>  if a change is made that _does_ affect the visible display -- only the
>  things that are actually new or different should change their
>  appearance, and everything else should remain the same and not flash.
>  But at the very least, there should be no flash when there are no
>  visible changes.
>
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: nautilus 1:3.30.5-1ubuntu1
>  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: Tue Jan 22 11:38:30 2019
>  InstallationDate: Installed on 2019-01-02 (20 days ago)
>  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
>  (20181017.3)
>  SourcePackage: nautilus
>  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+subscriptions

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

Title:
  Desktop view flashes every time ~/Desktop changes

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

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  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: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces

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

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

Title:
  NetworkManager interferes with unmanaged 802.11 monitor mode
  interfaces

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  If a virtual 802.11 interface of type monitor is created on a 802.11
  physical interface that already has a virtual interface of type
  managed created on it, then the managed interface is deleted.
  NetworkManager sets the type of the monitor interface to managed. This
  can be illustrated by the following commands. All the interface names
  have been listed in /etc/network/interfaces as follows so
  NetworkManager should not be managing them in any way.

  # Disable network manager on interface names I want to use for monitoring
  # related purposes
  iface eth1 inet manual
  iface BigTenda inet manual
  iface LittleBelkin inet manual
  iface LittleTenda inet manual
  iface Sinmax inet manual
  iface mon0 inet manual
  iface phy0.mon manual
  iface phy1.mon manual
  iface phy2.mon manual
  iface phy3.mon manual
  iface phy4.mon manual
  iface phy5.mon manual
  iface phy6.mon manual
  iface phy7.mon manual
  iface phy8.mon manual
  iface phy9.mon manual

  root@dragon:/home/roger# systemctl start NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# systemctl stop NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
  root@dragon:/home/roger# iw dev
  phy#4
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor

  This stops any running or future network traces on this interface
  working.

  This is another example of network manager interfering with interfaces
  it is not supposed to be managing. See bug #1314848 which is still
  unresolved.

  The above test was carried out on Ubuntu 15.10

  network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
   *** 1.0.4-0ubuntu5.2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

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

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

[Desktop-packages] [Bug 1746232] Re: driver looping then crashing

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Invalid

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

Title:
  driver looping then crashing

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  Running driver on Artful with the xwayland compositor. At random times
  the GPU stalls with.

  Jan 30 11:22:28 dragon kernel: [  487.046219] radeon :02:00.0: ring 0 
stalled for more than 29200msec
  Jan 30 11:22:28 dragon kernel: [  487.046224] radeon :02:00.0: GPU lockup 
(current fence id 0x1bdb last fence id 0x1bdc on ring 0)

  Usually when the system is idle.

  The above message is repeated once a second for a while. This usually
  but not always terminates with a page load fault in the driver.

  System can run for a few days without this happening. But on average
  it is once or twice a day.


  
  Jan 30 11:22:30 dragon kernel: [  488.507091] BUG: unable to handle kernel 
paging request at b406c1891ffc
  Jan 30 11:22:30 dragon kernel: [  488.507176] IP: 
radeon_ring_backup+0xd3/0x140 [radeon]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-radeon 1:7.10.0-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 30 11:40:08 2018
  DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] 
[1002:9442] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-07-01 (577 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/wd-root ro
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Dec  9 13:32:35 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

[Desktop-packages] [Bug 892918] Re: Cannot start jack using qjackctrl via dbus when playback only option is needed

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

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

Title:
  Cannot start jack using qjackctrl via dbus when playback only option
  is needed

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  My audio hardware requires the playback only option to be specified to
  successfully start jackd. However I cannot start jackd with this
  option via qjackctrl unless dbus startup option is disabled. I am
  guessing that qjacktrl causes a dbus jackd with default parameters to
  be started (and stopped) before it tries to start the one with the
  playback only parameter. Starting a jackd without the playback only
  parameter always results in a server that hang and doe not respond to
  any client requests. Catch 22.

  Ubuntu 11.10
  jackd2 1.9.7~dsfg-1ubuntu2
  qjackctl 0.3.8-1

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: jackd2 1.9.7~dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Nov 21 01:32:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (36 days ago)

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

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

[Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

I think this bug may well be a duplicate of #1825623. Would anyone
object if I marked it as such.

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

Title:
  Desktop view flashes every time ~/Desktop changes

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

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  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: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

I worked round this issue by uninstalling gnome-shell-extension-
appindicator. This fixed this issue and also a number of high cpu usage
issues I was seeing. The cpu issues were sometimes severe enough to also
expose weaknesses in the compositor.

I suggest that anyone who is getting problems with gnome shell tries
this work around and reports the results back here along with the a
quick summary of the problem they were seeing.

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

Title:
  Desktop view flashes every time ~/Desktop changes

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

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  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: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

Closed bug to reduce confusion.

** This bug is no longer a duplicate of bug 1812883
   Desktop view flashes every time ~/Desktop changes

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

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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

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

[Desktop-packages] [Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

2019-07-13 Thread Roger James

I have seen a number of issues related to this error message. Including
slow wake up from sleeps. Long pauses in screen repaint. Long launch
times for applications. The only sure fix I found was to completely
purge the gnome-shell-extension-appindicator package and reboot. The
system them becomes properly responsive again. I have no idea what
visual flim flam this extension provides so I can certainly do without
it. It is a shame that it is installed by default.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

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

Bug description:
  After startup or login, An error occurs that just states cancel or
  report... but does not open a detail dialog

  Error messages in the syslog:

  ...
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] 
Registering 
StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  ...

  It seems that the update notifier cannot register its icon in the top
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:49:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (354 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

2019-07-04 Thread Roger James

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

Hi Daniel,

Sorry about the incomplete bug report. I had forgotten that I had turned
apport. I have now found a fix for the first part of my report. This has
reduced the noise level so that I can see the next part is definitely
not the same bug.

For the fist bug the relevant line from syslog is

Jul  3 21:25:06 dragon gnome-shell[8816]: JS ERROR: TypeError: fileItem
is null#012_updateDesktopIfChanged@/usr/share/gnome-shell/extensions
/desktop-
icons@csoriano/desktopManager.js:339:17#012_monitorDesktopFolder/<@/usr/share
/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89

This means that this bug is a duplicate of #1826604.

The other bug seems to be related to gdm-x-session so I raise it over
there. (After I have fixed apport!)

Roger


** This bug has been marked a duplicate of bug 1826604
   Extension causes saving files to desktop to be slow

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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

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

[Desktop-packages] [Bug 1835295] [NEW] Closing a window on the desktop freezes the desktop for a minute or more.

2019-07-03 Thread Roger James

Public bug reported:

When I close a window on the gnome desktop. The desktop often freezes
for anything between 30 seconds and a number of minutes. I notice this
most often when closing a terminal window with ctrl+d.

When look at the syslog and cpu usage (top) from a terminal logged in
via ssh I see gnome-shell running at 100% and various gnome-shell error
messages being reports. On the longer freezes the display often corrupts
and the compositor can take a number of minutes to recover.

I see that there a number of bug reports with similar problems.
Returning to the computer after a period of activity also can cause a
long delay when wakoen up by a key press (similsr to #1830255)..

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  3 20:04:23 2019
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-07-01 (1097 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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


** Tags: amd64 apport-bug disco

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  I see that there a number of bug reports with similar problems.
  Returning to the computer after a period of activity also can cause a
  long delay when wakoen up by a key press (similsr to #1830255)..

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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

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

[Desktop-packages] [Bug 211966] Re: nautilus-share report a warning about missing /var/lib/samba/usershares

2019-06-02 Thread Roger Davis

Also happens in 18.04 !!!

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

Title:
  nautilus-share report a warning about missing
  /var/lib/samba/usershares

Status in Apache2 Web Server:
  Invalid
Status in nautilus-share package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: nautilus-share

  if you start nautilus from console you can see this error message:

  Nautilus-Share-Message: Called "net usershare info" but it failed: 'net 
usershare' returned error 255: net usershare: cannot open usershare directory 
/var/lib/samba/usershares. Error Aucun fichier ou dossier de ce type
  Please ask your system administrator to enable user sharing.

  I assume it needs to create /var/lib/samba/usershares in the package

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

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

[Desktop-packages] [Bug 211966] Re: nautilus-share report a warning about missing /var/lib/samba/usershares

2019-06-02 Thread Roger Davis

Initializing nautilus-dropbox 2.10.0
Nautilus-Share-Message: 20:23:01.714: Called "net usershare info" but it 
failed: 'net usershare' returned error 255: mkdir failed on directory 
/var/run/samba/msg.lock: Permission denied
net usershare: cannot open usershare directory /var/lib/samba/usershares. Error 
No such file or directory
Please ask your system administrator to enable user sharing.

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

Title:
  nautilus-share report a warning about missing
  /var/lib/samba/usershares

Status in Apache2 Web Server:
  Invalid
Status in nautilus-share package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: nautilus-share

  if you start nautilus from console you can see this error message:

  Nautilus-Share-Message: Called "net usershare info" but it failed: 'net 
usershare' returned error 255: net usershare: cannot open usershare directory 
/var/lib/samba/usershares. Error Aucun fichier ou dossier de ce type
  Please ask your system administrator to enable user sharing.

  I assume it needs to create /var/lib/samba/usershares in the package

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

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

[Desktop-packages] [Bug 1272380] Re: Missing whitespace between generated man page refentrys

2019-04-09 Thread Roger Light

This is no longer an issue in recent Ubuntu releases.

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

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

Title:
  Missing whitespace between generated man page refentrys

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  I am generating man pages from docbook xml using xsltproc and
  /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl

  My man page contains entries like this for the "See Also" section:

 
  mosquitto
  8
  
  
  mosquitto-conf
  5
  

  When I process the man pages using xsltproc from Saucy, the resulting
  code looks like:

  \fBmosquitto\fR(8)\fBmosquitto-conf\fR(5)

  When viewed in man, this looks like "mosquitto(8)mosquitto-conf(5)" -
  with no space between the two entries.

  On Precise, the output from the same man page is:

  \fBmosquitto\fR(8)
  \fBmosquitto-conf\fR(5)

  and when viewed in man this looks like "mosquitto(8) mosquitto-
  conf(5)" as expected.

  The xml man pages and Makefile to generate the troff output can be
  found in http://mosquitto.org/files/source/mosquitto-1.2.3.tar.gz in
  the man directory.

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

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

[Desktop-packages] [Bug 1822973] [NEW] Clicking link in slack snap causes infinite loop of retrying xdg-open

2019-04-03 Thread Roger Light

Public bug reported:

First off, apologies there are lots of components this could be from, I
don't know which one.

If I click on a link in the Slack snap, nothing happens to open that
link. In the background, from what I can tell, a loop of `systemd
--user`, calling `xdg-open`, calling `kde-open5` occurs. This keeps
going. Each time I click on a link a new loop starts up and my CPU fan
starts getting louder :)

`xdg-desktop-portal` and `xdg-desktop-portal-kde` are also hanging
around but without restarting, unlike the other processes which are new
ones each time. I did have a `kde-open5` crash yesterday which is
probably related, but at the time I didn't know what had caused it.

If I `pkill kde-open5`, then all loops stop running.


Strace of `xdg-desktop-portal`, which is using a constant ~6% CPU gives a 
rapidly repeating version of the below (not useful I bet):

poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
futex(0x7f21dc7a22a8, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
futex(0x56187eb3aee0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x56187eb3aed0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
futex(0x56187eb3aee0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x56187eb3aed0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x56187eb3a228, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x56187eb3aee0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x56187eb3aed0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f21cc003ba8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 1 ([{fd=3, 
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8


Strace of `xdg-desktop-portal-kde` is a repeating

write(2128309]>, "xdp-kde-settings: ReadAll called with 
parameters:\n", 50) = 50
write(2128309]>, "xdp-kde-settings: groups:  
(\"org.kde.kdeglobals.*\")\n", 56) = 56
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}], 1, -1) = 1 ([{fd=5, 
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
write(2128309]>, "xdp-kde-settings: Read called with 
parameters:\n", 47) = 47
write(2128309]>, "xdp-kde-settings: group:  
\"org.kde.kdeglobals.General\"\n", 59) = 59
write(2128309]>, "xdp-kde-settings: key:  \"menuFont\"\n", 
39) = 39
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}], 1, -1) = 1 ([{fd=5, 
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
write(2128309]>, "xdp-kde-settings: Read called with 
parameters:\n", 47) = 47
write(2128309]>, "xdp-kde-settings: group:  
\"org.kde.kdeglobals.General\"\n", 59) = 59
write(2128309]>, "xdp-kde-settings: key:  \"font\"\n", 35) = 
35
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}], 1, -1) = 1 ([{fd=5, 
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
write(2128309]>, "xdp-kde-settings: Read called with 
parameters:\n", 47) = 47
write(2128309]>, "xdp-kde-settings: group:  
\"org.kde.kdeglobals.WM\"\n", 54) = 54
write(2128309]>, "xdp-kde-settings: key:  \"activeFont\"\n", 
41) = 41
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}], 1, -1) = 1 ([{fd=5, 
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
write(2128309]>, "xdp-kde-settings: Read called with 
parameters:\n", 47) = 47
write(2128309]>, "xdp-kde-settings: group:  
\"org.kde.kdeglobals.General\"\n", 59) = 59
write(2128309]>, "xdp-kde-settings: key:  
\"toolBarFont\"\n", 42) = 42

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xdg-utils 1.1.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr  3 09:54:04 2019
InstallationDate: Installed on 2018-10-22 (162 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to disco on 2019-03-27 (6 days ago)

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  Clicking link in slack snap causes infinite loop of retrying xdg-open

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  First off, apologies there are lots of components this could be from,
  I don't know which one.

  If I click on a link in the Slack snap, nothing happens to open that
  link. In the background, from

[Desktop-packages] [Bug 1769231] Re: wpa_cli -i flag and p2p_disabled=1 config broken

2018-10-09 Thread Roger James

The p2p-disabled flag is not supported until wpa-supplicant 2.5+.

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

Title:
  wpa_cli -i flag and p2p_disabled=1 config broken

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  When connecting to wpa_supplicant with wpa_cli -i interface command,
  the connection hangs and never completes.  This breaks various
  ifupdown integrations.

  Also, when p2p_disable=1 is set in wpa_supplicant.conf, the directive
  is not honored.

  I pulled the latest upstream hostap 2.6 source from git and built it
  using the same config file pulled from the deb source and tested to
  verify.  Oddly the bug is actually in the wpa_supplicant binary as
  starting 2.6 with the right flags allows both the 2.4 and the 2.6
  client to work correctly.  However, starting the 2.4 daemon provided
  by artful causes both wpa_cli -i connection flags to fail.

  Starting the packaged wpa_supplicant throws an odd warning as well,
  not the double prefix on the p2p-dev.

  /sbin/wpa_supplicant -B -P /run/wpa_supplicant.wlp4s0.pid -i wlp4s0 -W -D 
nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf
  Successfully initialized wpa_supplicant
  Could not read interface p2p-dev-wlp4s0 flags: No such device
  Failed to create interface p2p-dev-p2p-dev-wlp4s0: -22 (Invalid argument)
  nl80211: Failed to create a P2P Device interface p2p-dev-p2p-dev-wlp4s0
  P2P: Failed to enable P2P Device interface

  Also, in the presence of the p2p_disabled=1 flag, the 2.6 daemon
  provides the expected behavior of simply not creating the addition
  /run/wpa_supplicant/p2p-dev-wlp4s0 socket and unnamed device as seen
  by iw dev.  However, the packaged version still creates both,
  apparently leaving p2p enabled.

  root@mendota:~/code/hostap/wpa_supplicant# iw dev
  phy#0
  Unnamed/non-netdev interface
  wdev 0x5e
  addr e0:9d:31:d6:45:f3
  type P2P-device
  txpower 0.00 dBm
  Interface wlp4s0
  ifindex 3
  wdev 0x1
  addr e0:9d:31:d6:45:f2
  type managed
  txpower 22.00 dBm
  root@mendota:~/code/hostap/wpa_supplicant# ls -l /run/wpa_supplicant
  total 0
  srwxrwx--- 1 root dialout 0 May  4 12:49 p2p-dev-wlp4s0
  srwxrwx--- 1 root dialout 0 May  4 12:49 wlp4s0

  root@mendota:~/code/hostap/wpa_supplicant# wpa_cli -p /run/wpa_supplicant -i 
wlp4s0
  wpa_cli v2.4
  Copyright (c) 2004-2015, Jouni Malinen  and contributors

  This software may be distributed under the terms of the BSD license.
  See README for more details.


  Interactive mode

  Warning: Failed to attach to wpa_supplicant.
  Could not connect to wpa_supplicant: wlp4s0 - re-trying ...

  Note that 2.6 still allows a connection even when p2p_disabled is not
  set and the unnammed p2p dev and socket is created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Fri May  4 12:49:50 2018
  ProcEnviron:
   LANGUAGE=en_US
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1787645] [NEW] Most, but not all, boots from cold, I get a Low Graphics Mode error

2018-08-17 Thread Roger Davis

Public bug reported:

After an update (kernel?), I have begun to receive the message "Running
in Low Graphics Mode" at boot. I can tell it to use Default setting from
the options it offers, and get by it, after which things look and work
normally until a reboot, which may or may not occur correctly.

If I select extra graphics debug messages and display boot messages in
Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
problem begins again.

I don't know which update caused it, but it was somewhere around mid or
early May.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Aug 17 12:02:03 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
 virtualbox, 5.1.38, 4.15.0-32-generic, x86_64: installed
 virtualbox, 5.1.38, 4.4.0-133-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1502 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet plymouth:debug=1 
plymouth:debug=1=1=1=1=1 splash plymouth:debug=1=1=1=1=1=1=1=1=1 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (607 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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
xserver.bootTime: Fri Aug 17 12:00:19 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Most, but not all, boots from cold, I get a Low Graphics Mode error

Status in xorg package in Ubuntu:
  New

Bug description:
  After an update (kernel?), I have begun to receive the message
  "Running in Low Graphics Mode" at boot. I can tell it to use Default
  setting from the options it offers, and get by it, after which things
  look and work normally until a reboot, which may or may not occur
  correctly.

  If I select extra graphics debug messages and display boot messages in
  Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
  problem begins again.

  I don't know which update caused it, but it was somewhere around mid
  or early May.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 17 12:02:03 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-32-generic, x86_64: i

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-08-08 Thread Roger Davis

I can't follow the above instruction, since before that date (6/5/18) I
have turned off all options in X-Diagnose, and the system boots every
time now.

BUT :
1) The boot process is now verbose, despite turning off all options, and I 
can't change this back to quiet, which could produce the problem again.
2) Occasionally upon reboot after a new kernel is installed, the system comes 
up in Ambiance theme, where I had it in Adwatia.  To get it back is not 
straighforward, I must either reboot into straight Ubuntu (not Gnome Flashback) 
and reset it, or cycle through the options a few times until it sticks.  This 
might be a clue?

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  This problem shows up using GNOME Flashback or Unity.

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  WORKAROUND: Using x-diagnose, I selected all options under both Debug
  and Workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon May 21 01:25:13 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1785312] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned

2018-08-03 Thread Roger Peris

Public bug reported:

nan

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Aug  3 19:02:29 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-12-06 (605 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.2.27
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  nan

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Aug  3 19:02:29 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-12-06 (605 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.2.27
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-05 Thread Roger Davis

Today, with Xdiagnose unused, I again had an error message "Running in
Low Graphics Mode", after about a dozen starts with no problem.

I again engaged Xdiagnose, checked the top 3 boxes about functions, and
also engaged "Disable bootloader graphics".

Back to checking results...

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-04 Thread Roger Davis

A) Regarding your comment:
>"sudo apt-get install --install-recommends linux-generic-hwe-16.04 
>xserver-xorg-hwe-16.04"

That doesn't confirm you are booted into the HWE kernel. That only shows
that certain packages are installed (which you provided already in a
previous comment).

If you want to demonstrate what kernel is being using currently type:
uname -a
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ 

B) Regarding your comment:
>"...but now after additional other updates, and using Xdiagnose with various 
>settings, I haven't seen a boot problem for a few updates. I will continue to 
>monitor for a few days with Xdiagnose off to assure that problem is really 
>gone."

Sounds good.

B) Regarding your comment:
>"...actually causes a problem in my system. It sets and locks the theme to 
>Ambiance, even though the setting properly shows Adwaita."

Could be a bug, but that isn't the scope of this report. If you want it
fixed, you would have to file a new report.

C) Regarding your comment:
>"Please tell me before I deal with this if this is possibly something done by 
>Xdiagnose..."

Given you don't recall doing it, it was done by Xdiagnose when you
checked its checkboxes.
 Response - -
A) roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$

B) Will be checking for several days to confirm if I've just been lucky, or ???
- I'll hold off on filing a bug on Xdiagnose, I know how to fix it, and don't 
want to seem like I find too much fault.

C) ok - Sounds logical to me.

I'll continue to monitor, so please keep this bug report open for a
while.

Thanks!

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemTy

Re: [Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-04 Thread Roger Davis

I understand - thanks !!!



The reasonable man adapts himself to the world.
The unreasonable man persists in trying to adapt the world to himself.
Therefore, all progress depends on the unreasonable man.
,-._,-.
\/)"(\/
(:o:)
  (!)
 


-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 11:50 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

a) You are responding multiple times to the same comment, causing confusion. 
Hence, it is best if you looked at the bug report (not email inbox) to confirm 
if you have already responded, and use the website to respond (not send emails):
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386

It is helpful if you use the website to "Hide" the duplicate comments
(#6, #9,  and #11) so others don't get confused.

b) Regarding your comment:
>"I'll hold off on filing a bug on Xdiagnose..."

Agreed. If you are using non-default kernel parameters, a potential
response would be "don't do that". However, if you have to use them so
the scope of this report doesn't happen, that's a different story.

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology C

Re: [Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

A) roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

roger@roger-desktop:~$


B) Will be checking for several days to confirm if I've just been lucky, or ???
- I'll hold off on filing a bug on Xdiagnose, I know how to fix it, and don't 
want to seem like I find too much fault.
- Sounds logical to me.


I'll continue to monitor, so please keep this bug report open for a while.


Thanks!



-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 7:25 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

 A) Regarding your comment:
>"sudo apt-get install --install-recommends linux-generic-hwe-16.04 
>xserver-xorg-hwe-16.04"

That doesn't confirm you are booted into the HWE kernel. That only shows
that certain packages are installed (which you provided already in a
previous comment).

If you want to demonstrate what kernel is being using currently type:
uname -a

 B) Regarding your comment:
>"...but now after additional other updates, and using Xdiagnose with various 
>settings, I haven't seen a boot problem for a few updates. I will continue to 
>monitor for a few days with Xdiagnose off to assure that problem is really 
>gone."

Sounds good.

 B) Regarding your comment:
>"...actually causes a problem in my system. It sets and locks the theme to 
>Ambiance, even though the setting properly shows Adwaita."

Could be a bug, but that isn't the scope of this report. If you want it
fixed, you would have to file a new report.

 C) Regarding your comment:
>"Please tell me before I deal with this if this is possibly something done by 
>Xdiagnose..."

Given you don't recall doing it, it was done by Xdiagnose when you
checked its checkboxes.

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13u

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

In response to Christopher M. Penalver

1) same as 3 above

2) roger@roger-desktop:~$ ls -la /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 May 29 03:46 .
drwxr-xr-x 15 root root 4096 Dec 17  2016 ..
roger@roger-desktop:~$ 

3) "To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1"
- I'm not familiar with that line.  I can guess two possibilities:
- - Something very old in the system, perhaps done to deal with an earlier 
difficulty
- - Some connection with Xdiagnose, which I have been experimenting with 
previously in connection with this problem (now all settings inactivated as of 
today).

4) "If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 "
Please tell me before I deal with this if this is possibly something done by 
Xdiagnose, and how to best remove it if that seems advisable.

Thanks!

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMe

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

1) I cannot tell which update caused this.

2) Not sure how to boot to previous kernels, especially not wanting to
fowl up my settings.

3) roger@roger-desktop:~$ sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 
[sudo] password for roger: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil
  python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab
  python3-reportlab-accel python3-sip
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
roger@roger-desktop:~$ 

Or do you mean results as to boot with no problems?  - No change to that
on earlier experience, but now after additional other updates, and using
Xdiagnose with various settings, I haven't seen a boot problem for a few
updates.  I will continue to monitor for a few days to assure that
problem is really gone.

In retrospect, it appears likely to me that there was a borderline
timing problem in the boot sequence, and something in the meantime
(almost daily updates, or ???) may have changed that, or maybe I've just
been lucky the past 8 or 10 tries.  Continued watching is appropriate.

Also, the command " sudo apt-get install --install-recommends linux-
generic-hwe-16.04 xserver-xorg-hwe-16.04 "  actually causes a problem in
my system.  It sets and locks the theme to Ambiance, even though the
setting properly shows Adwaita.  It will not allow the theme to be reset
until I reboot into Unity desktop which then allows it to reset properly
to Adwaita.  I don't know if this is a bug, or just the way it works for
diagnostic purposes.  If it's just the way it works, it should be
described in the documentation along with the fix.  If it's a bug, I'll
leave it to others for now.

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

Re: [Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

1) roger@roger-desktop:~$ sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
[sudo] password for roger:
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil
  python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab
  python3-reportlab-accel python3-sip
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
roger@roger-desktop:~$
Or do you mean results as to boot with no problems?  - No change to that on 
earlier experience, but now after additional other updates, and using Xdiagnose 
with various settings, I haven't seen a boot problem for a few updates.  I will 
continue to monitor for a few days with Xdiagnose off to assure that problem is 
really gone.
In retrospect, it appears likely to me that there was a borderline timing 
problem in the boot sequence, and something in the meantime (almost daily 
updates, or ???) may have changed that, or maybe I've just been lucky the past 
8 or 10 tries.  Continued watching is appropriate.
Also, the command " sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 "  actually causes a problem in 
my system.  It sets and locks the theme to Ambiance, even though the setting 
properly shows Adwaita.  It will not allow the theme to be reset until I reboot 
into Unity desktop which then allows it to reset properly to Adwaita.  I don't 
know if this is a bug, or just the way it works for diagnostic purposes.  If 
it's just the way it works, it should be described in the documentation along 
with the fix.  If it's a bug, I'll leave it to others for now.

2) roger@roger-desktop:~$ ls -la /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 May 29 03:46 .
drwxr-xr-x 15 root root 4096 Dec 17  2016 ..
roger@roger-desktop:~$ 

3) "To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1"
- I'm not familiar with that line.  I can guess two possibilities:
- - Something very old in the system, perhaps done to deal with an earlier 
difficulty
- - Some connection with Xdiagnose, which I have been experimenting with 
previously in connection with this problem (now all settings inactivated as of 
today).

4) "If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 "
Please tell me before I deal with this if this is possibly something done by 
Xdiagnose, and how to best remove it if that seems advisable.

Thanks!


-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 5:40 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

1) To clarify, when using the upgraded HWE stack, did this influence the
reported issue "message - Low Graphics mode - about 2/3 of startups -
not all"?

2) To narrow down, could you please provide the output of the following 
terminal command (not manually attach anything found):
ls -la /var/crash

3) To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

4) If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buf

[Desktop-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all