[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Got it, thanks!

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Allen]

Same issue here. I don't understand the status, "Won't fix"?

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Won't Fix

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

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

[Allen]

Public bug reported:

Random freezes

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 25 10:28:36 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-24 (1 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=3ea98830-6da6-49cf-b34a-00412e832e62 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze mantic 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/2054932

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Random freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 10:28:36 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing 

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

[Allen]

Public bug reported:

Nothing more. Just freezes all the time.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 09:37:57 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=3ea98830-6da6-49cf-b34a-00412e832e62 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze mantic 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/2054882

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Nothing more. Just freezes all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 24 09:37:57 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  

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

[Allen]

Public bug reported:

Everything freezes, several times per day. I am not sure if it's NVIDIA
related or not. I am willing to troubleshoot as long as I am told very
specifically what needs to be done.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.146.02  Sun Dec  3 
14:06:14 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 14:30:35 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-14 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240214)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.117-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.3-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze noble 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/2053278

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Everything freezes, several times per day. I am not sure if it's
  NVIDIA related or not. I am willing to troubleshoot as long as I am
  told very specifically what needs to be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.146.02  Sun Dec  3 
14:06:14 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Allen]

It's not producing a crash file.

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  New

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: 

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Allen]

Nothing in /var/crash.

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in gnome-control-center:
  Fix Released
Status in Webkit:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  New

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll 

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Allen]

https://errors.ubuntu.com/user/71bccc9eec8b281afbf94f22b6f69c64a37ecb7e24b101ec466be8c2cd4977590e029bded41a9364d90f45402e96cb8f3c33b48ae17febc41fc2a442a21d0ece

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in gnome-control-center:
  Fix Released
Status in Webkit:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  New

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 

[Desktop-packages] [Bug 2018656] Re: login process frozen in between username and password

[Allen]

Is this the same? 2023322?

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

Title:
  login process frozen in between username and password

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
   MY SYSTEM 
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  gnome-online-accounts:
Installed: 3.48.0-1
Candidate: 3.48.0-1
Version table:
   *** 3.48.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I have tested this on my desktop running 23.04 on Intel I-9, and the second 
desktop running the same (23.04) but on Intel I-7, and both of them show the 
same problem.

  -PROBLEM---

  When I entered my email address in my Google account, I could provide
  my email address, and after I clicked on the following form to enter
  my password.  The form was able to pick up my email address and moved
  to the following form for password entry; it just froze in between.
  Sometimes, the password form could pick up the first keyboard
  character but never go past 2nd character.  Sometimes, it just froze
  without being able to pick up the first keyboard character.

  Then a bit later, the whole box of gnome-online-accounts blacks out.
  Closing with X didn't work, so I had to xkill the app.

  -TYPICAL BEHAVIOR---

  Usually, on 22.04, I never had a problem adding online accounts,
  particularly for Google accounts.   The first form asked for my email
  address, and quickly moved on to the following form asking for a
  password.  Once the password is accepted, it will move on to the next
  form requesting my authorization for GNOME to connect to my account on
  Google before adding it to my Ubuntu system (I'd see the drive folder
  on the bar on Nautilus).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-online-accounts 3.48.0-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  6 13:51:07 2023
  InstallationDate: Installed on 2023-05-04 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2023322] Re: Unable to connect Ubuntu with Google Online Accounts

[Allen]

That command brings up the browser and things work fine there.

I don't know if it matters but it seems like connecting to Microsoft
also uses the same mechanism, but that works fine. It's just connecting
to google.

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

Title:
   Unable to connect Ubuntu with Google Online Accounts

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

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 

[Desktop-packages] [Bug 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes

[Allen]

I'm not sure if it's identical or not:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/2023322

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

Title:
  Cannot reauthorize Google account or authorize again. The app crashes

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  As in title

  I tried to relogin, The window prompt appears and quickly exits and
  nothing happens. Still cannot not logged in. Have to remove account
  and sign in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 17:45:34 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  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/2019739/+subscriptions


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

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

[Allen]

apport information

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

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

Title:
   Unable to connect Ubuntu with Google Online Accounts

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

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  --- 
  ProblemType: Bug
  ApportVersion: 

[Desktop-packages] [Bug 2023322] Re: Unable to connect Ubuntu with Google Online Accounts

[Allen]

apport information

** Tags added: apport-collected lunar

** Description changed:

  When I go into Settings > Online Accounts > Google, I get to the prompt
  for email address, once in a while it stops accepting input there. But
  often I can get to the password screen. Once I do, I can't type anything
  or paste anything.
  
  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.
  
  Nothing in /var/crash
  
  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2023-06-01 (7 days ago)
+ InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-online-accounts 3.48.0-1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  

[Desktop-packages] [Bug 2023322] [NEW] Unable to connect Ubuntu with Google Online Accounts

[Allen]

Public bug reported:

When I go into Settings > Online Accounts > Google, I get to the prompt
for email address, once in a while it stops accepting input there. But
often I can get to the password screen. Once I do, I can't type anything
or paste anything.

This is a fresh install of Ubuntu 23.04 and I have installed all
updates.

Nothing in /var/crash

Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - 
GNOME Terminal Server...
Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - 
GNOME Terminal Server.
Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for 
user root(uid=0) by (uid=0)
Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for 
user root
Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated 
successfully.
Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.

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

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

Title:
   Unable to connect Ubuntu with Google Online Accounts

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

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I 

[Desktop-packages] [Bug 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes

[Allen]

I am having the same issue. How can I help?

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

Title:
  Cannot reauthorize Google account or authorize again. The app crashes

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  As in title

  I tried to relogin, The window prompt appears and quickly exits and
  nothing happens. Still cannot not logged in. Have to remove account
  and sign in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 17:45:34 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  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/2019739/+subscriptions


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

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

[Allen]

Public bug reported:

Frequent lockups, not sure if it's related to NVIDIA or not.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
 GCC version:
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  4 12:29:49 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo RocketLake-S GT1 [UHD Graphics 750] [17aa:32dd]
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2023-06-01 (3 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and 
Mouse Combo
 Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF
 Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 30EF004VUS
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro nomodeset text
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3AA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3AA:bd03/16/2023:br1.58:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze lunar 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/2022864

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Frequent lockups, not sure if it's related to NVIDIA or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64

[Desktop-packages] [Bug 2006630] [NEW] CD not found in MusicBrainz, but I can see it in musicbrainz.org

[KD Allen]

Public bug reported:

rhythmbox version 3.4.4, Ubuntu Ubuntu 22.04.1 LTS
When I try to extract a legit copy of "Never born to follow" by the Men They 
Couldn't Hang, rhythmbox says "can't find, please add". I go to musicbrainz.org 
and can see it listed, but there is a 1 second discrepancy in the final track 
length, and I assume that is stopping the match. Presumably the existing data 
works for other people so I am hesitant to report it as a MusicBrainz data 
error. Rather than a bug therefore, this may be an enhancement request either 
to loosen the match criteria, or perhaps allow the user to manually enter a 
MusicBrainz url or other ID to force the match?

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

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

Title:
  CD not found in MusicBrainz, but I can see it in musicbrainz.org

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  rhythmbox version 3.4.4, Ubuntu Ubuntu 22.04.1 LTS
  When I try to extract a legit copy of "Never born to follow" by the Men They 
Couldn't Hang, rhythmbox says "can't find, please add". I go to musicbrainz.org 
and can see it listed, but there is a 1 second discrepancy in the final track 
length, and I assume that is stopping the match. Presumably the existing data 
works for other people so I am hesitant to report it as a MusicBrainz data 
error. Rather than a bug therefore, this may be an enhancement request either 
to loosen the match criteria, or perhaps allow the user to manually enter a 
MusicBrainz url or other ID to force the match?

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


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

[Desktop-packages] [Bug 1994201] [NEW] package sgml-base 1.30 failed to install/upgrade: triggers looping, abandoned

[Allen Rubin]

Public bug reported:

failed to install

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: sgml-base 1.30
ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210
Uname: Linux 5.4.0-131-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Oct 25 16:18:19 2022
DuplicateSignature:
 package:sgml-base:1.30
 Processing triggers for libgl1-amdgpu-mesa-dri:i386 (1:20.1.6-1188099) ...
 dpkg: error processing package libgl1-amdgpu-mesa-dri:i386 (--configure):
  installed libgl1-amdgpu-mesa-dri:i386 package post-installation script 
subprocess returned error exit status 1
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-06-24 (1584 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: sgml-base
Title: package sgml-base 1.30 failed to install/upgrade: triggers looping, 
abandoned
UpgradeStatus: Upgraded to jammy on 2022-10-25 (0 days ago)

** Affects: sgml-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package sgml-base 1.30 failed to install/upgrade: triggers looping,
  abandoned

Status in sgml-base package in Ubuntu:
  New

Bug description:
  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: sgml-base 1.30
  ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210
  Uname: Linux 5.4.0-131-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 25 16:18:19 2022
  DuplicateSignature:
   package:sgml-base:1.30
   Processing triggers for libgl1-amdgpu-mesa-dri:i386 (1:20.1.6-1188099) ...
   dpkg: error processing package libgl1-amdgpu-mesa-dri:i386 (--configure):
installed libgl1-amdgpu-mesa-dri:i386 package post-installation script 
subprocess returned error exit status 1
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-06-24 (1584 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: sgml-base
  Title: package sgml-base 1.30 failed to install/upgrade: triggers looping, 
abandoned
  UpgradeStatus: Upgraded to jammy on 2022-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1994201/+subscriptions


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

[Desktop-packages] [Bug 1973093] [NEW] xmessage loses text area as buttons are added and -g

[Ian! D. Allen]

Public bug reported:

xmessage text gets obscured with option combinations using buttons and
geometry specifications.

Quick background: xmessage creates a new grey window with a white text
box inside it.  Without -buttons, the white text box usually spans the
full width of the grey window that contains it, leaving no margins.
Things start going wrong when you start specifying -buttons or -g
(geometry), and text can end up being obscured.

Problem #1:

If the width of all the buttons you specify makes the grey window wider
than the text, the white text box does not increase in width to match.
You end up with an undesirable wide grey margin on the right side of the
white text box.  If you resize the window, making it less wide, the grey
margin does not narrow; it moves in and covers and obscures the text,
even though there is plenty of room for the text.

Suggested Fix #1: The white text box must always be created the same width
as the window that contains it, with no useless grey margin to the right.
Narrowing the width of the window should not cause text to be obscured
by a wide and useless fixed grey margin.

Reproduce:

xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20
"123456789"

Problem #2:

If you add a -g (geometry) option and specify just the width (not the
height) for a window with buttons wider than the text box, the obscuring
grey margin persists.

If you add a "-g NNN" option, where NNN is the width that xmessage would
have chosen itself, then you get exactly the same unpleasant behaviour
as Problem #1 above.

If you increase the NNN to be wider that what xmessage would have used,
then both the window and the text box width are created increased by
that amount, as if you had resized the window with a mouse.  The useless
grey margin to the right of the text box stays the same width, just as
in Problem #1.

If you decrease the NNN to be narrower that what xmessage would have used,
then both the window and the text box width are created decreased by that
amount, as if you had resized the window with a mouse.  Not all buttons
will show; this is expected.  What is not expected is that the useless
grey margin to the right of the text box stays the same width, and so
it now overwrites and obscures the text, even though there is plenty
of room for the text.  If you resize the window back so that all the
buttons show, all the text also shows and we're back to Problem #1 above.

Suggested Fix #2: Same as above.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"

Problem #3:

If you add a -g option and specify both the width *and* the height for
a window with buttons wider than the text, things get much worse.

If you add a "-g NNNx55" option, where NNN is the width that xmessage
would have chosen itself and "55" is about the same height, you would
expect to get exactly the same results as if you didn't specify any
geometry at all.  That's not what happens.  You get a fixed-width text
window about 12 characters wide, with a huge grey margin on the right.
It doesn't matter what size text you specify; the white text box will be
created about 12 characters wide and any text to the right of that will
be masked and obscured by the wide grey margin.  Changing the width of
the window has all the problems of Problems #1 and #2 above.

Suggested Fix #3: Same as above.
Specifying a geometry that is identical to what xmessage would have chosen
itself should create an identical window.  Text should not be obscured.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 541x55 -buttons
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU
DON'T SEE THIS"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: x11-utils 7.7+5build2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 17:12:52 2022
DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed
 v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated 
Graphics Controller [10cf:15f5]
InstallationDate: Installed on 2020-09-08 (610 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 

[Desktop-packages] [Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)

[Allen Lowe]

I'm having the same issue with an RTX 2080. If I start up in safe
graphics mode, it works. But of course then I get degraded graphics.

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

Title:
  Weird colors after startup (Ubuntu 22.04)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

[Ian! D. Allen]

I'm now getting radeon GPU lockup with the Ubuntu 5.11.0-25 and 5.11.0-27 
kernels.
The 5.8.0-63 kernel and all previous work fine.

$ lspci | grep ATI
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 
GL [FirePro 2450]
06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 GL 
[FirePro 2450]

I use three (of four possible) 1600x1200 LCD monitors on the four
FirePro outputs.

Selected lines from /var/log/syslog are attached.  These are the actual
repeating lockup lines:

Aug 17 15:20:44 linux kernel: [ 7403.029720] radeon :06:00.0: GPU lockup 
(current fence id 0x0001 last fence id 0x0002 on ring 0)
Aug 17 15:20:44 linux kernel: [ 7403.541687] radeon :06:00.0: ring 0 
stalled for more than 11304msec

The last two lines "GPU lockup" and "ring 0 stalled" repeat over and
over.  The keyboard and the X11 display won't respond.  I can ssh into
the machine, and I can type "reboot", but it hangs somewhere in the
shutdown (or else it is waiting for something longer than I'm willing to
wait).  The system reboots when I type ALT-SYSRQ-B on the keyboard, and
I select the 5.8.0-63 kernel and everything is fine.


** Attachment added: "Selected drm and radeon lines from syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5518846/+files/radeon.txt

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

Title:
  GPU lockup ring 0 stalled for more than X msec

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 

[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04

[Stephen Allen]

I wonder if the recent Gnome 3.38.5 update addresses this?

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

Title:
  Overview sometimes fails to appear or disappear in 21.04

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

Bug description:
  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this 
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu. 

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

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

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

[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Damn doesn't seem to be a close or delete option. Daniel could you
please do the honours?

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

Title:
  Gnome Wayland session starts, then quits.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Daniel I was pretty sure that the problem existed in my home directory. So, 
rather than go through all the gnome gnome settings one by one, with subsequent 
reboots, I cleaned out my home directory of all gnome specific settings at once 
this am, and rebooted and problem is gone - I'm now in XWayland.
 
This would have taken a long time to troubleshoot, so I took the quick route it 
was a Fool's errand to try to figure out which setting was creating the 
problem, because I have backed up my home directory for over 10 years 
continuously, and I had a lot of cruft in there, so it was time to clean it 
out.I'm going to close this bug now, thanks for all your help Daniel I didn't 
want to waste any more of your time. Cheers.

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

Title:
  Gnome Wayland session starts, then quits.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Regarding Item #3: Didn't know /var/crash existed, thanks for the heads
up with the article too.

I browsed /var/crash, there are quite a few files (18) from yesterday
and today. Now none dated Jan 04 matched XWayland, however 2 from
yesterday. The more recent ones (Jan 04) mention 'Blueman Applet' only.
Do you want both? According to the article referenced, it seems to
indicate using ubuntu-bug to run on the most recent files in
/var/log/crash — were you meaning that I should do that in the future?
Anywho, will touch base in the morning EST.

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

Title:
  Gnome Wayland session starts, then quits.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.

[Stephen Allen]

Thanks Daniel, yes I meant a crash, just different wording.

OK Attached is the file with all extensions disabled. If I'm reading the
file correctly it seems to be a snap issue with an app not autostarting?
Anyway lots of errors but when I scrolled down to the bottom showing the
most recent boot up using XWayland, only two errors, relating to a snap
launch.

** Attachment added: "journalctl log file"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+attachment/5449337/+files/prevboot.txt

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

Title:
  Gnome Wayland session starts, then quits.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1909946] Re: XWayland session starts, then quits.

[Stephen Allen]

Some more details: Using both gnome-wayland & ubuntu-wayland sessions,
the common major errors are the following:

12:22:45 PM gnome-shell: Can't create a GtkStyleContext without a display 
connection
12:22:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file


It happens when the desktop appears after about maybe 10 seconds or so. So I 
can't see PAM being involved as PAM is invoked during login — isn't it?

Anyway hope this helps.

Oh, I reinstalled from a backup image, (I have the system on a separate
hard drive to my home directory) that was working correctly on Wayland.
And with nothing added to the image, the same behaviour happened. So,
I'm thinking this is probably a setting in my home directory — but which
one?

Suggestions to troubleshoot this are welcome — I'll put in the time to
help figure this out.

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

Title:
  XWayland session starts, then quits.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1909946] [NEW] XWayland session starts, then quits.

[Stephen Allen]

Public bug reported:

So, this started about a week ago after an update from Ubuntu. I can
initially login with XWayland, but something loading after the desktop
appears, causes the session to exit. The only thing I can find relevant
in the logs at the timestamp this occurred are the following:

-gkr-pam: unable to locate daemon control file

-Failed to start Process error reports when automatic reporting is
enabled.

-A start job for unit UNIT has failed

I hope this helps track down the issue. Thanks for reading.

BTW I have to submit this as a bug on something else, launchpad keeps
telling me that XWayland doesn't exist.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xwayland 2:1.20.9-2ubuntu1.1
Uname: Linux 5.9.16-xanmod1 x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan  3 19:33:28 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 
OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
InstallationDate: Installed on 2020-04-25 (253 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: groovy pam xwayland

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

Title:
  XWayland session starts, then quits.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries

[Todd Allen]

Example of errors:

Jun  1 18:27:41 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: Can't set a parent on widget which has 
a parent
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Jun  1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed

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

Title:
  .xsession-errors filled with entries

Status in Network Manager Applet:
  New
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

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

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

[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries

[Todd Allen]

I am encountering the same issue in 20.04. The message is repeating
approximately every three seconds, resulting in log files of hundreds of
gigabytes. It also makes the system log nearly useless for any other
use; it is near-impossible to even open the file, and causes logrotate
to hang up for hours every time it attempts to run since it attempts
compression.

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

Title:
  .xsession-errors filled with entries

Status in Network Manager Applet:
  New
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

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

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

[Desktop-packages] [Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITI

[Stephen Allen]

Fixed for me as the reporter of the bug - Thus it can be closed. Thanks!

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

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

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  It core dumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 21:08:46 2020
  InstallationDate: Installed on 2019-02-23 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-C

[Stephen Allen]

Hi, Evolution Calendar is working fine on my end. Just a data point in case
you don't have the latest updates installed. I haven't tested
Gnome-Calendar yet - I'll do that next and report back.

On Fri, Apr 10, 2020 at 11:25 AM Bicet <1867...@bugs.launchpad.net>
wrote:

> Same happening here with an exchange calendar and multi-day events
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867302
>
> Title:
>   gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
>   gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
>   (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
>   gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
>   Segmentation fault (core dumped)
>
> Status in gnome-calendar package in Ubuntu:
>   New
>
> Bug description:
>   It core dumped.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-calendar 3.36.0-1
>   Uname: Linux 5.5.8-xanmod6 x86_64
>   ApportVersion: 2.20.11-0ubuntu20
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar 12 21:08:46 2020
>   InstallationDate: Installed on 2019-02-23 (383 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   SourcePackage: gnome-calendar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions
>


-- 
"It is through science that we prove, but through intuition that we
discover."

- Henri Poincare

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

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  It core dumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 21:08:46 2020
  InstallationDate: Installed on 2019-02-23 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1867080] Re: [radeon] No mouse cursor drawn in Wayland session

[Stephen Allen]

Thanks fellas, it's fixed for me. Great release!

@Daniel this desktop version definitely appears quicker and smoother! No
doubt due to your extensive work in that regard.

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

Title:
  [radeon] No mouse cursor drawn in Wayland session

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1792085] Re: Regression: MTP not working/very slow

[Allen Brian]

Also have this problem - on Linux Mint 19.3, XFCE with a Samsung S7.
This worked fine under Mint 17.1 - listing 3500 jpeg files took 20
seconds; usually less.  Now when trying to read the same directory which
is now only 2500 jpeg files, both Thunar and PCMANFM take > 20 MINUTES
to generate a file listing - a slowdown by a factor of 60 for a thousand
fewer files.  But once the listing shows up, I can scroll and do file
transfers just fine.  Directories of only a few hundred jpegs on the
phone come up almost instantly.  I can't get a more recent version of
the libmtp than 1.1.13 from the repository, and I get errors that state
"Dependency is not satisfiable: libmpt9(=1.1.17-2)" when I try the other
solutions mentioned previously.

This is a deal breaker. Downloading pictures from my phone is one of the
most common operations I perform.  At this point, I may have to
reconsider going back to Windows 10, which at least gets the job done -
it takes roughly 40 seconds to do the directory on those 2500 files.

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

Title:
  Regression: MTP not working/very slow

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1867302] [NEW] gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRI

[Stephen Allen]

Public bug reported:

It core dumped.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-calendar 3.36.0-1
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 12 21:08:46 2020
InstallationDate: Installed on 2019-02-23 (383 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Segmentation fault (core dumped)

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  It core dumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 21:08:46 2020
  InstallationDate: Installed on 2019-02-23 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866995] Re: XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

[Stephen Allen]

I just noticed that GDM hasn't been updated to 3.26, so this shouldn't
be reported yet as the new gnome packages haven't obviously been
released yet. So pardon the interruption.

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

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Stephen Allen (stephen-d-allen)

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

Title:
  XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The cursor is there, just invisible. If one moves the mouse around one
  can see that it's there, but not visible. Tested in both Ubuntu
  XWayland session and Gnome Vanillia session. It's working OK in Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 08:24:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-xanmod6 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1867017] Re: Cursor Invisible, but there.

[Stephen Allen]

I just noticed that GDM hasn't been updated to 3.26, so this shouldn't
be reported yet as the new gnome packages haven't obviously been
released yet. So pardon the interruption.

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

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Stephen Allen (stephen-d-allen)

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

Title:
  Cursor Invisible, but there.

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  Further to my previous bug for XWayland same issue. I should probably
  note that this isn't a clean install but an upgrade from 19.10 on bare
  metal. HTH.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:37:49 2020
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1867017] [NEW] Cursor Invisible, but there.

[Stephen Allen]

Public bug reported:

Further to my previous bug for XWayland same issue. I should probably
note that this isn't a clean install but an upgrade from 19.10 on bare
metal. HTH.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 11:37:49 2020
InstallationDate: Installed on 2019-02-23 (381 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Cursor Invisible, but there.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Further to my previous bug for XWayland same issue. I should probably
  note that this isn't a clean install but an upgrade from 19.10 on bare
  metal. HTH.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:37:49 2020
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866995] [NEW] XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

[Stephen Allen]

Public bug reported:

The cursor is there, just invisible. If one moves the mouse around one
can see that it's there, but not visible. Tested in both Ubuntu XWayland
session and Gnome Vanillia session. It's working OK in Xorg.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland 2:1.20.7-2ubuntu2
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 08:24:26 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 
OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
InstallationDate: Installed on 2019-02-23 (381 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-xanmod6 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal reproducible single-occurrence ubuntu

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

Title:
  XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The cursor is there, just invisible. If one moves the mouse around one
  can see that it's there, but not visible. Tested in both Ubuntu
  XWayland session and Gnome Vanillia session. It's working OK in Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 08:24:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1837392] Re: "unable to find firefox.desktop" when clicking "Show Details" on the Firefox menu (top)

[Jont Allen]

This may be useful, and a bit obvious:
/usr/share/applications/firefox.desktop

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

Title:
  "unable to find firefox.desktop" when clicking "Show Details" on the
  Firefox menu (top)

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  When a user tries to open the menu that is on the top, next to
  Activities button, and clicks "Show Details", it opens GNOME Software,
  but stays on the loading bar for a while then it says "Unable to find
  firefox.desktop".

  However, if I opened GNOME Software to search for Firefox, there are
  two entries for Firefox, one from Ubuntu repo, one from Snap. I know
  that Firefox existed on GNOME Software, but it seems weird that it
  won't be able to search for "firefox.desktop."

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 14:59:54 2019
  InstallationDate: Installed on 2019-07-21 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1856298] [NEW] Tried to start xdiagnose and got error.

[Sean Allen]

Public bug reported:

No more details that  I know other than what's in the summary.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec 13 03:32:46 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
InstallationDate: Installed on 2019-12-06 (7 days ago)
InstallationMedia: It
MachineType: Dell Inc. Dell System Inspiron N7110
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 05VJ58
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System Inspiron N7110
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Tried to start xdiagnose and got error.

Status in xorg package in Ubuntu:
  New

Bug description:
  No more details that  I know other than what's in the summary.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec 13 03:32:46 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
  InstallationDate: Installed on 2019-12-06 (7 days ago)
  InstallationMedia: It
  MachineType: Dell Inc. Dell System Inspiron N7110
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=29f55db3-5639-47d5-82af-087cfc3e019d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05VJ58
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn05VJ58:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N7110
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Desktop-packages] [Bug 1836481] [NEW] Every Backup Is A Complete Backup

[Stephen Allen]

Public bug reported:

The past couple of weeks, the following issue has occurred. Despite the 1st 
backup being done quite some time ago, recently the application asks for my 
password each time it runs, as it is creating a NEW backup, instead of 
appending to the existing.
This is very problematic as it often takes longer than 24hrs to complete.

I'm using Google Drive as my backup storage.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: duplicity 0.7.18.2-1ubuntu3.1
Uname: Linux 5.2.0-050200rc7-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 14 08:53:11 2019
InstallationDate: Installed on 2019-02-23 (140 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  Every Backup Is A Complete Backup

Status in duplicity package in Ubuntu:
  New

Bug description:
  The past couple of weeks, the following issue has occurred. Despite the 1st 
backup being done quite some time ago, recently the application asks for my 
password each time it runs, as it is creating a NEW backup, instead of 
appending to the existing.
  This is very problematic as it often takes longer than 24hrs to complete.

  I'm using Google Drive as my backup storage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: duplicity 0.7.18.2-1ubuntu3.1
  Uname: Linux 5.2.0-050200rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 14 08:53:11 2019
  InstallationDate: Installed on 2019-02-23 (140 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1816549] [NEW] het zoeken beeld blijft hangen in midden van scherm

[Bernard H. Allen]

Public bug reported:

zoeken image blijft hangen

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Feb 19 11:20:07 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Wrestler [Radeon HD 
6310] [1462:aa53]
InstallationDate: Installed on 2019-02-18 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-AA53
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-AA53
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd02/01/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-AA53:pvr0A:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-AA53:rvrTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-AA53
dmi.product.version: 0A
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  het zoeken beeld blijft hangen in midden van scherm

Status in xorg package in Ubuntu:
  New

Bug description:
  zoeken image blijft hangen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Feb 19 11:20:07 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Wrestler [Radeon HD 
6310] [1462:aa53]
  InstallationDate: Installed on 2019-02-18 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-AA53
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-AA53
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd02/01/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-AA53:pvr0A:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-AA53:rvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-AA53
  dmi.product.version: 0A
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: 

Re: [Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

I found that in my situation it was the upgrade not working good with some
config settings in my ~/home. When I was beta testing, I don't think the
Ubuntu developers considered that many problems are associated with
upgrades. Once I did a clean install, this situation was gone.

On Wed, Sep 12, 2018 at 8:35 PM Leoncio de Queiroz Maya <
1758...@bugs.launchpad.net> wrote:

> Thank you Cas.
> Let me answer to your suggestions.
>
> Check all updates are installed? Try proposed updates?
> I always install all updates.
>
> Is this with mouse or trackpad?
> I only use the trackpad.
>
> Have you checked what gsettings is reporting?
>
> gsettings get org.gnome.desktop.peripherals.mouse left-handed
> true
>
> Perhaps try a booting with a livecd ubuntu and test mouse there. I don't
> have a CD with Ubuntu 18.04.
>
> I started using Ubuntu with version 12.04 and I have updated it to
> versions 14.04 and 16.04. The left-handed mode always worked fine. A
> couple of weeks ago, I was offered to install version 18.04. The bug
> started after the installation of this new version. I must say it is
> very annoying.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Invalid
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1788926] [NEW] package nvidia-prime 0.8.2 failed to install/upgrade: there is no script in the new version of the package - giving up

[Brad Allen]

Public bug reported:

I am upgrading the environment in which I have NVIDIA processes run, and
they need to be able to find the nvidia libraries and everything else
needed to work with my (very expensive) NVIDIA card that I require.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-prime 0.8.2
ProcVersionSignature: Ubuntu 4.4.0-133.159-lowlatency 4.4.134
Uname: Linux 4.4.0-133-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Aug 24 12:24:18 2018
ErrorMessage: there is no script in the new version of the package - giving up
InstallationDate: Installed on 2016-11-21 (641 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.2.27
SourcePackage: nvidia-prime
Title: package nvidia-prime 0.8.2 failed to install/upgrade: there is no script 
in the new version of the package - giving up
UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago)

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment removed: "Df.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180416/+files/Df.txt

** Attachment removed: "Dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180417/+files/Dmesg.txt

** Attachment removed: "DpkgHistoryLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180418/+files/DpkgHistoryLog.txt

** Attachment removed: "AptOrdering.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180414/+files/AptOrdering.txt

** Attachment removed: "NonfreeKernelModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180413/+files/NonfreeKernelModules.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180415/+files/Dependencies.txt

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

Title:
  package nvidia-prime 0.8.2 failed to install/upgrade: there is no
  script in the new version of the package - giving up

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  I am upgrading the environment in which I have NVIDIA processes run,
  and they need to be able to find the nvidia libraries and everything
  else needed to work with my (very expensive) NVIDIA card that I
  require.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.2
  ProcVersionSignature: Ubuntu 4.4.0-133.159-lowlatency 4.4.134
  Uname: Linux 4.4.0-133-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Aug 24 12:24:18 2018
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2016-11-21 (641 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.2.27
  SourcePackage: nvidia-prime
  Title: package nvidia-prime 0.8.2 failed to install/upgrade: there is no 
script in the new version of the package - giving up
  UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+subscriptions

-- 
Mailing list: https://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 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

[Stephen Allen]

I can click, just no response to that action. I'll close this if you think
it's already represented.

On Thu, Jun 14, 2018 at 11:15 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> It sounds like you mean you just can't click on things.
>
> There is a whole family of those bugs to check out here:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=noclick
>
> ** Tags added: noclick
>
> ** Also affects: mutter (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776901
>
> Title:
>   Startup or Reboot GDM3 Keyboard/Mouse Not Working
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I don't reboot often due to running LTS. However over the past month
>   or so, on subsequent reboots after upgrades, GDM3 accepts focus but
>   won't accept any input either from keyboard or mouse.
>
>   The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
>   a console, which won't give me a login prompt until I hit the 'return'
>   key. Then I can go back to the GDM3 session and login normally.
>
>   I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
>   updates applied.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.2-0ubuntu1.2
>   ProcVersionSignature: Ubuntu
> 4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
>   Uname: Linux 4.15.0-20201805060708-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Jun 14 08:44:36 2018
>   InstallationDate: Installed on 2018-01-19 (146 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.


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

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

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I don't reboot often due to running LTS. However over the past month
  or so, on subsequent reboots after upgrades, GDM3 accepts focus but
  won't accept any input either from keyboard or mouse.

  The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
  a console, which won't give me a login prompt until I hit the 'return'
  key. Then I can go back to the GDM3 session and login normally.

  I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
  updates applied.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
  Uname: Linux 4.15.0-20201805060708-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 14 08:44:36 2018
  InstallationDate: Installed on 2018-01-19 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1776901] [NEW] Startup or Reboot GDM3 Keyboard/Mouse Not Working

[Stephen Allen]

Public bug reported:

I don't reboot often due to running LTS. However over the past month or
so, on subsequent reboots after upgrades, GDM3 accepts focus but won't
accept any input either from keyboard or mouse.

The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to a
console, which won't give me a login prompt until I hit the 'return'
key. Then I can go back to the GDM3 session and login normally.

I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current updates
applied.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
Uname: Linux 4.15.0-20201805060708-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jun 14 08:44:36 2018
InstallationDate: Installed on 2018-01-19 (146 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I don't reboot often due to running LTS. However over the past month
  or so, on subsequent reboots after upgrades, GDM3 accepts focus but
  won't accept any input either from keyboard or mouse.

  The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
  a console, which won't give me a login prompt until I hit the 'return'
  key. Then I can go back to the GDM3 session and login normally.

  I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
  updates applied.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
  Uname: Linux 4.15.0-20201805060708-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 14 08:44:36 2018
  InstallationDate: Installed on 2018-01-19 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

Well it's fixed, that's the important thing.

On Sat, Jun 2, 2018 at 9:30 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:

> Make that 4.13 kernel. Can't type today.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

Trish, run this in a terminal as one line:

gsettings get org.gnome.desktop.peripherals.mouse left-handed

What does it return? True or false?

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

It was fixed some time ago before 18.04 was released. Do you have all
repos activated, including /contrib & /universe?

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

If  I recall correctly it might have been a libinput update? I'm sure the
developer will answer soon. Trish I assume you've rebooted?

On Thu, May 31, 2018 at 7:01 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:

> Actually, I just tried plugging in my office wireless mouse into the
> personal laptop, and the buttons work fine on that. So it's JUST the
> buttons with the track pad. In every previous version of Ubuntu I've
> used, I've always just changed the touchpad buttons through GCC under
> the mouse settings. Is there another way to change settings for the
> touchpad?
>
> If it helps, my personal laptop is a Lenovo Ideapad 300.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button to Right (left-handed) in Settings
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
> Status in xserver-xorg-input-libinput package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Stephen Allen]

Confirm that as of Saturday April 14/18 update: the issue is resolved
for me.

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

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Thanks a lot! Been driving me nuts and afraid that I'll get used to this
and not able to go back.

On Wed, Apr 11, 2018 at 4:15 PM Launchpad Bug Tracker <
1758...@bugs.launchpad.net> wrote:

> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Well I don't know what to say - I'm using Ubuntu's environment. Somehow
over time I didn't notice that the vanilla-gnome-session was
removed/replaced. Now I have packages that I didn't have before. I'll
delete the gnome environment settings I have in my ~/home and see what
happens. These wouldn't have any effect on the plymouth-bug or losing
keyboard and mouse focus on gdm3. This iteration isn't worthy of a 'LTS'
release.

On Tue, Apr 3, 2018 at 6:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> I'm using real installs, not virtual.
>
> I suppose you are talking about the vanilla-gnome-desktop package, then,
> i.e. a meta package whose purpose is to install GNOME packages. The
> login options are provided by the gnome-session package, and the options
> are:
>
> GNOME
> GNOME on Xorg
>
> I had gnome-session installed already, chose the GNOME option (which
> means GNOME on Wayland), and could still successfully change the mouse
> behavior via g-c-c.
>
> So I couldn't reproduce the issue you described this time either, and
> I'm out of ideas.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   New
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Gunnar I'm on Xorg Vanilla-Gnome-Session. Jeremy had mentioned a few
weeks back that he needed testing on 'vanilla-gnome-session'(thats an
installable package, Gunnar) so I installed and am reporting bugs on it.
Hope this clears up any misunderstanding. Cheers.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

No Vanilla Gnome means 'Vanilla-Gnome-Session'.

On Tue, Apr 3, 2018 at 4:39 PM Stephen 
wrote:

> Well I'm using bare metal and my ~/home is in good shape, from backups.
> In  terms of my system I'm running a vanilla Ubuntu-Gnome and the reason
> it's not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
> Are you running your instance on bare metal or emulation?
>
> On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
> 1758...@bugs.launchpad.net> wrote:
>
>> My 'problem' is that I can't reproduce the issue.
>>
>> You now mentioned a few things, which indicate that your system isn't in
>> the best shape.
>>
>> While I have tested this on "Ubuntu with Xorg", you mentioned that you
>> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
>> chance you can log in to an "Ubuntu with Xorg" session and check if the
>> problem is present for you there?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758306
>>
>> Title:
>>   Cannot switch mouse primary button in GCC
>>
>> Status in gnome-control-center package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
>> configured for left handed use. That is the mouse primary button being
>> switched to the right. GCC doesn't seem to work for this now. I don't know
>> if it's related to evdev or what.
>>   Held back reporting this in case it was fixed by changes overnight.
>> Updated this morning and problem persists.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>>   ProcVersionSignature: Ubuntu
>> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>>   ApportVersion: 2.20.8-0ubuntu10
>>   Architecture: amd64
>>   CurrentDesktop: GNOME
>>   Date: Fri Mar 23 07:07:02 2018
>>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
>> (20170920)
>>   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/1758306/+subscriptions
>>
> --
>
> This email is printed from 100% recycled electrons.
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Well I'm using bare metal and my ~/home is in good shape, from backups. In
terms of my system I'm running a vanilla Ubuntu-Gnome and the reason it's
not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
Are you running your instance on bare metal or emulation?

On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> My 'problem' is that I can't reproduce the issue.
>
> You now mentioned a few things, which indicate that your system isn't in
> the best shape.
>
> While I have tested this on "Ubuntu with Xorg", you mentioned that you
> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
> chance you can log in to an "Ubuntu with Xorg" session and check if the
> problem is present for you there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Makes sense.
OK I had already tried a new user account, but tried again (just in case).
Doesn't affect the issue - it still remains (I can change it in G-C-C but
doesn't change mouse behaviour). Complicating trouble shooting is
continuously running into the 'plymouth corruption bug' at login making it
difficult to choose the new user! As well the bug in gdm3 'losing keyboard
and mouse control' when I logout necessitates a hard reboot each time.
Annoying. lol
In terms of the left handed mouse issue, it doesn't make much sense that it
would be my home settings - as stated this worked several days ago fine, a
recent update borked it, so a regression somewhere.

On Mon, Apr 2, 2018 at 12:00 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> Thanks. Then the question is why it doesn't have any effect for you.
>
> Another test: Can you please create an additional user, log in to that
> user, and test it there? If it works for the other user, the problem is
> somewhere in the $HOME of your first user.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Er, sorry I posted the wrong output, I had toggled it. It's showing as true
when switched to left handed in G-C-C:
'gsettings get org.gnome.desktop.peripherals.mouse left-handed
true'

On Mon, Apr 2, 2018 at 7:23 AM Stephen 
wrote:

> Thanks Gunnar. It's sticking in 'gsettings': gsettings get
> org.gnome.desktop.peripherals.mouse left-handed
> false
> Yet the left handed primary button (right button on mouse) still shows me
> a contextual menu.
> So, yes, the value is changed, but doesn't have any affect.
>
> On Sun, Apr 1, 2018 at 9:20 PM Gunnar Hjalmarsson <
> 1758...@bugs.launchpad.net> wrote:
>
>> @Simon: What makes you think that modifications of the GUI for the
>> region panel has anything to do with whether the primary button setting
>> is effective?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758306
>>
>> Title:
>>   Cannot switch mouse primary button in GCC
>>
>> Status in gnome-control-center package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
>> configured for left handed use. That is the mouse primary button being
>> switched to the right. GCC doesn't seem to work for this now. I don't know
>> if it's related to evdev or what.
>>   Held back reporting this in case it was fixed by changes overnight.
>> Updated this morning and problem persists.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>>   ProcVersionSignature: Ubuntu
>> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>>   ApportVersion: 2.20.8-0ubuntu10
>>   Architecture: amd64
>>   CurrentDesktop: GNOME
>>   Date: Fri Mar 23 07:07:02 2018
>>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
>> (20170920)
>>   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/1758306/+subscriptions
>>
> --
>
> This email is printed from 100% recycled electrons.
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

-- 
Mailing list: https://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 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Thanks Gunnar. It's sticking in 'gsettings': gsettings get
org.gnome.desktop.peripherals.mouse left-handed
false
Yet the left handed primary button (right button on mouse) still shows me a
contextual menu.
So, yes, the value is changed, but doesn't have any affect.

On Sun, Apr 1, 2018 at 9:20 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> @Simon: What makes you think that modifications of the GUI for the
> region panel has anything to do with whether the primary button setting
> is effective?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   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/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

 Thanks SQ.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Still happening - surely I'm not the only person that uses a mouse left
handed?! Can someone look at this please?

** Description changed:

- Prior to yesterday's Bionic update, I had my mouse configured for left handed 
use. That is the mouse primary button being switched to the right. GCC doesn't 
seem to work for this now. I don't know if it's related to evdev or what.
+ Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

[Stephen Allen]

Thanks. Thursday's March 29/18 updates seemed to have fixed it! Thank-
you.

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

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
  Been happening for the past week.

  Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
  Happens in both vanilla-gnome-session and ubuntu-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 10:32:33 2018
  InstallationDate: Installed on 2018-01-19 (65 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

[Stephen Allen]

Circumstances are somewhat different than the duplicate bug.

** This bug is no longer a duplicate of bug 1750995
   Logging out live session takes several minutes

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
  Been happening for the past week.

  Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
  Happens in both vanilla-gnome-session and ubuntu-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 10:32:33 2018
  InstallationDate: Installed on 2018-01-19 (65 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

[Stephen Allen]

Not really a duplicate - this doesn't kick me into a terminal session and
this isn't the 'Live' edition but an installed on metal situation.

On Mon, Mar 26, 2018 at 3:50 AM Jean-Baptiste Lallement <
jean-baptiste.lallem...@ubuntu.com> wrote:

> *** This bug is a duplicate of bug 1750995 ***
> https://bugs.launchpad.net/bugs/1750995
>
> ** This bug has been marked a duplicate of bug 1750995
>Logging out live session takes several minutes
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758677
>
> Title:
>   Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout
>
> Status in gnome-session package in Ubuntu:
>   New
>
> Bug description:
>   When manually logging out, it often takes over 30 seconds to give me
> logout dialogue.
>   Been happening for the past week.
>
>   Additionally When I complete the logout - Mouse or keyboard input isn't
> registered forcing a hard reboot.
>   Happens in both vanilla-gnome-session and ubuntu-session.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-session 3.28.0-0ubuntu1
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 25 10:32:33 2018
>   InstallationDate: Installed on 2018-01-19 (65 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-session
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1758677/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
  Been happening for the past week.

  Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
  Happens in both vanilla-gnome-session and ubuntu-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 10:32:33 2018
  InstallationDate: Installed on 2018-01-19 (65 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758677] [NEW] Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

[Stephen Allen]

Public bug reported:

When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
Been happening for the past week.

Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
Happens in both vanilla-gnome-session and ubuntu-session.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 10:32:33 2018
InstallationDate: Installed on 2018-01-19 (65 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
  Been happening for the past week.

  Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
  Happens in both vanilla-gnome-session and ubuntu-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 10:32:33 2018
  InstallationDate: Installed on 2018-01-19 (65 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

[Stephen Allen]

Forgot to add that this is 'vanilla gnome'.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's Bionic update, I had my mouse configured for left handed 
use. That is the mouse primary button being switched to the right. GCC doesn't 
seem to work for this now. I don't know if it's related to evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1758306] [NEW] Cannot switch mouse primary button in GCC

[Stephen Allen]

Public bug reported:

Prior to yesterday's Bionic update, I had my mouse configured for left handed 
use. That is the mouse primary button being switched to the right. GCC doesn't 
seem to work for this now. I don't know if it's related to evdev or what.
Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 23 07:07:02 2018
InstallationDate: Installed on 2018-01-19 (62 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
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/1758306

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's Bionic update, I had my mouse configured for left handed 
use. That is the mouse primary button being switched to the right. GCC doesn't 
seem to work for this now. I don't know if it's related to evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  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/1758306/+subscriptions

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

[Desktop-packages] [Bug 1741822] Re: nautilus crashed with SIGABRT in g_assertion_message → g_assertion_message_expr → filesystem_info_stop → start_or_stop_io → nautilus_directory_async_state_change

[Stephen Allen]

As reporter of this bug - It's gone, fini, finished for me. Hence 'fix-
released'.

Note: don't we need a 'closed' status?

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

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message →
  g_assertion_message_expr → filesystem_info_stop → start_or_stop_io →
  nautilus_directory_async_state_change

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Simply selected a podcast audio file, but app didn't segfault, and otherwise 
it appears to be working normally.
  I'm only reporting this, because Ubuntu-Bug was invoked automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  6 21:46:28 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-12-20 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   nautilus_directory_async_state_changed ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Stephen Allen]

Fix works here! Thank-you.

On Fri, Jan 12, 2018 at 12:05 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high
>
>   * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
> causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
>   * Refresh patches to apply more cleanly:
> - 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
> - 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch
>
>  -- Daniel van Vugt   Fri, 12 Jan 2018
> 10:23:11 +0800
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1742769).
> https://bugs.launchpad.net/bugs/1742750
>
> Title:
>   [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
>   invalid /etc/pulse/default.pa file
>
> Status in pulseaudio package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
>   connect.patch, which changes line 38 of /etc/pulse/default.pa to read
>   ".endif### Load audio drivers statically".  It appears that there are
>   a couple of line feeds missing here, and having the comment on the
>   same line as the endif causes pulseaudio not to start.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+subscriptions
>


-- 

This email is printed from 100% recycled electrons.

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

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://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 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

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

OK Thanks for this - Did not see that one prior to filing. Should I close
mine or has that already been done?

On Thu, Jan 11, 2018 at 9:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1742750 ***
> https://bugs.launchpad.net/bugs/1742750
>
> Duplicate of bug 1742750, thanks.
>
> ** This bug has been marked a duplicate of bug 1742750
>Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/
> default.pa file
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1742769
>
> Title:
>   Pulse Audio Won't Run After BionicBeaver Update
>
> Status in pulseaudio package in Ubuntu:
>   New
>
> Bug description:
>   As per the bug report, I've noticed that Pulse Audio is segfaulting.
>   Happened after the large update to Bionic Beaver this morning
>   (Thursday Jan 11/18).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
>   Uname: Linux 4.14.0-16-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
> '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c',
> '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
> '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p',
> '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p',
> '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1',
> '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: GNOME
>   Date: Thu Jan 11 13:32:21 2018
>   InstallationDate: Installed on 2017-12-20 (21 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/12/2012
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1401
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: M5A97 LE R2.0
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev 1.xx
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: To Be Filled By O.E.M.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: To be filled by O.E.M.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742769/+subscriptions
>


-- 

This email is printed from 100% recycled electrons.

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK 

[Desktop-packages] [Bug 1742769] [NEW] Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

Public bug reported:

As per the bug report, I've noticed that Pulse Audio is segfaulting.
Happened after the large update to Bionic Beaver this morning (Thursday
Jan 11/18).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
Uname: Linux 4.14.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: GNOME
Date: Thu Jan 11 13:32:21 2018
InstallationDate: Installed on 2017-12-20 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 bionic package-from-proposed pulseaudio sound wayland-session

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1738503] Re: Cannot Install SNAPS from Gnome-Software Bionic

[Stephen Allen]

I reinstalled (clean install) didn't use previous ~/home as I usually
do. I was thinking some data carried over from another distro may have
corrupted things. I usually keep ~home on a separate partition so I can
/install various distributions on the main drives, all sharing the same
~/home. Never ran into any issues until now. So I'll close this bug,
unless someone else is having the same problem?

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

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Error captured in attached Screengrab. I don't recall making any
  changes, how would I fix this locally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 15 18:36:40 2017
  InstallationDate: Installed on 2017-09-25 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.3-2ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1741822] [NEW] nautilus crashed with SIGABRT in g_assertion_message()

[Stephen Allen]

Public bug reported:

Simply selected a podcast audio file, but app didn't segfault, and otherwise it 
appears to be working normally.
I'm only reporting this, because Ubuntu-Bug was invoked automatically.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan  6 21:46:28 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-12-20 (18 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 nautilus_directory_async_state_changed ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

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


** Tags: amd64 apport-crash bionic need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Simply selected a podcast audio file, but app didn't segfault, and otherwise 
it appears to be working normally.
  I'm only reporting this, because Ubuntu-Bug was invoked automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  6 21:46:28 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-12-20 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   nautilus_directory_async_state_changed ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1738503] [NEW] Cannot Install SNAPS from Gnome-Software Bionic

[Stephen Allen]

Public bug reported:

Error captured in attached Screengrab. I don't recall making any
changes, how would I fix this locally?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.3-2ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
Uname: Linux 4.14.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 15 18:36:40 2017
InstallationDate: Installed on 2017-09-25 (81 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.26.3-2ubuntu1
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.3-2ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic gnome-software wayland-session

** Attachment added: "Screengrab of error message when attempting to install 
from Snap-store"
   
https://bugs.launchpad.net/bugs/1738503/+attachment/5023244/+files/Screenshot-20171215183531-1126x844.png

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

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Error captured in attached Screengrab. I don't recall making any
  changes, how would I fix this locally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 15 18:36:40 2017
  InstallationDate: Installed on 2017-09-25 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.3-2ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"

[Stephen Allen]

Affecting Ubuntu Evolution LTS 18.04 too

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

Title:
  Execution of filter 'Junk check' fails with "Empty cache file"

Status in Evolution:
  Unknown
Status in evolution package in Ubuntu:
  Confirmed
Status in evolution package in Debian:
  New

Bug description:
  I currently use an Evolution setup in which I retrieve email via IMAP
  from an unfiltered mailbox, and then use Evolution to automatically
  filter for spam/junk mail.

  This process works as expected upon starting Evolution: all email is
  retrieved from the mailbox (and thus resides in the Inbox folder,
  where it arrived), then it's filtered to identify spam, and then the
  spam is moved from the Inbox to a Junk folder.

  However, after Evolution has been running for some time (hard to
  estimate because it requires an email to be received, but likely 5-10
  minutes; it's possible that this is just "one email refresh interval"
  but also possible that something else is going on), newly received
  email stops being filtered for spam, and all the email remains in the
  Inbox. This happens at least in the case of receiving one email at a
  time, and most likely in the case where multiple emails are received
  in one send/receive cycle.

  When this failure to remove spam/junk happens, there's a yellow banner
  at the top of the screen saying, for example (the filename is not
  always the same),

  "Error while performing operation.

  Execution of filter 'Junk check' failed: Empty cache file:
  
/home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052"

  I checked the contents of the file in question; it appears to be a
  copy of the email that was just received, including all headers. (It's
  possible that there's a race condition here and that the file was
  empty when the filter looked at it, but became populated just after it
  errored out, but perhaps something else is going on.)

  This behaviour is a problem because it means that either I have to
  delete junk mail by hand, or else that I have to repeatedly close and
  reopen Evolution so that the automated system will work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 22 17:19:59 2016
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-06-03 (811 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SourcePackage: evolution
  UpgradeStatus: Upgraded to xenial on 2016-05-02 (112 days ago)

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Stephen Allen]

I can't even get vpn and/or socks5 to work. This is dangerous, perhaps
it should be stressed that people shouldn't use 11.10 as a daily OS
until this is fixed. I know, I know, me should know better. I'm just
glad I checked before assuming I was in a secure tunnel. Otherwise 11.10
is working fine without any show stoppers for moi.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1712221] [NEW] package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Charles Allen]

Public bug reported:

Not sure where the bug is. Not sure where to begin. I will work on trying to 
provide more technical information on how to report bugs that can actually help 
DevOps. I was trying to update the OS, however it is something that always pops 
up after initial boot/startup.
Thanks

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgtk2.0-bin 2.24.31-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 net-tools:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 17 19:45:16 2017
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-04-22 (121 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gtk+2.0
Title: package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Not sure where the bug is. Not sure where to begin. I will work on trying to 
provide more technical information on how to report bugs that can actually help 
DevOps. I was trying to update the OS, however it is something that always pops 
up after initial boot/startup.
  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgtk2.0-bin 2.24.31-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   net-tools:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 17 19:45:16 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-22 (121 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1712221/+subscriptions

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

[Desktop-packages] [Bug 1636514] Re: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

[Stephen Allen]

Same here only difference it happens when copying locally in Nautilus,
and yes, they're moved.

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

Title:
  nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

Status in Ubuntu GNOME:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  This crash occurred just after I had asked Nautilus to move several
  large files (in groups) to several different locations. Then I believe
  that I minimized Nautilus and in a few minutes noticed the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 25 13:52:09 2016
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-05-15 (162 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: nautilus .
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_cursor_on_cell () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (5 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1642828] [NEW] mixing of English and Khmer fonts

[Allen Myers]

Public bug reported:

I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are
presented partly in Khmer and partly in English.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog: [  OK  ] Started LSB: Speech Dispatcher.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Nov 18 13:47:26 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated 
Graphics Controller [1025:0920]
   Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993]
InstallationDate: Installed on 2016-09-29 (49 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Acer Aspire E5-572G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HWS
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd08/24/2015:svnAcer:pnAspireE5-572G:pvrV1.08:rvnAcer:rnEA50_HWS:rvrV1.08:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-572G
dmi.product.version: V1.08
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Nov 18 06:35:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5567 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  mixing of English and Khmer fonts

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are
  presented partly in Khmer and partly in English.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov 18 13:47:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated 
Graphics Controller [1025:0920]
 Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993]
  InstallationDate: Installed on 2016-09-29 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire E5-572G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash 

[Desktop-packages] [Bug 1641442] [NEW] Import with reneg-sec larger than 65535 fails

[Nick Allen]

Public bug reported:

Attempting to import a .ovpn config file with a reneg-sec option larger
than 65535 through the gnome network manager causes the following error
message:


The file 'config.ovpn' could not be read or does not contain recognized VPN 
connection information

Error: configuration error: invalid 1th argument to 'reneg-sec' where
number expected (line 54).

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Import with reneg-sec larger than 65535 fails

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

Bug description:
  Attempting to import a .ovpn config file with a reneg-sec option
  larger than 65535 through the gnome network manager causes the
  following error message:

  
  The file 'config.ovpn' could not be read or does not contain recognized VPN 
connection information

  Error: configuration error: invalid 1th argument to 'reneg-sec' where
  number expected (line 54).

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

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

[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Chris Allen]

Same issue here. I have an Asus X540LA laptop with the same chipset and
the headset mic doesn't work.

[1.576056] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[1.612215] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[1.612220] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[1.612224] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[1.612226] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[1.612228] snd_hda_codec_realtek hdaudioC1D0:inputs:
[1.612231] snd_hda_codec_realtek hdaudioC1D0:  Mic=0x1b

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

[Allen Hung]

My statement in #50 has some incorrectness. I thought unity does not
query current brightness, but accrording to Marco has addressed in #64
it is because upower always returns the cached brightness value.I do
agree the change has to be made at UPower side.

I also agree the commit c311de72495efdc757edb3cd59b1455541532eb7 should
be able to fix the issue at boot.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Desktop-packages] [Bug 1579319] [NEW] Text missing in GTK+ applications after suspend

[Nathan Allen]

Public bug reported:

Occasionally when resuming from suspend, text is randomly missing in
GTK+ applications. Chrome and QT apps are unaffected. In my case it
doesn't occur very frequently, perhaps once a week at most. I typically
suspend my system every day and only reboot once or twice a month.

It's not clear what is causing the problem. Based on the symptoms and
similar bug reports, it seems most likely a problem with xorg and/or
xserver-xorg-video-intel. It appears to be a new bug with 16.04 as I
never experienced this in 15.10.

I've noticed that the amount of missing text seems to vary depending on
the font and font size. Some fonts/sizes seem to be okay, while with
others there is no text on screen at all.

Font rendering settings also appear have an effect. The problem is only
visible with slight hinting and RGB sub pixel order. Disabling anti-
aliasing or changing either the hinting or sub pixel order to anything
else immediately renders all characters normally.

Switching to a virtual terminal and back again fixes the problem
(Ctrl+Alt+F1 then Ctrl+Alt+F7), as does restarting Xorg or logging out.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sat May  7 12:39:24 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
InstallationDate: Installed on 2016-04-23 (13 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Extensa 5230
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=ba619ff4-ea0b-4b58-aa61-e79a3e7e7c1b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.28
dmi.board.name: Homa
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5230
dmi.product.version: 0100
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  4 02:12:16 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   15105 
 vendor LPL
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug ubuntu xenial

** Attachment added: "Screenshot_2016-05-07_12-31-27.png"
   
https://bugs.launchpad.net/bugs/1579319/+attachment/4657780/+files/Screenshot_2016-05-07_12-31-27.png

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

Title:
  Text missing in GTK+ applications after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally when resuming from suspend, text is randomly missing in
  GTK+ applications. Chrome and QT apps are unaffected. In my case it
  doesn't occur very frequently, perhaps once a week at most. I
  typically suspend my system every day and only reboot once or twice a
  month.

  It's not clear what is causing the problem. Based on the symptoms and
  similar bug reports, it seems most likely a problem with xorg and/or
  xserver-xorg-video-intel. It appears to be a new bug with 16.04 as I
  never experienced this in 15.10.

  I've noticed that the amount of missing text seems to vary depending
  on the font and font size. Some fonts/sizes 

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

[Nathan Allen]

I'm having a similar issue. I found that switching to a virtual terminal
and back again fixes the missing text in my case (Ctrl+Alt+F1 then
Ctrl+Alt+F7).

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

Title:
  On-screen text disappears after suspend

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Apr 22 09:26:06 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1479
   vendor

[Desktop-packages] [Bug 971776] Re: software-center crashed with GError in constructor(): Format der Bilddatei unbekannt

[crystal allen]

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

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

Title:
  software-center crashed with GError in constructor(): Format der
  Bilddatei unbekannt

Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-software-center source package in Precise:
  Fix Released

Bug description:
  I am on Ubuntu12.04 64bit updated to 2.3.2012.

  The Software center crashed on the search term"python".

  [TEST CASE]
  This crash occurs only intermittently under certain conditions when an image 
download fails. As such, this error can't be reliably reproduced. However, to 
test, you can fully exercise this code by clearing the downloaded icon cache 
and then reloading them per the following steps:
  1. Install the version of software-center in precise-proposed.
  2. With Software Center not running, execute the following in a terminal:

  $ cd ~/.cache/software-center/icons
  $ rm *

  3. Launch Software Center and navigate to "All Software" -> "For Purchase"
  4. Verify that as you scroll the list the application icons are loaded in the 
view.

  [REGRESSION POTENTIAL]
  Very low. If a regression were to occur, it would manifest as "generic" icons 
appearing in the list views or the details view.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.14
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr  2 20:19:36 2012
  ExecutablePath: /usr/share/software-center/software-center
  ExecutableTimestamp: 1333128425
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac 
(20120328)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcCwd: /home/user
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-center']
  SourcePackage: software-center
  Title: software-center crashed with GError in constructor(): Format der 
Bilddatei unbekannt
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Jont Allen]

Why is this not getting fixed. It is clearly more than a nuance at this point.
The priority needs to be raised. What would that take to happen?

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Allen Webb]

@philip-gemmell-r what version of fglrx-updates did you install? (the
package version) I don't think the fix is actually released in the main
repositories. They are still showing (2:15.201-0ubuntu1)

If you want to get the fixed version you need to enable wily-proposed
long enough to install fglrx-updates. Then you can disable wiley-
proposed. For instructions see prior posts.

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1002453] Re: Firefox Screen Freeze

[Ian! D. Allen]

This just started happening to me in Ubuntu 15.04 with Firefox 42.0, but
only if I run Firefox under the old vtwm window manager:

Firefox 42.0 "Mozilla Firefox for Ubuntu" canonical - 1.0 under Ubuntu
15.04.

The browser now (in the past week or two) locks up when requested to
enter Full Screen if not running under any window manager (or when
running under an old window manager such as vtwm that doesn't have all
the modern hooks).

Reproduce:

1. Start up Ubuntu 15.04 with the full Unity desktop installed.
2. Clean out (remove or rename) $HOME/.mozilla to start clean.
3. Open Firefox.
4. Note that using F11 correctly resizes Firefox to Full Screen and back down.
5. Kill the window manager: run: initctl stop unity7
6. Return to Firefox and try F11 or turn on "Full Screen" from the menu.
7. Browser locks up.

Changing tabs doesn't refresh the screen unless you do something to
trigger an X11 refresh such as opening a menu.  F11 does *not* undo the
damage - the browser stays locked up.  Using the Firefox menu to disable
(un-check) "Full Screen" also does nothing.  Nothing works.

8. Start an old window manager such as "vtwm".  No change.  Firefox is
still locked up.
9. Exit vtwm.
10. Re-start the Unity window manager: run: initctl start unity7
11. Return to Firefox and use F11 or the menu "Full Screen" a few times and 
Firefox is working again.
12. Repeat as needed. 

** Summary changed:

- Firefox Screen Freeze
+ Firefox Screen Freeze in Full Screen mode

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

Title:
  Firefox Screen Freeze in Full Screen mode

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04.

  Firefox freezes when I enter full screen mode. By freeze, I *do not*
  mean that it locks up. I can't think of another word to use. What
  happens is that anything below the top bar becomes unreadable.

  For example, after a period of time in full screen, if I were to go
  and begin typing a web address, what usually would come down in a drop
  menu of recent websites doesn't appear. Also, if I am scrolling down a
  website, it doesn't register. This is the case until I put the mouse
  at the top of the screen to bring down the top bar, and at this time
  the new website will register on the screen.

  Apologies if this doesn't make enough sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 12.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dalton 1866 F pulseaudio
   /dev/snd/pcmC0D0p:   dalton 1866 F...m pulseaudio
  BuildID: 20120423122928
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf540 irq 53'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0269,10431213,00100100 
HDA:80862804,10431213,0010'
 Controls  : 26
 Simple ctrls  : 12
  Channel: release
  Date: Mon May 21 15:06:08 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.3  metric 2
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423122928 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-05-18 (3 days ago)
  dmi.bios.date: 07/01/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U43
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd07/01/2010:svnASUSTeKComputerInc.:pnU43F:pvr1.0:rvnPEGATRONCORPORATION:rnU43:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.name: U43F
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Allen Webb]

@Mikael This probably isn't the right place to report something like
that unless it doesn't happen when you use the same driver version
without the gcc 5.0 fix. I am not sure where the best place is to report
bugs in the proprietary driver it self but a quick google let me to:
http://www.amdsurveys.com/se.ashx?s=5A1E27D23A3DE979

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Allen Webb]

I have been following another bug related to creating USB boot drives
and it seems like they are having issues with gcc 5.0 because of a
section alignment issue. I don't know whether or not that would effect
compiling the wrapper for fglrx, but I figured I would bring it up
incase it is linked to the root cause of the incompatibility with gcc. I
know the boot issue with syslinux is different than the boot issue with
fglrx, but if there is an issue created by a bug or change in gcc 5 it
might give some light on other issues. See:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002/comments/6

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1377546] Re: evince gets Gtk-CRITICAL errors

[Jont Allen]

I also see this bug with 15.04. It makes looking at the Latex errors, very 
difficult. And its really annoying to have this error
constantly spewing across the screen.

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

Title:
  evince gets Gtk-CRITICAL errors

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  evice alwas gets following errors when opening a PDF file:

  (evince:3932): GLib-GObject-WARNING **: The property GtkSettings:gtk-
  menu-images is deprecated and shouldn't be used anymore. It will be
  removed in a future version.

  (evince:3932): Gtk-CRITICAL **: gtk_widget_show: assertion
  'GTK_IS_WIDGET (widget)' failed

  (evince:3932): Gtk-CRITICAL **: gtk_widget_show: assertion
  'GTK_IS_WIDGET (widget)' failed

  Here is the release information:

  jchen@utopic:~$ lsb_release -rd
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10
  jchen@utopic:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  4 19:33:41 2014
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2014-10-03 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Allen Webb]

I ended up with two ubuntu one accounts for some reason, so I tested it in 
#108. Both the 16.04 packages and the packages in wily-proposed have fixed the 
problem for me. Versions:
ii  fglrx-amdcccle-updates  
2:15.201-0ubuntu2~15.10.1  amd64Catalyst Control Center 
for the AMD graphics accelerators
ii  fglrx-updates   
2:15.201-0ubuntu2~15.10.1  amd64Video driver for the 
AMD graphics accelerators
ii  fglrx-updates-core  
2:15.201-0ubuntu2~15.10.1  amd64Minimal video driver 
for the AMD graphics accelerators
ii  fglrx-updates-dev   
2:15.201-0ubuntu2~15.10.1  amd64Video driver for the 
AMD graphics accelerators (devel files)

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

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Wily:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

-- 
Mailing list: https://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 1506817] [NEW] left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

[Jont Allen]

it seems that your attached to this bug report. I have no idea why. I 
dont think I emailed you, launchpad did this.
If you dont understand what I saying, just ignore it. Its is not important.

Jont Allen

On 10/16/2015 02:25 PM, A. Richard Miller wrote:
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1506817

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

Title:
  left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I have reported the details of this problem at
  https://answers.launchpad.net/ubuntu-certification/+question/272142

  As summarized on that question:

  X250 analysis:
   I used the command on the X250
evtest /dev/input/event15 | grep EV_KEY

   I can see the bug, as follows:

  I click on button 1 (left) over and over. When I push the button down,
  I see it register as 1,
  and when I let go of the key, it registers as a 0.

  The bug is that every now and then (once every 20 clicks), when I let go
  of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays 
in state 1).

  This is highly random, but cant be triggered more often, by dragging a
  window, which I do with BIN_LEFT.

  I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
  this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

  Ubuntu 15.04

  apt-cache policy xserver-xorg-input-synaptics
  xserver-xorg-input-synaptics:
Installed: 1.8.1-1ubuntu1
Candidate: 1.8.1-1ubuntu1
Version table:
   *** 1.8.1-1ubuntu1 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 04:52:03 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  InstallationDate: Installed on 2015-08-15 (61 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct 16 03:31:10 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1506817/+subscriptions

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

[Desktop-packages] [Bug 1506817] [NEW] left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

[Jont Allen]

Public bug reported:

I have reported the details of this problem at
https://answers.launchpad.net/ubuntu-certification/+question/272142

As summarized on that question:

X250 analysis:
 I used the command on the X250
  evtest /dev/input/event15 | grep EV_KEY

 I can see the bug, as follows:

I click on button 1 (left) over and over. When I push the button down,
I see it register as 1,
and when I let go of the key, it registers as a 0.

The bug is that every now and then (once every 20 clicks), when I let go
of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays in 
state 1).

This is highly random, but cant be triggered more often, by dragging a
window, which I do with BIN_LEFT.

I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

Ubuntu 15.04

apt-cache policy xserver-xorg-input-synaptics
xserver-xorg-input-synaptics:
  Installed: 1.8.1-1ubuntu1
  Candidate: 1.8.1-1ubuntu1
  Version table:
 *** 1.8.1-1ubuntu1 0

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 16 04:52:03 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
InstallationDate: Installed on 2015-08-15 (61 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20CMCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET36W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CMCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CMCTO1WW
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Oct 16 03:31:10 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1079 
 vendor LGD
xserver.version: 2:1.17.1-0ubuntu3.1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu vivid

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

Title:
  left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I have reported the details of this problem at
  https://answers.launchpad.net/ubuntu-certification/+question/272142

  As summarized on that question:

  X250 analysis:
   I used the command on the X250
evtest /dev/input/event15 | grep EV_KEY

   I can see the bug, as follows:

  I click on button 1 (left) over and over. When I push the button down,
  I see it register as 1,
  and when I let go of the key, it registers as a 0.

  The bug is that every now and then (once every 20 clicks), when I let go
  of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays 
in state 1).

  This is highly random, but cant be triggered more often, by dragging a
  window, which I do with BIN_LEFT.

  I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
  this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

  Ubuntu 15.04

  apt-cache policy 

[Desktop-packages] [Bug 1506817] Re: left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

[Jont Allen]

I upgraded 15.05 with all the latest patches as of Oct 16, 2015.

The left-mouse button bug is not fixed.

apt-show-versions xserver-xorg-input-synaptics 
xserver-xorg-input-synaptics:amd64/vivid 1.8.1-1ubuntu1 uptodate

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

Title:
  left TPP/2 IBM TrackPoint "sticks on" randomly (X250 15.04)

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I have reported the details of this problem at
  https://answers.launchpad.net/ubuntu-certification/+question/272142

  As summarized on that question:

  X250 analysis:
   I used the command on the X250
evtest /dev/input/event15 | grep EV_KEY

   I can see the bug, as follows:

  I click on button 1 (left) over and over. When I push the button down,
  I see it register as 1,
  and when I let go of the key, it registers as a 0.

  The bug is that every now and then (once every 20 clicks), when I let go
  of the left mouse button (BIN_LEFT), it does not return to state 0 (it stays 
in state 1).

  This is highly random, but cant be triggered more often, by dragging a
  window, which I do with BIN_LEFT.

  I am using a brand new X250, purchased in late July 2015. The system was 
returned 3 times to IBM repair as I assumed
  this was a hardware error. Now with the above, it seems clear that this is a 
software issue.

  Ubuntu 15.04

  apt-cache policy xserver-xorg-input-synaptics
  xserver-xorg-input-synaptics:
Installed: 1.8.1-1ubuntu1
Candidate: 1.8.1-1ubuntu1
Version table:
   *** 1.8.1-1ubuntu1 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 04:52:03 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  InstallationDate: Installed on 2015-08-15 (61 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=5718b40f-944e-47a3-acda-04e29336d0bc ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET36W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct 16 03:31:10 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1506817/+subscriptions

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

[Desktop-packages] [Bug 1493888] [NEW] FGLRX incompatible with kernel 4.2

[Allen Webb]

Public bug reported:

With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am able
to SSH into the machine. I booted the older kernel (4.1.0-3-generic) and
it works with FGLRX. After purging FGLRX and using xserver-xorg-video-
radeon I am able to get the graphics working, but even it has issues
with my display port (The DVI ports are working correctly).

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
Date: Wed Sep  9 09:29:54 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-01-07 (1705 days ago)
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  FGLRX incompatible with kernel 4.2

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with kernel 4.2

[Allen Webb]

It looks like this has been reported upstream:
http://ati.cchtml.com/show_bug.cgi?id=1189

** Bug watch added: ATi Linux Platform Bugs #1189
   http://ati.cchtml.com/show_bug.cgi?id=1189

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

Title:
  FGLRX incompatible with kernel 4.2

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions

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

[Desktop-packages] [Bug 1451146] [NEW] fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build

[Clay Allen Figley]

Public bug reported:

I was following instructions here: 
https://help.ubuntu.com/community/BinaryDriverHowto/AMD#Manually_installing_Catalyst_13.4
When I ran sudo dpkg -i fglrx*.deb some dependencies weren't met, so I 
proceeded to Ubuntu Software Center, which automatically recognized the unmet 
dependencies and began downloading and installing them.  Before the changes 
were complete in the USC progress tab, this error popped up, and here's the bug 
report.

I'll try a couple of things and update with progress.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:8.970-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:
 
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSBuildLog:
 DKMS make.log for fglrx-8.970 for kernel 3.16.0-30-generic (x86_64)
 Sun May  3 01:38:27 CDT 2015
 AMD kernel module generator version 2.1
 kernel includes at /lib/modules/3.16.0-30-generic/build/include not found or 
incomplete
 file: /lib/modules/3.16.0-30-generic/build/include/linux/version.h
DKMSKernelVersion: 3.16.0-30-generic
Date: Sun May  3 01:38:36 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.970: added
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff1f]
InstallationDate: Installed on 2015-05-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: TOSHIBA Satellite L505D
PackageVersion: 2:8.970-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=8941aaa7-8b0f-4cd8-95fb-4f4a1f698df6 ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer
Title: fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.10
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd12/17/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-00J001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite L505D
dmi.product.version: PSLV6U-00J001
dmi.sys.vendor: TOSHIBA
make.log:
 DKMS make.log for fglrx-8.970 for kernel 3.16.0-30-generic (x86_64)
 Sun May  3 01:38:27 CDT 2015
 AMD kernel module generator version 2.1
 kernel includes at /lib/modules/3.16.0-30-generic/build/include not found or 
incomplete
 file: /lib/modules/3.16.0-30-generic/build/include/linux/version.h
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 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
xserver.bootTime: Sun May  3 00:30:05 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
xserver.video_driver: radeon

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 trusty ubuntu

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

Title:
  fglrx 2:8.970-0ubuntu1: fglrx kernel module failed to build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  I was following instructions here: 
https://help.ubuntu.com/community/BinaryDriverHowto/AMD#Manually_installing_Catalyst_13.4
  When I ran sudo dpkg -i fglrx*.deb some dependencies weren't met, so I 
proceeded to Ubuntu Software Center, which automatically recognized the unmet 
dependencies and began downloading and installing them.  Before the changes 
were complete in the USC progress tab, this error popped up, and here's the bug 
report.

  I'll try a couple of things and update with progress.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:8.970-0ubuntu1
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves

[Allen Webb]

Is it just me or does the --scale option ignore the cursor so that the
cursor isn't scaled with the desktop/screen?

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Precise:
  Fix Released
Status in xorg-server source package in Quantal:
  Fix Released
Status in xorg-server source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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