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

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

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 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 1414291] [NEW] [To be filled by O.E.M., Realtek ALC887-VD, Green Headphone Out, Front] Pulseaudio fails to detect card

[Stephen Allen]

Public bug reported:

After updating last evening to alpha 2 of this upcoming Ubuntu release.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:4.0-0ubuntu22
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC2D0c', 
'/dev/snd/controlC2', '/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/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: GNOME
Date: Sat Jan 24 07:41:29 2015
InstallationDate: Installed on 2015-01-20 (4 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141218)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA ATI SB
Symptom_Jack: Green Headphone Out, Front
Title: [To be filled by O.E.M., Realtek ALC887-VD, Green Headphone Out, Front] 
Pulseaudio fails to detect card
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.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 apport-bug vivid

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

Title:
  [To be filled by O.E.M., Realtek ALC887-VD, Green Headphone Out,
  Front] Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After updating last evening to alpha 2 of this upcoming Ubuntu
  release.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC2D0c', 
'/dev/snd/controlC2', '/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/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Sat Jan 24 07:41:29 2015
  InstallationDate: Installed on 2015-01-20 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141218)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Headphone Out, Front
  Title: [To be filled by O.E.M., Realtek ALC887-VD, Green Headphone Out, 
Front] Pulseaudio fails to detect card
  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.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/1414291/+subscriptions

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

[Desktop-packages] [Bug 1396250] [NEW] Continually am prompted for Google credentials. First time pwd is always wrong, 2nd input takes. This happened on Debian Jessie awhile ago too.

[Stephen Allen]

Public bug reported:

It happens at intermittent times, there is no logic to it in terms of I
do this and it happens. Always the 1st attempt is wrong, regardless if
the pwd is correct or not. Very irritating.

Not absolutely sure if this should be filed against Gnome proper or GOA.
So, feel free to change to the appropriate package if this is wrong.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gnome-online-accounts 3.12.4-1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Tue Nov 25 11:57:53 2014
InstallationDate: Installed on 2014-11-23 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Continually am prompted for Google credentials. First time pwd is
  always wrong, 2nd input takes. This happened on Debian Jessie awhile
  ago too.

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

Bug description:
  It happens at intermittent times, there is no logic to it in terms of
  I do this and it happens. Always the 1st attempt is wrong, regardless
  if the pwd is correct or not. Very irritating.

  Not absolutely sure if this should be filed against Gnome proper or
  GOA. So, feel free to change to the appropriate package if this is
  wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-online-accounts 3.12.4-1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Nov 25 11:57:53 2014
  InstallationDate: Installed on 2014-11-23 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   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-online-accounts/+bug/1396250/+subscriptions

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