[Desktop-packages] [Bug 1879016] [NEW] Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon

[Dan Kortschak]

Public bug reported:

Sporadically, I see loss of the Riot-Desktop (https://github.com/vector-
im/riot-web/ care of https://packages.riot.im/debian/) app indicator
icon. This appears to be associated with the following log lines from
`journalctl /usr/bin/gnome-shell`

```
May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9dec3a00), has been already finalized. Impossible to set any property to 
it.
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for context 
0x55ec9bc28340 ==
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7fbed86c9340 @ 58)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #3 0x7ffd2838df70 b   
self-hosted:916 (0x7fbf1c1f12b8 @ 367)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #4 0x7ffd2838e060 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #5 0x55ec9c0c0c88 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190
 (0x7fbed86b6f78 @ 22)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #6 0x7ffd2838f3c0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #7 0x55ec9c0c0be0 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:219
 (0x7fbed86b65e8 @ 225)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #8 0x7ffd28390720 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #9 0x55ec9c0c0b68 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/extension.js:61
 (0x7fbed8688780 @ 37)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #10 0x55ec9c0c0aa8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7fbf086592b8 @ 441)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #11 0x55ec9c0c0a28 i   
resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7fbf08659d58 @ 13)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #12 0x7ffd28391490 b   
self-hosted:251 (0x7fbf1c1c4ab0 @ 223)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #13 0x55ec9c0c09a8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7fbf08659cd0 @ 64)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #14 0x55ec9c0c0928 i   
resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7fbf08659de0 @ 87)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #15 0x7ffd28392990 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #16 0x7ffd28393130 b   
resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7fbf083704d8 @ 254)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #17 0x7ffd28394520 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #18 0x55ec9c0c07e8 i   
resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7fbf083702b8 @ 40)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #19 0x7ffd28395880 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9d075050), has been already finalized. Impossible to set any property to 
it.
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #20 0x55ec9c0c0740 i   
resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7fbf08353a28 @ 188)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #21 0x7ffd28396be0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #22 0x55ec9c0c0690 i   
resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7fbf08353ab0 @ 391)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #23 0x7ffd28397f40 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #24 0x55ec9c0c0610 i   
resource:///org/gnome/shell/ui/screenShield.js:854 (0x7fbf083519a0 @ 25)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for context 
0x55ec9bc28340 ==
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7fbed86c9340 @ 58)
May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b   
re

[Desktop-packages] [Bug 1879016] Re: Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon

[Dan Kortschak]

I have found a perfect reproducer; locking the screen (and so entering
standby) reproduces this 100% of the time.

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

Title:
  Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot
  AppIndicator icon

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

Bug description:
  Sporadically, I see loss of the Riot-Desktop (https://github.com
  /vector-im/riot-web/ care of https://packages.riot.im/debian/) app
  indicator icon. This appears to be associated with the following log
  lines from `journalctl /usr/bin/gnome-shell`

  ```
  May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9dec3a00), has been already finalized. Impossible to set any property to 
it.
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for 
context 0x55ec9bc28340 ==
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7fbed86c9340 @ 58)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #3 0x7ffd2838df70 b   
self-hosted:916 (0x7fbf1c1f12b8 @ 367)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #4 0x7ffd2838e060 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #5 0x55ec9c0c0c88 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190
 (0x7fbed86b6f78 @ 22)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #6 0x7ffd2838f3c0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #7 0x55ec9c0c0be0 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:219
 (0x7fbed86b65e8 @ 225)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #8 0x7ffd28390720 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #9 0x55ec9c0c0b68 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/extension.js:61
 (0x7fbed8688780 @ 37)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #10 0x55ec9c0c0aa8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7fbf086592b8 @ 441)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #11 0x55ec9c0c0a28 i   
resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7fbf08659d58 @ 13)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #12 0x7ffd28391490 b   
self-hosted:251 (0x7fbf1c1c4ab0 @ 223)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #13 0x55ec9c0c09a8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7fbf08659cd0 @ 64)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #14 0x55ec9c0c0928 i   
resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7fbf08659de0 @ 87)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #15 0x7ffd28392990 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #16 0x7ffd28393130 b   
resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7fbf083704d8 @ 254)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #17 0x7ffd28394520 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #18 0x55ec9c0c07e8 i   
resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7fbf083702b8 @ 40)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #19 0x7ffd28395880 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9d075050), has been already finalized. Impossible to set any property to 
it.
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #20 0x55ec9c0c0740 i   
resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7fbf08353a28 @ 188)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #21 0x7ffd28396be0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #22 0x55ec9c0c0690 i   
resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7fbf08353ab0 @ 391)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #23 0x7ffd28397f40 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #24 0x55ec9c0c0610 i   
resource:///org/gnome/shell/ui/screen

[Desktop-packages] [Bug 990377] Re: lock icon in User Accounts is at best confusing

[Dan Kortschak]

One of my hobbies is to shout into the void; bugs are my favourite.

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

Title:
  lock icon in User Accounts is at best confusing

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

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

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

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

[Desktop-packages] [Bug 1830000] [NEW] NVIDIA driver (390) does not allow progress to login screen

[Dan Kortschak]

Public bug reported:

Installing the nvidia-driver-390 package and disabling (or not) the
nouveau drivers results in a system that superficially appears to busy
hang before reaching the login screen, leaving only the fsck
"/dev/sda1: clean,..." message on the screen.

The machine is alive, and logging in remotely gives a hint at what is
happening. The output of top shows that init and systemd are struggling
with something:

```
top - 17:24:00 up 1 min,  1 user,  load average: 2.76, 1.00, 0.36
Tasks: 188 total,   2 running, 106 sleeping,   0 stopped,   0 zombie
%Cpu(s): 17.0 us, 15.2 sy,  0.0 ni, 67.6 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem : 16238012 total, 15513832 free,   242248 used,   481932 buff/cache
KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
1 root  20   0  225600   9312   6672 S  60.4  0.1   0:51.63 /sbin/init 
nosplash
  797 root  20   0   71656   7180   5296 S  26.8  0.0   0:14.92 
/lib/systemd/systemd-logind
 1133 root  20   0   46368   3584   1976 R  13.9  0.0   0:12.01 
/lib/systemd/systemd-udevd 
  795 root  20   0 1773200  30772  12548 S  13.2  0.2   0:11.71 
/usr/lib/snapd/snapd   
  784 message+  20   0   51464   6036   3988 S  12.9  0.0   0:11.15 
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 
  308 root  19  -1  249904 120460 114260 S  10.7  0.7   0:10.60 
/lib/systemd/systemd-journald  
 1132 root  20   0   46368   3584   1976 S  10.0  0.0   0:08.71 
/lib/systemd/systemd-udevd 
 1134 root  20   0   46368   3260   1656 S  10.0  0.0   0:08.61 
/lib/systemd/systemd-udevd 
  333 root  20   0   46368   4684   3084 S   5.0  0.0   0:04.25 
/lib/systemd/systemd-udevd   
```

Eventually, Xorg does manage to get a word in, but falls over, to try
again repeatedly.

```
top - 16:52:36 up 2 min,  1 user,  load average: 1.69, 1.04, 0.43
Tasks: 187 total,   2 running, 106 sleeping,   0 stopped,   0 zombie
%Cpu(s):  9.5 us,  3.7 sy,  0.0 ni, 85.6 id,  0.0 wa,  0.0 hi,  1.2 si,  0.0 st
KiB Mem : 16238012 total, 15457080 free,   278152 used,   502780 buff/cache
KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
 1821 root  20   0  312908  61228  20584 R  65.2  0.4   0:01.97 
/usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 
  806 root  20   0   71656   7200   5320 S  18.5  0.0   0:24.83 
/lib/systemd/systemd-logind
```

A further hint comes from syslog which is spammed with systemd trying to
start nvidia-persistenced, which is then killed. This happens hundreds
of times while the machine is up. This except shows one instance.

```
May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon...
May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened
May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and 
group ID 127
May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon.
May 22 16:34:52 cube nvidia-persistenced: Started (31927)
May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered
May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized
May 22 16:34:52 cube nvidia-persistenced: Received signal 15
May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon...
May 22 16:34:52 cube nvidia-persistenced: Socket closed.
May 22 16:34:52 cube nvidia-persistenced: PID file unlocked.
May 22 16:34:52 cube nvidia-persistenced: PID file closed.
May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission 
to remove its runtime data directory /var/run/nvidia-persistenced
May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927)
May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon.
```

This is a fresh install of 18.04.2 (less than an hour old). If apport
has not collected all the necessary details I'll post them after this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNI

[Desktop-packages] [Bug 1830029] [NEW] nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

[Dan Kortschak]

Public bug reported:

I am trying to use the nouveau drivers on a recent (today) install of
18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at
all.

What I am finding is that the sluggishness of the display is comparable
to the case when nouveau drivers are disabled. The only real difference
is in the amount of noise coming from the fan because of a slightly
reduced CPU load due to Xorg.

I don't even know where to start looking into this intelligently, but I
would have expected that the drivers would have gotten to a usable state
in the past 2 1/2 years since I last tried them on this machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 22 21:05:40 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540]
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
InstallationDate: Installed on 2019-05-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:066d Acer, Inc 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook P65_P67RGRERA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P65_P67RGRERA
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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

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


** Tags: amd64 apport-bug bionic performance ubuntu

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

Title:
  nouveau driver for nvidia is sluggish on GTX970M to the point of
  unusability

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to use the nouveau drivers on a recent (today) install of
  18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work
  at all.

  What I am finding is that the sluggishness of the display is
  comparable to the case when nouveau drivers are disabled. The only
  real difference is in the amount of noise coming from the fan because
  of a slightly reduced CPU load due to Xorg.

  I don't even know where to start looking into this intelligently, but
  I would have expected that the drivers would have gotten to a usable
  state in the past 2 1/2 years since I last tried them on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 22 21:05:40 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VG

[Desktop-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

[Dan Kortschak]

Removing the nomodeset kernel parameter makes GDM snappier, but it then
hangs on login (relevant portion of syslog attached).

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830029/+attachment/5265713/+files/syslog

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

Title:
  nouveau driver for nvidia is sluggish on GTX970M to the point of
  unusability

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to use the nouveau drivers on a recent (today) install of
  18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work
  at all.

  What I am finding is that the sluggishness of the display is
  comparable to the case when nouveau drivers are disabled. The only
  real difference is in the amount of noise coming from the fan because
  of a slightly reduced CPU load due to Xorg.

  I don't even know where to start looking into this intelligently, but
  I would have expected that the drivers would have gotten to a usable
  state in the past 2 1/2 years since I last tried them on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 22 21:05:40 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2019-05-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1830034] [NEW] dock obstructs desktop icons when in auto-hide mode

[Dan Kortschak]

Public bug reported:

When not in auto-hide mode, icons are shifted out of the way of the
dock. This does not happen when the dock is in auto-hide mode meaning
that when there is no window to cause it to hide, the icons at the edge
of the desktop are obscured. These icons are commonly Home, Trash and
various volumes.

Either the icons should be autplaced out of the way of the dock, or the
dock should be able to be made to auto-hide always (my preferred
solution) as well as only when a window would be obstructed.

~ $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
~ $ apt-cache policy gnome-shell-extension-ubuntu-dock 
gnome-shell-extension-ubuntu-dock:
  Installed: 0.9.1ubuntu18.04.3
  Candidate: 0.9.1ubuntu18.04.3
  Version table:
 *** 0.9.1ubuntu18.04.3 500
500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.9.1 500
500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages

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

** Attachment added: "who's-hiding.png"
   
https://bugs.launchpad.net/bugs/1830034/+attachment/5265725/+files/who%27s-hiding.png

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

Title:
  dock obstructs desktop icons when in auto-hide mode

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

Bug description:
  When not in auto-hide mode, icons are shifted out of the way of the
  dock. This does not happen when the dock is in auto-hide mode meaning
  that when there is no window to cause it to hide, the icons at the
  edge of the desktop are obscured. These icons are commonly Home, Trash
  and various volumes.

  Either the icons should be autplaced out of the way of the dock, or
  the dock should be able to be made to auto-hide always (my preferred
  solution) as well as only when a window would be obstructed.

  ~ $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  ~ $ apt-cache policy gnome-shell-extension-ubuntu-dock 
  gnome-shell-extension-ubuntu-dock:
Installed: 0.9.1ubuntu18.04.3
Candidate: 0.9.1ubuntu18.04.3
Version table:
   *** 0.9.1ubuntu18.04.3 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages

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

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

[Desktop-packages] [Bug 1711377] Re: Nautilus desktop mode should relearn handling a dock nicely in intellihide

[Dan Kortschak]

An alternative (preferable IMO, and probably simpler) is to make the
dock configurable to always hide.

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

Title:
  Nautilus desktop mode should relearn handling a dock nicely in
  intellihide

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

Bug description:
  When dock is in intellihide mode, the icons are aligned below the dock
  when visible. We should teach nautilus to take into account icon dock
  size in that mode and shift them.

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

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

[Desktop-packages] [Bug 1830444] [NEW] IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

Public bug reported:

In previous versions of Ubuntu (16.04 and before), it was possible to
specify the IPv4 method to use "Shared to other computers" directly from
the top bar (via the via the nm-connection-editor/nm-applet).

This ability is no longer available via the preferred network
configuration panel in the gnome control center, i.e. without invoking
either nm-connection-editor directly or via the nm-applet (which then
doubles up the network controls in the top bar).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:12:16 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

Image of current directly available control panel.

** Attachment added: "no-shared-to-other.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830444/+attachment/5266382/+files/no-shared-to-other.png

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

Image of nm-connection editor control, including shared to other.

** Attachment added: "with-shared-to-other.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830444/+attachment/5266383/+files/with-shared-to-other.png

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830449] [NEW] Power control panel does not provide suspend on lid close dependent on battery power

[Dan Kortschak]

Public bug reported:

In previous versions of Ubuntu (16.04) it was possible to set an
automatic suspend on laptop lid closure when the laptop was battery
powered, but not when on mains. This is no longer available; automatic
suspend provided by the power control panel is purely time-based. The
gnome tweak tool does offer a lid-based suspend trigger, but this is
independent of power source.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:33:46 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830448] [NEW] gnome shell does not respect "Photos: Do nothing" for removable media

[Dan Kortschak]

Public bug reported:

Setting "Photos: Do nothing" in the removable media panel of the gnome
control center had no effect in that inserting a removable volume with
photos/video (GoPro SD card) results in Shotwell being opened. The only
way to prevent this from happening is to check "Never prompt or start
programs on media insertion" which then prevents convenient starting of
e.g. DVD playing.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:24:20 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830449] Re: Power control panel does not provide suspend on lid close dependent on battery power

[Dan Kortschak]

** Attachment added: "automatic-suspend.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830449/+attachment/5266393/+files/automatic-suspend.png

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830448] Re: gnome shell does not respect "Photos: Do nothing" for removable media

[Dan Kortschak]

With this setting Shotwell is still started on insertion.

** Attachment added: "do-nothing-for-photos.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830448/+attachment/5266388/+files/do-nothing-for-photos.png

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830448] Re: gnome shell does not respect "Photos: Do nothing" for removable media

[Dan Kortschak]

This setting prevents Shotwell from starting, but obviously block
everything else as well.

** Attachment added: "never-do-anything.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830448/+attachment/5266389/+files/never-do-anything.png

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830449] Re: Power control panel does not provide suspend on lid close dependent on battery power

[Dan Kortschak]

** Attachment added: "lid-suspend.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830449/+attachment/5266394/+files/lid-suspend.png

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

This is part of the set up process for installation of ev3dev linux on
an EV3 robot controller (see https://www.ev3dev.org/docs/tutorials
/connecting-to-the-internet-via-usb/ scroll down to the linux
instructions).

Connection to the USB via USB is an mandatory step prior to setting up
wi-fi. This step does not work without this option.

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

[Dan Kortschak]

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

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Dan Kortschak]

Still present in 18.04.2.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

[Desktop-packages] [Bug 1780310] Re: Option 'finishings' has value '3' and cannot be edited

[Dan Kortschak]

Still affecting 18.04. Also note that upstream does not have an issue
tracker anymore, losing the linked issue above.

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

Title:
  Option 'finishings' has value '3' and cannot be edited

Status in System Config Printer:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Whenever I open the print queue for my local printer, I get a dialog
  box with the message:

  Option 'finishings' has value '3' and cannot be edited

  I can dismiss the dialog box and everything seems to work normally,
  but it is annoying.  However, it's possible that some obscure printer
  feature does not work for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: system-config-printer 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 12:30:50 2018
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2018-07-03 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  Lpstat: device for Ricoh-Aficio-MP-C3500: 
lpd://hqnvprint02.nvidia.com/secureprint
  MachineType: ASUS X299-A
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=d418cc23-14fc-41cf-b75f-29644c2a16be ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnASUS:pnX299-A:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X299-A
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1780310/+subscriptions

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

[Desktop-packages] [Bug 1834554] [NEW] Screen displays dynamic corruptions

[Dan Kortschak]

Public bug reported:

Regularly the screen displays corruptions that change depending on disk
i/o, keyboard/mouse and other system activity. The screen corruptions do
not appear on each session and can be removed by selecting an
alternative resolution and then changing back (or reverting without
accepting the change).

The location of the corruptions is stereotypical and always has the same
shape characteristics.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-24-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun 28 12:14:17 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed
 nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801]
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fc]
InstallationDate: Installed on 2019-06-25 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic 
root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE V2
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.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

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


** Tags: amd64 apport-bug bionic corruption ubuntu

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

Title:
  Screen displays dynamic corruptions

Status in xorg package in Ubuntu:
  New

Bug description:
  Regularly the screen displays corruptions that change depending on
  disk i/o, keyboard/mouse and other system activity. The screen
  corruptions do not appear on each session and can be removed by
  selecting an alternative resolution and then changing back (or
  reverting without accepting the change).

  The location of the corruptions is stereotypical and always has the
  same shape characteristics.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname

[Desktop-packages] [Bug 1834554] Re: Screen displays dynamic corruptions

[Dan Kortschak]

Screen shots of the corruption do not work as the screen shot tool
appears to overwrite the corruption. Video capture does work.

** Attachment added: "Video capture of screen corruption"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv

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

Title:
  Screen displays dynamic corruptions

Status in xorg package in Ubuntu:
  New

Bug description:
  Regularly the screen displays corruptions that change depending on
  disk i/o, keyboard/mouse and other system activity. The screen
  corruptions do not appear on each session and can be removed by
  selecting an alternative resolution and then changing back (or
  reverting without accepting the change).

  The location of the corruptions is stereotypical and always has the
  same shape characteristics.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun 28 12:14:17 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed
   nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801]
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fc]
  InstallationDate: Installed on 2019-06-25 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic 
root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  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.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1834554] Re: [nvidia] Screen displays dynamic corruptions

[Dan Kortschak]

Yeah, I considered that and I guess it's a possibility, but if it's the
case it's only exercised by the 18.04 X code, this has never appeared
prior to the installation of 18.04 a couple of days ago (was previously
running 16.04). I don't recall seeing it while running the live usb
either, but I can check that when I'm back at the machine.

The other things that makes me feel like it's a software issue is the
interdependence of the effect and other activity on the system as
mentioned: typing changes the cadence of the updates as does disk i/o; I
would not expect that behaviour if it were graphics card RAM failure. It
almost feels like someone is writing a buffer in an incorrect location,
but the allocation of the screen memory changes with resolution change
and this can randomly choose somewhere that's not being abused like that
(random stab in the dark).

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

Title:
  [nvidia] Screen displays dynamic corruptions

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

Bug description:
  Regularly the screen displays corruptions that change depending on
  disk i/o, keyboard/mouse and other system activity. The screen
  corruptions do not appear on each session and can be removed by
  selecting an alternative resolution and then changing back (or
  reverting without accepting the change).

  The location of the corruptions is stereotypical and always has the
  same shape characteristics.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun 28 12:14:17 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed
   nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801]
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fc]
  InstallationDate: Installed on 2019-06-25 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic 
root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  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.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version

[Desktop-packages] [Bug 1024768] Re: [xorg-edgers] Missing icons in unity launcher and app switcher after update

[Dan Kortschak]

This or a similar bug is still sporadically affecting me. As for Hamil,
no obvious cause, no recent upgrade. The only path to fix is to reatart
the machine (is this an approach to fix Bug 1 by immitation?).

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

Title:
  [xorg-edgers] Missing icons in unity launcher and app switcher after
  update

Status in Unity:
  Invalid
Status in “mesa” package in Ubuntu:
  Fix Released

Bug description:
  After about 2 weeks I updated my 12.04 64b Ubuntu and after restart
  mentioned icons are missing, see screenshot [1]. I tried "unity
  --replace" and even "unity --reset" but no luck. I can provide more
  information if needed (at least until I'll give up and reinstall
  ubuntu). I'm using the default unity (3d ?)

  OS: Ubuntu 12.04 LTS 64b
  unity:
Installed: 5.12-0ubuntu1.1
Candidate: 5.12-0ubuntu1.1
Version table:
   *** 5.12-0ubuntu1.1 0
  500 http://cz.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.10.0-0ubuntu6 0
  500 http://cz.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  [1] https://docs.google.com/open?id=0B6Sd5ov8j7IUaEtuSXRaTHdmbDA

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Jul 14 20:14:45 2012
  DistUpgraded: 2012-05-06 17:03:39,172 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20e4]
 Subsystem: Lenovo Device [17aa:20e4]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  MachineType: LENOVO 744332G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic 
root=UUID=db34f35f-de70-4ca0-8577-1ef5590b414a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-06 (69 days ago)
  dmi.bios.date: 10/02/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VET80WW (3.10 )
  dmi.board.name: 744332G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VET80WW(3.10):bd10/02/2009:svnLENOVO:pn744332G:pvrThinkPadR400:rvnLENOVO:rn744332G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 744332G
  dmi.product.version: ThinkPad R400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.37+git20120713.992e2afd-0ubuntu0ricotz~precise
  version.libgl1-mesa-dri: libgl1-mesa-dri 
8.1~git20120712.fe911c1d-0ubuntu0sarvatt3~precise
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
8.1~git20120712.fe911c1d-0ubuntu0sarvatt3~precise
  version.xserver-xorg-core: xserver-xorg-core 
2:1.12.3+git20120709+server-1.12-branch.60e0d205-0ubuntu0ricotz~precise
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.7.0+git20120504.f28507e8-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99+git20120711.ef8a4043-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0+git20120711.b5db90aa-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1+git20120711.d1bc38b6-0ubuntu0sarvatt~precise

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

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

[Desktop-packages] [Bug 1024768] Re: [xorg-edgers] Missing icons in unity launcher and app switcher after update

[Dan Kortschak]

And equally unexplicably, mine has gone again. How on earth can this be
tagged as fixed. If LTS does not mean fixes are released for it, what
does LTS actually mean. Without a launcher, what is the point of unity?

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

Title:
  [xorg-edgers] Missing icons in unity launcher and app switcher after
  update

Status in Unity:
  Invalid
Status in “mesa” package in Ubuntu:
  Fix Released

Bug description:
  After about 2 weeks I updated my 12.04 64b Ubuntu and after restart
  mentioned icons are missing, see screenshot [1]. I tried "unity
  --replace" and even "unity --reset" but no luck. I can provide more
  information if needed (at least until I'll give up and reinstall
  ubuntu). I'm using the default unity (3d ?)

  OS: Ubuntu 12.04 LTS 64b
  unity:
Installed: 5.12-0ubuntu1.1
Candidate: 5.12-0ubuntu1.1
Version table:
   *** 5.12-0ubuntu1.1 0
  500 http://cz.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.10.0-0ubuntu6 0
  500 http://cz.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  [1] https://docs.google.com/open?id=0B6Sd5ov8j7IUaEtuSXRaTHdmbDA

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Jul 14 20:14:45 2012
  DistUpgraded: 2012-05-06 17:03:39,172 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20e4]
 Subsystem: Lenovo Device [17aa:20e4]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  MachineType: LENOVO 744332G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic 
root=UUID=db34f35f-de70-4ca0-8577-1ef5590b414a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-06 (69 days ago)
  dmi.bios.date: 10/02/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VET80WW (3.10 )
  dmi.board.name: 744332G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VET80WW(3.10):bd10/02/2009:svnLENOVO:pn744332G:pvrThinkPadR400:rvnLENOVO:rn744332G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 744332G
  dmi.product.version: ThinkPad R400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.37+git20120713.992e2afd-0ubuntu0ricotz~precise
  version.libgl1-mesa-dri: libgl1-mesa-dri 
8.1~git20120712.fe911c1d-0ubuntu0sarvatt3~precise
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
8.1~git20120712.fe911c1d-0ubuntu0sarvatt3~precise
  version.xserver-xorg-core: xserver-xorg-core 
2:1.12.3+git20120709+server-1.12-branch.60e0d205-0ubuntu0ricotz~precise
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.7.0+git20120504.f28507e8-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99+git20120711.ef8a4043-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0+git20120711.b5db90aa-0ubuntu0sarvatt~precise
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1+git20120711.d1bc38b6-0ubuntu0sarvatt~precise

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

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

[Desktop-packages] [Bug 1075360] [NEW] list view jumps to arbitrary location after deleting email(s)

[Dan Kortschak]

Public bug reported:

Deleting and email causes the list view to jump to an arbitrary location
in the list (a sane email is selected and displayed in the preview, but
its subject line etc is not visible in the email list). Requiring
navigation back to the desired point in the subject list view.

This occurs when deleting one or many emails and when deletion is by
menu or delete key.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: evolution 3.2.3-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Tue Nov  6 10:08:29 2012
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to precise on 2012-09-20 (46 days ago)

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


** Tags: amd64 apport-bug precise running-unity third-party-packages

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

Title:
  list view jumps to arbitrary location after deleting email(s)

Status in “evolution” package in Ubuntu:
  New

Bug description:
  Deleting and email causes the list view to jump to an arbitrary
  location in the list (a sane email is selected and displayed in the
  preview, but its subject line etc is not visible in the email list).
  Requiring navigation back to the desired point in the subject list
  view.

  This occurs when deleting one or many emails and when deletion is by
  menu or delete key.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evolution 3.2.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Nov  6 10:08:29 2012
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to precise on 2012-09-20 (46 days ago)

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

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

[Desktop-packages] [Bug 669465] Re: Evolution's e-addressbook-factory process renders CPU usage 100%

[Dan Kortschak]

I'm seeing something very similar, though entirely different (sorry).

e-addressbook-server occasionally starts thrashing on my hard drive with
low CPU and memory use (~5% and 25MB RES respectively). Appart from
being noisy, this impact on actually useful disk-intensive applications.

$ lsb_release -r
Release:12.04

$ apt-cache policy evolution-data-server
evolution-data-server:
  Installed: 3.2.3-0ubuntu7
  Candidate: 3.2.3-0ubuntu7
  Version table:
 *** 3.2.3-0ubuntu7 0
500 http://mirror.aarnet.edu.au/pub/ubuntu/archive/ 
precise-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.2.3-0ubuntu6 0
500 http://mirror.aarnet.edu.au/pub/ubuntu/archive/ precise/main amd64 
Packages

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

Title:
  Evolution's e-addressbook-factory process renders CPU usage 100%

Status in Evolution Data Server:
  New
Status in “evolution-data-server” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: evolution-data-server

  I have set-up Evolution email client to access my Gmail and UbuntuOne
  address books. However, on some occasions e-addressbook-factory starts
  using 100% of CPU. It has happened to me more than ten times, but I
  still cannot tell what exactly causes the book to occur. It may be
  something with Gmail address book and UbuntuOne address book accessed
  at the same time. BTW, this bug seems to occur more often after Ubuntu
  resumes from suspend. Killing the process, apparently, helps, as it is
  restarted and works normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: evolution-data-server 2.30.3-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Nov  1 16:06:27 2010
  ExecutablePath: /usr/lib/evolution/e-addressbook-factory
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: evolution-data-server

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/669465/+subscriptions

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

[Desktop-packages] [Bug 1018263] [NEW] exhaustive memory leak

[Dan Kortschak]

Public bug reported:

If I leave firefox running over night, since upgrading to 13.0.1
Firefox, firefox exhausts all system memory, running with 100% load on
one core. This has been noticed on other platforms by other users (for
example here http://support.mozilla.org/en-US/questions/930472).

Action:
Leave firefox running and go home from work.

Expect:
Low load and low memory use from firefox when get back in the morning.

See:
100% load on one core due to ff, and full memory (in this case 12GB) exhaustion 
(or worse OOM killer marks on other long running applications, including but 
not limited to compiz).

Extra points:
I have small multiples of tabs open, but nothing actually doing anything and 
not that had caused any problems prior to this version.

It seems ff13.0.1 could give NT a run for it's money if it were in the
airlines stakes ;|

$ lsb_release -rd
Description:Ubuntu 10.04.4 LTS
Release:10.04

$ dpkg -l | grep firefox
ii  firefox  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla
ii  firefox-3.0  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
ii  firefox-3.0-branding 
3.6.10+build1+nobinonly-0ubuntu0.9.10.1   dummy upgrade package for 
firefox-3.0 -> firefox-3.5
ii  firefox-3.0-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
ii  firefox-branding 
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
ii  firefox-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - GNOME support

$ uname -srvm
Linux 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51 UTC 2012 x86_64

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

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

Title:
  exhaustive memory leak

Status in “firefox” package in Ubuntu:
  New

Bug description:
  If I leave firefox running over night, since upgrading to 13.0.1
  Firefox, firefox exhausts all system memory, running with 100% load on
  one core. This has been noticed on other platforms by other users (for
  example here http://support.mozilla.org/en-US/questions/930472).

  Action:
  Leave firefox running and go home from work.

  Expect:
  Low load and low memory use from firefox when get back in the morning.

  See:
  100% load on one core due to ff, and full memory (in this case 12GB) 
exhaustion (or worse OOM killer marks on other long running applications, 
including but not limited to compiz).

  Extra points:
  I have small multiples of tabs open, but nothing actually doing anything and 
not that had caused any problems prior to this version.

  It seems ff13.0.1 could give NT a run for it's money if it were in the
  airlines stakes ;|

  $ lsb_release -rd
  Description:Ubuntu 10.04.4 LTS
  Release:10.04

  $ dpkg -l | grep firefox
  ii  firefox  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla
  ii  firefox-3.0  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-3.0-branding 
3.6.10+build1+nobinonly-0ubuntu0.9.10.1   dummy upgrade package for 
firefox-3.0 -> firefox-3.5
  ii  firefox-3.0-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-branding 
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - GNOME support

  $ uname -srvm
  Linux 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51 UTC 2012 x86_64

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

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

[Desktop-packages] [Bug 1018263] Re: exhaustive memory leak

[Dan Kortschak]

My apologies - my clarity goes away when long running development tests
are crashed by another, unrelated, application.

I'll set up a VM and try to replicate the situation there.

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

Title:
  exhaustive memory leak

Status in “firefox” package in Ubuntu:
  Invalid

Bug description:
  If I leave firefox running over night, since upgrading to 13.0.1
  Firefox, firefox exhausts all system memory, running with 100% load on
  one core. This has been noticed on other platforms by other users (for
  example here http://support.mozilla.org/en-US/questions/930472).

  Action:
  Leave firefox running and go home from work.

  Expect:
  Low load and low memory use from firefox when get back in the morning.

  See:
  100% load on one core due to ff, and full memory (in this case 12GB) 
exhaustion (or worse OOM killer marks on other long running applications, 
including but not limited to compiz).

  Extra points:
  I have small multiples of tabs open, but nothing actually doing anything and 
not that had caused any problems prior to this version.

  It seems ff13.0.1 could give NT a run for it's money if it were in the
  airlines stakes ;|

  $ lsb_release -rd
  Description:Ubuntu 10.04.4 LTS
  Release:10.04

  $ dpkg -l | grep firefox
  ii  firefox  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla
  ii  firefox-3.0  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-3.0-branding 
3.6.10+build1+nobinonly-0ubuntu0.9.10.1   dummy upgrade package for 
firefox-3.0 -> firefox-3.5
  ii  firefox-3.0-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-branding 
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - GNOME support

  $ uname -srvm
  Linux 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51 UTC 2012 x86_64

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

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

[Desktop-packages] [Bug 1019094] [NEW] exhaustive fatal memory leak

[Dan Kortschak]

Public bug reported:

This is a resubmission of bug 1018263 required for bug submission via
apport (I won't repeat comments here as this is submitted from a VM).

As explained in the last comment of that submission. It was not possible
to trigger apport on crash while following the apport wiki instrauction,
so the best I can do is collect apport data on firefox.

It does not appear to be possible to start apport with firefox in safe
mode, and ubuntu-bug incorrectly claims that firefox has been upgraded
since started and so refuses to submit if I pass --safe-mode to firefox.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: firefox 13.0.1+build1-0ubuntu0.10.04.1
ProcVersionSignature: Ubuntu 2.6.32-41.91-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1370/1 [ES1370 DAC2/ADC]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  daniel 1202 F pulseaudio
BuildID: 20120615040410
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1370 at 0xc100, irq 11'
   Mixer name   : 'Asahi Kasei AK4531'
   Components   : 'AK4531'
   Controls  : 43
   Simple ctrls  : 15
Channel: release
CurrentDmesg:
 [8.885322] ppdev: user-space parallel port driver
 [9.270375] JBD: barrier-based sync failed on vda1-8 - disabling barriers
 [   18.664039] eth0: no IPv6 routers present
Date: Fri Jun 29 10:14:53 2012
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
IpRoute:
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.3  metric 1 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 default via 192.168.0.1 dev eth0  proto static
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Plugins:
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-plugins)
 Windows Media Player Plug-in 10 (compatible; Totem) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
 VLC Multimedia Plugin (compatible Totem 2.30.2) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
 QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
 DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615040410 (In use)
RelatedPackageVersions:
 rhythmbox-plugins 0.12.8-0ubuntu7
 totem-mozilla 2.30.2-0ubuntu1
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

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


** Tags: apport-bug i386 lucid release-channel

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

Title:
  exhaustive fatal memory leak

Status in “firefox” package in Ubuntu:
  New

Bug description:
  This is a resubmission of bug 1018263 required for bug submission via
  apport (I won't repeat comments here as this is submitted from a VM).

  As explained in the last comment of that submission. It was not
  possible to trigger apport on crash while following the apport wiki
  instrauction, so the best I can do is collect apport data on firefox.

  It does not appear to be possible to start apport with firefox in safe
  mode, and ubuntu-bug incorrectly claims that firefox has been upgraded
  since started and so refuses to submit if I pass --safe-mode to
  firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 13.0.1+build1-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-41.91-generic 2.6.32.59+drm33.24
  Uname: Linux 2.6.32-41-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1370/1 [ES1370 DAC2/ADC]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1202 F pulseaudio
  BuildID: 20120615040410
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1370 at 0xc100

[Desktop-packages] [Bug 1018263] Re: exhaustive memory leak

[Dan Kortschak]

Replicated with fresh (but upgraded to current state) 32 and 64 lucid
instances - on both VMs firefox was started in safe-mode.

As per the apport wiki https://wiki.ubuntu.com/Apport/:

I executed `sudo service apport start force_start=1' prior to firefox
launch. However apport was not started, so I *cannot* provide the
information that is required to submit a valid bug. Nor is it possible
to examine about:memory as firefox is not longer with us.

The best I can do is collect apport information on one of the VM
instances - bug 1019094.

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

Title:
  exhaustive memory leak

Status in “firefox” package in Ubuntu:
  Invalid

Bug description:
  If I leave firefox running over night, since upgrading to 13.0.1
  Firefox, firefox exhausts all system memory, running with 100% load on
  one core. This has been noticed on other platforms by other users (for
  example here http://support.mozilla.org/en-US/questions/930472).

  Action:
  Leave firefox running and go home from work.

  Expect:
  Low load and low memory use from firefox when get back in the morning.

  See:
  100% load on one core due to ff, and full memory (in this case 12GB) 
exhaustion (or worse OOM killer marks on other long running applications, 
including but not limited to compiz).

  Extra points:
  I have small multiples of tabs open, but nothing actually doing anything and 
not that had caused any problems prior to this version.

  It seems ff13.0.1 could give NT a run for it's money if it were in the
  airlines stakes ;|

  $ lsb_release -rd
  Description:Ubuntu 10.04.4 LTS
  Release:10.04

  $ dpkg -l | grep firefox
  ii  firefox  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla
  ii  firefox-3.0  
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-3.0-branding 
3.6.10+build1+nobinonly-0ubuntu0.9.10.1   dummy upgrade package for 
firefox-3.0 -> firefox-3.5
  ii  firefox-3.0-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-branding 
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - transitional package
  ii  firefox-gnome-support
13.0.1+build1-0ubuntu0.10.04.1Safe and easy web browser 
from Mozilla - GNOME support

  $ uname -srvm
  Linux 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51 UTC 2012 x86_64

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

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

[Desktop-packages] [Bug 1019094] Re: exhaustive fatal memory leak

[Dan Kortschak]

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

Title:
  exhaustive fatal memory leak

Status in “firefox” package in Ubuntu:
  New

Bug description:
  This is a resubmission of bug 1018263 required for bug submission via
  apport (I won't repeat comments here as this is submitted from a VM).

  As explained in the last comment of that submission. It was not
  possible to trigger apport on crash while following the apport wiki
  instrauction, so the best I can do is collect apport data on firefox.

  It does not appear to be possible to start apport with firefox in safe
  mode, and ubuntu-bug incorrectly claims that firefox has been upgraded
  since started and so refuses to submit if I pass --safe-mode to
  firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 13.0.1+build1-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-41.91-generic 2.6.32.59+drm33.24
  Uname: Linux 2.6.32-41-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1370/1 [ES1370 DAC2/ADC]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 1202 F pulseaudio
  BuildID: 20120615040410
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1370 at 0xc100, irq 11'
 Mixer name : 'Asahi Kasei AK4531'
 Components : 'AK4531'
 Controls  : 43
 Simple ctrls  : 15
  Channel: release
  CurrentDmesg:
   [8.885322] ppdev: user-space parallel port driver
   [9.270375] JBD: barrier-based sync failed on vda1-8 - disabling barriers
   [   18.664039] eth0: no IPv6 routers present
  Date: Fri Jun 29 10:14:53 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  IpRoute:
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.3  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   default via 192.168.0.1 dev eth0  proto static
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-plugins)
   Windows Media Player Plug-in 10 (compatible; Totem) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Totem 2.30.2) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615040410 (In use)
  RelatedPackageVersions:
   rhythmbox-plugins 0.12.8-0ubuntu7
   totem-mozilla 2.30.2-0ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
  dmi.product.name: Bochs
  dmi.sys.vendor: Bochs

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

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

[Desktop-packages] [Bug 990377] Re: lock icon in User Accounts is at best confusing

[Dan Kortschak]

Submitted to GNOME Bugzilla as Bug 676912:
https://bugzilla.gnome.org/show_bug.cgi?id=676912

** Bug watch added: GNOME Bug Tracker #676912
   https://bugzilla.gnome.org/show_bug.cgi?id=676912

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

Title:
  lock icon in User Accounts is at best confusing

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

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

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

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

[Desktop-packages] [Bug 990377] [NEW] lock icon in User Accounts is at best confusing

[Dan Kortschak]

Public bug reported:

This is a UI issue.

Description:Ubuntu 12.04 LTS
Release:12.04

The lock/unlock button in User Accounts goes against the normal use of a
lock to indicate the locked state, instead meaning the action of
locking. This makes the icon confusing. A better approach would be to
use the commonly used convention, and not have the lock in the button.

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

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

Title:
  lock icon in User Accounts is at best confusing

Status in “gnome-system-tools” package in Ubuntu:
  New

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

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

-- 
Mailing list: https://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 990377] Re: lock icon in User Accounts is at best confusing

[Dan Kortschak]

On Sat, 2012-04-28 at 12:53 +, Milan Bouchet-Valat wrote:
> What's the "normal use"? This button is standard as it's provided by
> GTK.
> 
Normal use would be the generally accepted and widely used metaphor -
that a closed lock means 'locked', 'safe', 'secure' etc. This is how it
has been used for almost the past decade by browsers to indicate that an
encrypted connection is being used, how the Mac OS uses it in the same
context as in User Accounts, and even how real world objects use the
metaphor (attached - a picture of a baby safety lock showing a closed
lock indicating locked and an open lock indicating unlocked).

I'm not entirely surprised that GTK gives this little bit of insanity,
but Ubuntu devs should be able to improve on it.


** Attachment added: "real-world-example.jpg"
   
https://bugs.launchpad.net/bugs/990377/+attachment/3113910/+files/real-world-example.jpg

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

Title:
  lock icon in User Accounts is at best confusing

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

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

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

[Desktop-packages] [Bug 993878] [NEW] there is no tab for access to file notes in the properties dialog

[Dan Kortschak]

Public bug reported:

The Notes tab of the properties dialog has gone away some time between
Lucid and Precise. The decoration indicating a note exists is still
present suggesting the feature has not been intentionally dropped.
Further examination shows that emblems have also disappeared (this
appears to be intentional http://ubuntuguide.net/add-emblems-to-
nautilus-files-folders-in-ubuntu-12-04-11-10 and is no great loss).

I would expect the notes tabs to be present in the properties dialog or
some other obvious way to read already existing notes (and preferably be
able to edit them).

$ lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
$ dpkg -l nautilus
ii  nautilus1:3.4.1-0ubuntu1file 
manager and graphical shell for GNOME

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

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

Title:
  there is no tab for access to file notes in the properties dialog

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  The Notes tab of the properties dialog has gone away some time between
  Lucid and Precise. The decoration indicating a note exists is still
  present suggesting the feature has not been intentionally dropped.
  Further examination shows that emblems have also disappeared (this
  appears to be intentional http://ubuntuguide.net/add-emblems-to-
  nautilus-files-folders-in-ubuntu-12-04-11-10 and is no great loss).

  I would expect the notes tabs to be present in the properties dialog
  or some other obvious way to read already existing notes (and
  preferably be able to edit them).

  $ lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04
  $ dpkg -l nautilus
  ii  nautilus1:3.4.1-0ubuntu1file 
manager and graphical shell for GNOME

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

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

[Desktop-packages] [Bug 993878] Re: there is no tab for access to file notes in the properties dialog

[Dan Kortschak]

Reported upstrean: https://bugzilla.gnome.org/show_bug.cgi?id=675417

** Bug watch added: GNOME Bug Tracker #675417
   https://bugzilla.gnome.org/show_bug.cgi?id=675417

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

Title:
  there is no tab for access to file notes in the properties dialog

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  The Notes tab of the properties dialog has gone away some time between
  Lucid and Precise. The decoration indicating a note exists is still
  present suggesting the feature has not been intentionally dropped.
  Further examination shows that emblems have also disappeared (this
  appears to be intentional http://ubuntuguide.net/add-emblems-to-
  nautilus-files-folders-in-ubuntu-12-04-11-10 and is no great loss).

  I would expect the notes tabs to be present in the properties dialog
  or some other obvious way to read already existing notes (and
  preferably be able to edit them).

  $ lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04
  $ dpkg -l nautilus
  ii  nautilus1:3.4.1-0ubuntu1file 
manager and graphical shell for GNOME

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

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

[Desktop-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

When I started looking at this problem, the machine would not boot
without nomodeset. This is no longer the case - and removing that fixes
the problem.

Thank you for looking at this, Timo. Please mark as invalid.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bio

[Desktop-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Not

[Desktop-packages] [Bug 1624299] [NEW] SFTP protocol source cannot be found

[Dan Kortschak]

Public bug reported:

Trying to play a video over SFTP fails, with Totem giving a pop-up:

"""
Required plugin could not be found

Videos requires to install plugins to support the following multimedia feature: 
SFTP protocol source
"""

There does not seem to be any package that fits this description in the
apt repos. Trying from the command line with a local terminal I get the
following:

"""
/run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4 
** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol 
source|urisource-sftp (SFTP protocol source)
/usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst 
was imported without specifying a version first. Use gi.require_version('Gst', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gst
/usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
Falling back to package information
CRITICAL:Could not find any packages to operate on
"""

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 16 19:28:29 2016
InstallationDate: Installed on 2016-06-07 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  SFTP protocol source cannot be found

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Trying to play a video over SFTP fails, with Totem giving a pop-up:

  """
  Required plugin could not be found

  Videos requires to install plugins to support the following multimedia 
feature: SFTP protocol source
  """

  There does not seem to be any package that fits this description in
  the apt repos. Trying from the command line with a local terminal I
  get the following:

  """
  /run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4 
  ** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol 
source|urisource-sftp (SFTP protocol source)
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst 
was imported without specifying a version first. Use gi.require_version('Gst', 
'1.0') before import to ensure that the right version gets loaded.
from gi.repository import Gst
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
  Falling back to package information
  CRITICAL:Could not find any packages to operate on
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 16 19:28:29 2016
  InstallationDate: Installed on 2016-06-07 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

I have sorted out the syscall-template.S issue by getting the libc6
source.

I have found places saying that the cause of gdb not liking the binary
is because of arch incompatibility (32 v 64). I tried this with no
change.

~# gdb /usr/bin/Xorg 2>&1 | tee gdb-Xorg.txt
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/Xorg": not in executable format: File format not recognised
(gdb) attach 2920
Attaching to process 2920
"/usr/lib/xorg/Xorg": not in executable format: File format not recognised
(gdb) cont
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xbdc85720 in ?? ()
(gdb) cont
Continuing.

Program received signal SIGTERM, Terminated.
0xbdc85cf3 in ?? ()
(gdb) cont
Continuing.

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) cont
The program is not being run.
(gdb) backtrace full
No stack.


Here we still have no capacity to get a backtrace. Once again, some indication 
of how to proceed to get more useful information would be greatly appreciated.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1

[Desktop-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

OK, `gdb64 /usr/lib/xorg/Xorg 2>&1 | tee gdb-Xorg.txt' works. The
instructions for backtracing at
https://wiki.ubuntu.com/X/Backtracing#Backtrace_with_gdb obviously need
some love.

With all the complaints from gdb out of the way it seems that the issue
shows up as the corrupted shared library list seen above.


** Attachment added: "Two attempts at backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1591472/+attachment/4715387/+files/gdb-Xorg.txt

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24

[Desktop-packages] [Bug 1591472] [NEW] Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

Public bug reported:

~ $ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
~ $ apt-cache policy nvidia-361 xorg
nvidia-361:
  Installed: 361.42-0ubuntu2
  Candidate: 361.42-0ubuntu2
  Version table:
 *** 361.42-0ubuntu2 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/restricted 
amd64 Packages
100 /var/lib/dpkg/status
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main amd64 
Packages
100 /var/lib/dpkg/status


Boot machine and login with correct credentials.

Expect a functioning X session with gnome.

Instead immediately returned to greeter.

Attempted to do backtracing, but this did not work because (presumably)
of absence of ../sysdeps/unix/syscall-template.S and an error returned
after staring gdb, `"/usr/bin/Xorg": not in executable format: File
format not recognised'. Went ahead any way and gdb sees:

```

Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
0x7fe59028acf3 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) cont
Continuing.
warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

Program received signal SIGTERM, Terminated.
0x7fe59028acf3 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
84  in ../sysdeps/unix/syscall-template.S
(gdb) cont
Continuing.

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
```

If given instructions on how to get backtracking to work, will happily
reattempt.

Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau is
unusable due to lag and sluggishness.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Jun 11 17:46:17 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
InstallationDate: Installed on 2016-06-07 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:066d Acer, Inc 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook P65_P67RGRERA
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: P65_P67RGRERA
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: li

[Desktop-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

Yoo hoo! Is anyone home?

Some triage love would be greatly appreciated here.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.ven